Linux with Docker CE
Windows 10 Pro, Enterprise or Education with Docker for Windows
Windows with Docker Toolbox
Mac with Docker for Mac
We provide a docker-compose configuration:
There are 3 alternatives:
docker-compose.yml with the following containers:
Caddy as reverse proxy to support HTTPS. Also issues the certificate.
The caddy proxy uses a custom image to configure the Caddyfile.
docker-compose-nginx.yml with the following containers:
NGINX as reverse proxy to support HTTPS
NGINX sidecar to provision free and secure certificates with LetsEncrypt.
The NGINX proxy uses a custom image to increase the size of the http headers.
docker-compose-noproxy.yml with the following containers:
Download the following files to your server:
.env file and set the following variables:
Your domain name, e.g. we use
The email address of the admin user.
The password of the admin user. Must contain a lowercase and uppercase letter, a number and a special character. Leaked passwords are also forbidden, check https://haveibeenpwned.com/Passwords first.
Keep it unchanged. You can set it to false to disable permanent redirects from http to https.
Keep it unchanged. You can set it to http to disable secure connections.
You can keep the other settings empty for now.
The data will be stored outside of the docker container to simplify the backups. The default path /etc/squidex will be created by docker.
docker-compose up -d
Please check the logs first using docker.
docker ps # Get the container id firstdocker logs <CONTAINER-ID> # Read the logs
In my tests it took sometime to issue the certificate. Probably around 10 minutes.
Also ensure that your DNS server is configured correctly.
In some cases, especially on CentOS 7, the communication between docker containers on the same host is blocked by the firewall. There is an open issue on Github for this problem.
The solution that worked in our cases was to add https as a service to the firewall:
sudo firewall-cmd --add-service=https --permanent --zone=trustedsudo firewall-cmd --reload
This problem is because you use an host name or IP address that is not reachable from the docker itself. You can think about the Squidex being two processes in one application. There is the OpenID Connect Server (Identity Server) that generates the access tokens and the API. When the API receives an access token it makes a request to the Identity Server to validate the token (See following diagram).
When you use a local host name or IP address such as
127.0.0.1your are referring to the host name. But containers inside docker cannot resolve the network routes and therefore the authentication flow fails. The solution is to either use another local hostname, that you have to configure in the host file of your Operation system or to use a real hostname, such as a public domain name.
It is very likely a configuration problem and not related to hosting under Docker. Checkout