Thanks for checking @ivo! After lots of digging, we found a few issues that were fixable and have updated it. Most of these issues were in the Cloudflare settings. In case anyone else in the future is planning to use Galaxy with Cloudflare here are the things we’ve learned:
Don’t use the Argo routing optimisation (it’s a paid upgrade) - for some reason, it seems to freak out routing to the galaxy servers and seems to have been the cause of the 500 errors
Using Cloudflare seems to have sped up the load times for our users in different regions (we host our galaxy from one region, but other regions have sped up… although galaxy speeds between regions is still pretty slow)
An interesting side effect that we want to confirm with a bit more analysis - but CPU and memory usage seem to have dropped for our galaxy containers since turning Cloudflare on.
You can use Cloudflare page rules to do the non ‘www’. route to the ‘www.’ route
Thanks for the help @vooteles vo and @ivo