NGINX 502 Bad Gateway after v9.3 upgrade

resolved Mattermost upgrade Reported 2026-02-10 Verified 2026-03-04

After upgrading Mattermost to v9.3, users get 502 errors when the upstream proxy timeout is too low for the new WebSocket handling.

Error Messages
502 Bad Gatewayupstream timed out
Versions: 9.39.3.1
OS: ubuntu-24.04debian-12
Deployment: dockerbare-metal

Resolutions (1)

high confidence 47 verified

Increase NGINX proxy timeouts in your site config:

proxy_read_timeout 600;
proxy_send_timeout 600;
proxy_connect_timeout 600;

Then reload NGINX: sudo nginx -s reload

Verified by 47 users on matching versions Added 2026-02-15
Applies to: 9.3, 9.3.1 on docker, bare-metal
/ Search Esc Clear ? Sitemap
24 tools / 3 guides / 9 resolved issues