The link he keeps spamming is what we’re already doing:
these steps will work on any Docker-compatible cloud provider or local server.
He is running the standard container. The docs mention using a “Docker compatible” box, which he is using. The docs even mention using a local server, which he’s using.
There is no mention of using a special approved proxy or disabling caching.
There is also docs for configuring SSO, which seems to have caused similar issues to what we’re experiencing in the past:
Still no mention of caching configuration or “custom” reverse proxy solutions.
At minimum I would suggest updating the documentation to highlight these potential issues, since they’re so obvious to Discourse experts.