Running your Cells Docker container behind a reverse proxy
In this tutorial, we explain how you can configure a reverse proxy for your Cells Docker container and what settings are the most important to change.
Run your Cells docker Container behind an Apache reverse Proxy using SSL¶
The process is pretty much the same as the example on reverse proxying with apache (you can apply those principles with every proxy),
when you run your docker container either with the command docker run
or in a docker-compose file, you have to specify CELLS_BIND
and CELLS_EXTERNAL
.
Here's what CELLS_BIND and CELLS_EXTERNAL mean to give a you a general understanding.
Side Note: The Sync Client requires an extra port that you will have to expose, Read this article
To illustrate the concept above an example is provided (this example show a reverse proxy on the same server but in the case of a different server, the cells_external
value must be the one ).
For instance you have your cells container running on a server that has an address such as : 192.168.1.12
you decide to run your container on port 7070
and therefore to run your container behind the proxy you will have to set:
CELLS_BIND = 192.168.1.12:7070
and CELLS_EXTERNAL = 192.168.1.12
(can be done in the docker-compose or as environment variables in the docker run command).
Then create configuration file for apache proxy (if used as it is , it will work when you have ssl enabled on both the proxy and cells) with the following:
you can apply the same set of rules for nginx, caddy etc... .