522 Error from Cloudflare after finished setup new SlickStack

yes this is an ongoing issue currently, you can simply sudo reboot and it fixes it (only affects first time SlickStack installs)

nobody sure why this is happening but more testing is being done

I think someone people see 502 error or 522 error…

There are 2 main issues we have been trying to fix over the past year:

1. Lets Encrypt failing to issue on the first attempt
2. 5xx error after first SlickStack install

Because these seemed possibly related, it made debugging them very confusing, esp. based on somewhat conflicting info we found while researching Certbot issues. To make matters even more confusing, the 5xx error only seemed to appear after Ubuntu 22.04 LTS… however, we now know that it wasn’t related to the kernel as we initially suspected.

The Lets Encrypt problem had to due with port 80 not 301 redirecting Certbot properly based on domain-matched Nginx blocks.

why does SlickStack fail to activate Lets Encrypt on first attempt

And the 5xx error we now believe was due to PHP-FPM being restarted instead of reloaded, which resulted in TCP listener 127.0.0.1:9000 never initiating until reboot.

https://www.google.com/search?q=522+cloudflare

so many possible causes!