The Forum giving 502 Bad Gateway Error discussion revolves around resolving a sudden error on a Discourse forum. Helical_Insight initially reports the issue, sharing a screenshot of the 502 Bad Gateway Error. RGJ suggests rebooting the system and checking disk space, but these steps do not resolve the issue. Helical_Insight confirms that the issue persists across different systems.
Further investigation reveals that when the forum is operational, posting answers is not working, resulting in an Internal Server error. Helical_Insight shares another screenshot to illustrate this point. Later, RGJ notes that the forum is working, albeit slowly. However, Helical_Insight reports that posting answers is still not possible, sharing a log file error. pfaffman inquires about the server’s specifications, including CPU speed, RAM, and disk type, to further troubleshoot the issue.
First, try to reboot the system and see if it resolves the issue.
If it does not, check your disk space.
(Or you can do it the other way around).
Hello Richard,
Thank you for your quick reply. We have tried the way which you mentioned and we also tried in different system but we are facing the same problem(502 Bad Gateway). What else we can do?
What does this mean?
So did you check your disk space?
We also tried in different system(Which means when we are trying to visit our forum url on different Machines(Laptops)) it is giving the same issue.
When the forum is up and running without 502 Bad Gateway at that time posting the answer to the question is not working it is giving Internal Server error. For clear understanding below is the screenshot.
Thank You
It seems to be working now although it’s very slow.
It’s working but we are not able to post the answer. Below is the log file error we are getting
How fast is the CPU? How much RAM? Are the disks SSD?
