Hello, I’ve been messing around with prosody and snikket and that means I’ve been messing around with nginx. I was having some issues so I decided to uninstall nginx and after anothet round of messing around with snikket, decided to install nginx again. It showed this error and I don’t really know what to do, since I’m really not that good with self-hosting yet. Please help. I will give more info as needed.

    • selfhostingpersonOP
      link
      fedilink
      English
      arrow-up
      15
      ·
      11 hours ago

      Thanks! Turns out nginx proxy manager was using 443. Changed the port and now nginx throws no errors!

    • red_bull_of_juarez@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      6
      ·
      10 hours ago

      Just to clarify, you can attach one listener per IP and port tuple. This means you can have separate processes listening on, for example, 127.0.0.1:80 and 192.168.0.1:80.

      • catloaf@lemm.ee
        link
        fedilink
        English
        arrow-up
        3
        ·
        7 hours ago

        And ports are per-protocol. Some DNS servers use TCP 53 and UDP 53, for example.

  • Matt The Horwood@lemmy.horwood.cloud
    link
    fedilink
    English
    arrow-up
    8
    ·
    12 hours ago

    your running something on port 443 already, if its nginx thats still running kill it. If not, then found out what is running on port 443 and kill it use ss -nlp to find the process name

    • sudneo@lemm.ee
      link
      fedilink
      English
      arrow-up
      4
      ·
      12 hours ago

      Run it with sudo in case you don’t see the process name with the above command.

      sudo ss -patln | grep 443