Good morning/night/evening/the time for you right now, ever since I set up Snikket, my web pages other than Snikket’s have been displaying nginx 404 not found errors. I can access the website locally but when I go to the domain name it pops up the error. When I go to localhost:443 it also shows the nginx not found 404 thing so I think that’s where my other website pages are getting the error from, but I never port fowarded port 443, at least I don’t think so. I use the standard nginx reverse proxy for Snikket, and Nginx Proxy Manager for my other web pages. I really hope someone can help me. Thank you very much in advance.
And the websites that had the nginx error went down. I don’t know how this could even happen? My containers use their own nginxes??? Maybe the mix of native nginx and docker nginx is messing everything up, if I can’t find a solution I’m probably gonna nuke my native nginx and use docker nginx for all of my nginx needs
nginx proxy manager’s in a docker container reverse proxying my nginx docker containers, and native nginx is reverse proxying snikket container because nginx proxy manager doesn’t go well with snikket.
Here’s the nginx config for my snikket.
server { # Accept HTTP connections listen 80;
listen [::]:80;
server_name chat.allinuxuser.xyz;
server_name groups.chat.allinuxuser.xyz;
server_name share.chat.allinuxuser.xyz;
location / { proxy_pass http://localhost:5080/; proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
# This is the maximum size of uploaded files in Snikket
client_max_body_size 104857616; # 100MB + 16 bytes }
} server { # Accept HTTPS connections
listen [::]:443 ssl; listen 443 ssl;
ssl_certificate /etc/letsencrypt/live/allinuxuser.xyz-0001/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/allinuxuser.xyz-0001/privkey.pem;
server_name chat.allinuxuser.xyz; server_name groups.chat.allinuxuser.xyz;
server_name share.chat.allinuxuser.xyz;
location / {
proxy_pass https://localhost:5443/;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
# REMOVE THIS IF YOU CHANGE `localhost` TO ANYTHING ELSE ABOVE
proxy_ssl_verify off;
proxy_set_header X-Forwarded-Proto https;
proxy_ssl_server_name on;
# This is the maximum size of uploaded files in Snikket
client_max_body_size 104857616; # 100MB + 16 bytes
# For BOSH and WebSockets
proxy_set_header Connection $http_connection;
proxy_set_header Upgrade $http_upgrade;
proxy_read_timeout 900s;
}
}
Here’s the docker-compose for one of the sites i’m running that’s been affected by the weird nginx error.
So your native nginx process covers ports 80 and 443. which ports does your NPM use? Are you trying to use the same ports? Because that’ll most likely clash.
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
Post more logs/configs
What kind of logs should I post?
find out which process is really binding to 443 if you don’t recognize that port as being used
I don’t know how to even interpret this, I know it says nginx but which nginx?? I got like 4 nginx web servers running
you do have an nginx process with PID
2511847using the portget more info with
ps aux | grep 2511847or kill it, if you need to spawn a new one with the right configuration
apparently it’s my native nginx… wtf. I used
And the websites that had the nginx error went down. I don’t know how this could even happen? My containers use their own nginxes??? Maybe the mix of native nginx and docker nginx is messing everything up, if I can’t find a solution I’m probably gonna nuke my native nginx and use docker nginx for all of my nginx needs
You’ll have to look by pid or command line.
The ones from the applications which should do the proxying and serving.
BTW: you’re using both Nginx Proxy Manager and Nginx in parallel? Native installations, docker, something else?
How are they configured?
nginx proxy manager’s in a docker container reverse proxying my nginx docker containers, and native nginx is reverse proxying snikket container because nginx proxy manager doesn’t go well with snikket.
Here’s the nginx config for my snikket.
Here’s the docker-compose for one of the sites i’m running that’s been affected by the weird nginx error.
Please tell me if there’s any more logs I need to provide.
So your native nginx process covers ports 80 and 443. which ports does your NPM use? Are you trying to use the same ports? Because that’ll most likely clash.
I mean I got them portmapped to other ports so… I dunno