Đạt_Hoàng is trying to configure NGINX in the Discourse Docker container to serve the forum at forum.example.com/forum while using forum.example.com for a static HTML page. After following instructions from a meta.discourse.org guide, they encountered an “ERR_TOO_MANY_REDIRECTS” error. pfaffman clarifies that Discourse already includes an internal NGINX server and asks what problem is being solved. Đạt_Hoàng confirms the goal is subfolder routing. pfaffman suggests an alternative guide: Serve Discourse from a subfolder. Đạt_Hoàng asks if this requires an enterprise hosted plan, to which pfaffman confirms that while enterprise hosting restricts this feature, self-hosted setups can implement it — though it’s discouraged due to complexity and lack of SEO benefit.
My Discourse forum is running at the address forum.example.com. I want to set up NGINX in the Discourse Docker container and followed the instructions here Run other websites on the same machine as Discourse
After completing the setup according to the instructions, I encountered an error “ERR_TOO_MANY_REDIRECTS”
My desire is to use forum.example.com/forum for the forum and forum.example.com for a HTML page.
I searched for a solution and found that I need to setup an extra nginx proxy in front of the Docker container.
I tried following the instructions above, but the result was not successful.
Yes, that is true for hosted customers. But if you read after this:
It describes how to do it on your own server. The admonitions that it is difficult, complicated, and not really recommended are all true, however. Most everyone now agrees that there is no SEO advantage to using a subfolder.