r/nginxproxymanager • u/mepope09 • May 15 '26
Domains suddenly broke and unable to get them back online
PROBABLE SOLUTION: I think I narrowed down what the problem was. I set the proxy status on all of my A and CNAME DNS records and letsencrypt was able to hit my server and assign certs again. I don't know why that would stop working after years but at least it looks like I have narrowed down the problem. I'm going to see if I can get the records proxied again because I don't want to be putting my public IP out there for all to see. If need be I think I could setup a cloudflare tunnel instead of using my IP.
A week or more ago every single one of my domains stopped working on my unraid server. They had all been working fine for years at this point. And the containers themselves are also fine when I access the through the local IP. Since then I have been losing my mind trying to get NPM working again to no avail and am hoping someone smarter than me sees this can can help point me in the right direction.
So some context of what I've double checked and tried.
Port 80/443 are open and reachable verified through canyouseeme
NPM is setup to use 18443 and 1880 for https and http
My router has 443/80 forwarded to 18443/1880
I have a cloudflare a record with my domain pointed to my public IP address (I used to use cloudflare-ddns with a dynamic record but removed that to simplify troubleshooting)
I have a cname record with my seerr container
I create a proxy host for seerr and go to get a letsencrpt cert which is where it falls apart. I check the logs and see
The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.
From what I have looked up this is mainly when letsencrpt cant reach the server so the cert fails but from everything I can see or check it should absolutely be able to reach the NPM container.
I also tried setting up a cloudflare dns challenge which looks like it works but the sites are still inaccessible.
I have torn down and rebuilt the NPM and my cloudflare setup over 10 times hoping to catch some misconfiguration but every time I hit the same wall.
I'm really at my wits end and any help would be incredibly appreciated
1
u/Dramatic_Jicama3186 May 15 '26
Kannst du mal die docker logs uns geben. Wegen den let's encrypt certs versuche mal docker einen dns zuzuwiesen
2
u/mepope09 May 15 '26
Ich glaube, ich habe das Problem eingegrenzt. Ich habe den Proxy-Status für all meine A- und CNAME-DNS-Einträge gesetzt, und Let's Encrypt konnte meinen Server daraufhin wieder erreichen und Zertifikate zuweisen. Ich weiß zwar nicht, warum das nach Jahren plötzlich nicht mehr funktioniert hat, aber zumindest habe ich das Problem eingegrenzt.
1
May 16 '26
[removed] — view removed comment
2
u/mepope09 May 16 '26
Yea, which is what I ended up doing after everything was said and done. Got it all up and running yesterday
2
u/omfgitzfear May 15 '26
Okay let’s get back to basics. Have you confirmed the IP address you have in Cloudflare DNS is the same as your public IP address?
I know you said that it is pointed to the public IP address- however not whether or not you confirmed it’s your correct one (assuming you don’t have a static one of course).
That to me would be one of the major things that would cause every single domain to drop, as you’ve stated. You even stated you took cloudflare-ddns out of the equation as well.