A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
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.
Only 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:https://superuser.com/questions/42843/finding-the-process-that-is-using-a-certain-port-in-linux
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.
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