Troubleshooting NPM issues after power outage and IP change

Hey folks, I’m in a bit of a pickle with my NPM setup. Everything was smooth sailing for months, but then we had a power cut. Now my apps and WordPress site are acting up.

Here’s the deal:

  • Requests are timing out
  • NPM shows expired SSL certs on my proxies
  • Can’t renew certs (get an ‘Internal Error’)
  • Public IP changed after the outage
  • Updated Cloudflare DNS, but still having issues
  • Site loads slowly, shows ‘insecure site’ warning
  • Now getting error 522 timeouts

I’m running this on Proxmox as a homelab project. Not super experienced with Docker or NPM, but I think the IP change messed something up.

Any ideas on how to get this back on track? I’m all ears for suggestions!

I encountered a similar scenario before. First, check that Cloudflare’s DNS records have been fully updated to your new IP address. It also helped to manually renew your SSL certificates in NPM by triggering a forced renewal, ensuring that the configuration aligns with the current network settings. In addition, restarting the Docker containers allowed them to reinitialize their network parameters. Lastly, verify that firewalls on both your server and router aren’t inadvertently blocking the new IP. Step by step, these adjustments typically resolve such configuration issues.

yo, sounds like u got a real headache there. have u tried flushing ur DNS cache? sometimes that helps with weird connection issues. also, double-check ur firewall settings - they mightve gotten messed up during the outage. if all else fails, maybe try rebuilding ur docker containers from scratch. good luck!

Been there, done that. Power outages can be a real pain, especially when they mess with your homelab setup. First things first, I’d recommend checking your router’s configuration. Sometimes after an IP change, port forwarding rules need to be updated. That could explain why you’re getting timeouts and can’t renew certs.

Next, try clearing your browser cache and flushing DNS on your local machine. It’s surprising how often this solves weird connectivity issues. If that doesn’t work, you might need to regenerate your SSL certs from scratch in NPM. I’ve had to do this a few times after major network changes.

As for the Docker containers, consider recreating them with the new network settings. It’s a bit of a hassle, but it ensures everything’s aligned with your current setup. And don’t forget to double-check your Cloudflare settings - sometimes it takes a while for changes to propagate fully.

Lastly, patience is key. DNS changes can take up to 48 hours to fully propagate across the internet. Hang in there, and keep troubleshooting. You’ll get it sorted!