# 502 Bad Gateway for only two Topics

**URL:** <https://meta.discourse.org/t/502-bad-gateway-for-only-two-topics/242981>\
**Category:** Self-hosting\
**Tags:** arm\
**Created:** [October 26, 2022, 4:24pm UTC](https://meta.discourse.org/t/502-bad-gateway-for-only-two-topics/242981 "2022-10-26T16:24:48Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![niccokunzmann](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/niccokunzmann/32/131771_2.png) [@niccokunzmann](https://meta.discourse.org/u/niccokunzmann)\
**Post date:** [November 15, 2022, 11:19pm UTC](https://meta.discourse.org/t/502-bad-gateway-for-only-two-topics/242981/20 "2022-11-15T23:19:29Z")

</div>

My question at the moment is: Is there a way to increase the time-out for nginx from say the 30 seconds to about two minutes? This would solve it probably.

- [https://stackoverflow.com/questions/63801913/nginx-timeout-20s-causes-502-bad-gateway](https://stackoverflow.com/questions/63801913/nginx-timeout-20s-causes-502-bad-gateway)
- templates/web.letsencrypt.ssl.template.yml - accesses the nginx config
- [Module ngx\_http\_proxy\_module](https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_read_timeout)

My conclusion is that I can write a template that adds a .conf file to `/etc/nginx/sites-enabled/` that sets the timeouts.

* * *

Also, I noticed that I observe this 502 with a higher likelihood when an answer was posted. My guess is that the forum needs to rebuild the page and that takes a while. Is this correct? I wonder: can I trigger a rebuild of a discourse page manually?

---

_[View the full topic](https://meta.discourse.org/t/502-bad-gateway-for-only-two-topics/242981)._