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.
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
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
selfh.st Newsletter and index of selfhosted software and apps
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 443