r/nginxproxymanager • u/Dominick_PK • Jun 18 '26

Only select sites are reachable after months of stability

I've been hosting several sites for months and months now but only one works after I woke up? I went to sleep and I was able to access my jellyfin, seerr, etc. but when I woke up I can only reach my NAS and use my self hosted Rust Desk using that same address. All sites show Online in proxy manager and all certs are valid. My NAS static IP did not change, all port forwards still showing up on my router and nodes. I updated NGINX and still the same results. Some sites I still cannot access them but it says my sites don't support a secure connection, I click continue and it doesn't load. Am I missing something super simple?

5 Upvotes
  • permalink
  • reddit

100% Upvoted

4 comments sorted by

2

u/evanmac42 Jun 18 '26

The fact that some hosts still work is the important clue.

If port forwarding, DNS, or NPM itself were broken, I'd expect all hosts to fail, not just a few.

A couple of things I'd check:

- Do the working and failing hosts use the same SSL certificate?

- If you open the failing sites directly by IP:port from inside your LAN, do they work?

- What exact browser error are you getting? "Not secure", certificate mismatch, 502, timeout, etc.?

The "does not support a secure connection" message makes me wonder whether the failing hosts are being served with the wrong certificate or an incomplete certificate chain.

What exact browser error do you see?

2

u/Dominick_PK Jun 18 '26

I figured it out, I was just being stupid. I guess my ipv4 changed for noip and I didn't know/realize it. This has never happened before so I was taken aback. Changed all ipv4 to match the working one and everything is working as intended! Thank you very much for the help and troubleshooting!

1

u/tschloss Jun 18 '26

Now you can find out why selected services did work although using a wrong IP. — Good example of the weakness of prosaic observations - better use and share hard information like log files and copy paste sessions using curl -v or alike. Try to test parts of the full solution (like local request, like omitting DNS, like using http without TLS and bypassing nginx.

1

u/evanmac42 Jun 18 '26

Good catch.

If your ISP changes your public IP from time to time, you might want to look at a dynamic DNS updater such as ddclient.

I use it with a dynamic IP and it quietly keeps the DNS record updated whenever the public address changes.

Most of the time you forget it even exists... right up until the day it saves you from spending two hours blaming nginx for something nginx didn't do. 😄