All twake servers run on a docker on one virtual machine and Apache is running on another virtual machine all on the same physical server…
I read the documentation https://doc.twake.app/configuration/custom-domain-and-https to setup Apache Proxy.
Everything works well thank you, except the messages which are not immediately available by the reader. The messages will appear only if the reader refresh the screen… And I continuously get you are offline…
The container port configuration of twake_nginx_01 is: 8086 -> 80. When I connect directly to the dockerserver:8086 everything is working well including the message… But does not work if it goes through the apache proxy.
Hello @huuich, the docs that you are referring to assume that you already have a proxy running, or want to set one up.
From your response, I think you do not yet have a reverse proxy running.
You can do that with a number of tools, but a pretty easy one is https://github.com/jc21/nginx-proxy-manager.
That gives you (yet another) web interface that you can use to set the proxy as you want it. This tool generates the applicable nginx reverse proxy config for you.
A minimal config would look like this:
(you should change the ip to match your situation)
domain name mydomain.com
protocol forward ip port
http 10.0.10.5 8000
You might also want to enable caching, block common exploits and enable websockets, and that should give you a working starting point. You can add the settings mentioned in an earlier post in advanced to get a bit better speed and responsiveness.
If you also want a lets encrypt certificate, that tool also gives you an easy way to generate one, but that is very dependent on your situation and the tool is pretty self explanatory.
So I’ve pasted the according configuration for configuration/frontend/environment.ts and configuration/backend/Parameters.php. What else do I need to get twake working via the nginx-proxy-manager? nginx-pm is already running and serving content to specific subdomains, but for some reason it doesn’t want to forward twake.
The simple steps @fvanlint recommended weren’t enough.
Any help?