Nginx Error
from selfhostingperson@sh.itjust.works to selfhosted@lemmy.world on 26 Feb 07:19
https://sh.itjust.works/post/33448300
from selfhostingperson@sh.itjust.works to selfhosted@lemmy.world on 26 Feb 07:19
https://sh.itjust.works/post/33448300
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.
threaded - newest
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 -nlpto find the process nameRun it with sudo in case you don’t see the process name with the above command.
sudo ss -patln | grep 443Only one program can listen on a port at a given time usually. Something’s listening on port 443 (the standard HTTPS port), and when nginx starts up it tries to listen on that port and can’t. You can figure out what’s already listening on that port with commands like
lsofornetstat, see here for examples:superuser.com/…/finding-the-process-that-is-using…
Thanks! Turns out nginx proxy manager was using 443. Changed the port and now nginx throws no errors!
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.
And ports are per-protocol. Some DNS servers use TCP 53 and UDP 53, for example.
That’s really interesting. What about 0.0.0.0? Does it resolve to localhost or the “public” ip?
0.0.0.0 means listen on all IPs
g.co/gemini/share/5a4a2f9998be
It’s a good answer