After updating to the latest version of Discourse we now have a strange issue with ngix posting error 502. Some users get Error 502 when posting, some don’t. Some profiles get 502, some don’t. CPU usage is around 10 to 25%, RAM usage is about 20% as well. I tried disabling our 5 plugins, same res…

You can check the postgres version at /var/discourse/shared/standalone/postgres_data/PG_VERSION – If you did a command line upgrade, it’s possible that it did the upgrade and you didn’t notice (but you’d have to have run the rebuild twice). If you upgraded from the web interface, you should probably…

502 Bad Gateway after updating to latest version

Support

pfaffman (Jay Pfaffman) April 29, 2025, 7:39pm 10

Did you follow the advice in PostgreSQL 15 update? You might also vaccuum the database.

Topic		Replies	Views
Is there a step by step diagnostic for when a Discourse site is found in a 502 Bad Gateway? Installation	8	470	March 30, 2024
Brand new install, shows only "502 Bad Gateway" Support	3	25	April 16, 2025
502 Bad Gateway, suddenly Installation server-resources	10	4903	June 8, 2024
502: Bad Gateway after web update Support	18	5487	January 15, 2020
How to track down failure of discourse upstream inside container resulting in 502 Bad Gateway Installation	8	1091	January 23, 2024

502 Bad Gateway after updating to latest version

Related topics