I rebuilt Discourse to v2.1.0.beta3 +20 following notification this morning that there was a critical update. There were no errors during the rebuilding. However, the Admin dashboard now returns a 502 after trying to load unsuccessfully for a few minutes.
When I SSH into the server and curl https://forum.quartertothree.com/admin/dashboard/general.json, the page seems to be returned. However, when trying to hit it externally, the following is in the Nginx log:
Looking in /var/discourse/shared/standalone/log/rails/unicorn.stderr.log the following appears:
E, [2018-07-27T18:07:20.883373 #323] ERROR -- : worker=3 PID:12195 timeout (31s > 30s), killing I, [2018-07-27T18:07:26.991147 #12648] INFO -- : worker=3 ready
We’ve tried turning off Cloudflare and/or various components of it, including the firewall. Regardless, the admin dashboard won’t load. Everything else about the forum is working as expected. Everything was working as expected prior to rebuilding.
Every other part of the Admin section works as expected… it’s only the dashboard portion that won’t load.
I’m on +21 and dashboard is loading fine as of now! as there is cloudflare involved, I’m almost certain that it is something to do with caching at their end but I can be wrong too.
Easiest way to know if it’s cloudflare is to disable their optimizations by going to DNS and disabling it (turning orange cloud grey by clicking it) and then a force refresh byCTRL+F5
You really REALLY do not want all traffic going through CloudFlare to a Discourse instance. We’ve had dozens of issues with CloudFlare “accidentally” breaking Discourse over the last couple of years. Search here if you don’t believe me.
Ok, thanks. I’ll do some searching to try to figure out the best way to set it up. It should be fine just serving up images and cat gifs, etc. though, right?
Ok, I did all of those things and none of them addressed the issue. We tried completely disabling Cloudflare and it still won’t work. It’s ONLY the bottom part of the Admin Dashboard page.
Now on v2.1.0.beta3 +30. Any further suggestions? I’m happy to give anything a shot.
Also note, I’m trying to help you debug this here, but next week I will push a commit to make it way easier to know what the error is, instead of this “exception” window.
Every one of those URLs loads swiftly with no errors.
And good to hear! This isn’t mission-critical as the entire site works except that dashboard, but it is a bit annoying. Really appreciate your help on a saturday night!