Broken sites error 522, need help

Hi, I am running a WordPress Site and several services on a Proxmox server at my house. I use Cloudflare for my Domains and proxy, sent back to Nginx Proxy Manager on my home server. I have used this setup for almost a year, and it has been working well. Unfortunately, a couple nights ago, the power went out, and all my sites quit working, timing out with error 522. I discovered my ISP changed my public IP Address. I revised my Cloudflare Domain to point to the new address, figuring that would fix it, but I'm still having the sites time out. I am running the WordPress Site on a Cloudpanel VM, which is proxied through Cloudflare to Nginx Proxy Manager. Anyone know what I might be missing to fix my sites?
5 Replies
andrew_nyr
andrew_nyr2d ago
Hmm, I would double check the new IP and any of your firewall settings to see if any of them contain the old IP
andrew_nyr
andrew_nyr2d ago
I would also look into switching to a Cloudflare Tunnel if I were you, that way if your IP changes it doesn't kill your sites. https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/
Cloudflare Docs
Cloudflare Tunnel · Cloudflare Zero Trust docs
Cloudflare Tunnel provides you with a secure way to connect your resources to Cloudflare without a publicly routable IP address. With Tunnel, you do not send traffic to an external IP — instead, a lightweight daemon in your infrastructure (cloudflared) creates outbound-only connections to Cloudflare's global network. Cloudflare Tunnel can conn...
JS
JSOP2d ago
Thanks, that sounds like a good option. So I would want to install the "Cloudflared" tunnel app on the Cloudpanel VM that hosts the site, and it should be able to pick up the site on localhost?
andrew_nyr
andrew_nyr2d ago
yep
JS
JSOP21h ago
I am looking into using a tunnel for the sites, however, I feel like I am close to restoring my existing setup. Last night, I made my own SSL Certificates through the Cloudflare API tokens, and was able to install them since it was having an internal error on NPM when I tried to renew the old ones. So I got SSL set up again. I can now reach the sites with https while I have the Proxy toggled off on Cloudflare and set to "DNS Only". But as soon as I turn the Proxy toggle on again, it breaks the site. I am wondering if there is there some kind of cache going on with the Cloudflare Proxy or something maybe?

Did you find this page helpful?