This section will contain common problems and how to resolve them. It will grow over time once there are more issues reported.
- Update the Devilbox
Issues are constantly being fixed. Before attempting to spend too much time digging into your issue, make sure you are running the latest git changes and have pulled the latest Docker images.
Also keep in mind that configuration files might change, so ensure to diff the default ones against your currently active ones for added, removed or changed values.
Table of Contents
- DNS issues
- SSL issues
- Web server issues
- PHP issues
- Database issues
In case something stopped working for no reason, check out other Docker container. If you experience similar issues as well, check for any unattended Windows updates or updates to Docker itself. If those exist, try to revert them and see if that was the cause.
I heard many bug stories from fellow Windows users so far. A good contact point for that is the Docker forum itself: https://forums.docker.com/c/docker-for-windows
A few general things you should always do before attempting to open up issues are:
1. Used default settings from env-example
Try using the exact settings from
env-exampleas variables might have been updated in git.# Ensure everything is stopped host> cp env-example .env
2. Clean, updated and minimal start
# Ensure everything is stopped host> docker-compose stop host> docker-compose kill host> docker-compose rm -f # Ensure everything is updated host> docker-compose pull # Start again host> docker-compose up php httpd bind
3. Reset Docker credentials:
As it might sound strange, this fix might indeed solve a lot of problems on Windows. Go to your Docker settings and reset your credentials.
4. Shared volumes:
Ensure all your Devilbox data (Devilbox directory and project directory) are within the volumes that are shared by Docker. If not add those in the Docker settings.
One of the Docker container wants to bind to a port on the host system which is already taken.
Figure out what service is listening on your host system and shut it down or change the port
of the affected service in the Devilbox
Some examples of common error messages:
Error starting userland proxy: Bind for 0.0.0.0:80: unexpected error (Failure EADDRINUSE)
If you are using Docker Toolbox, the Devilbox intranet is not available on localhost or 127.0.0.1, but rather on the IP address of the Docker Toolbox machine.
This simply means your Docker and/or Docker Compose versions are outdated.
bind_1 | /etc/bind/devilbox-wildcard_dns.localhost.conf:1: zone 'localhost': already exists previous definition: /etc/bind/named.conf.default-zones:10
This error occurs when using
localhost as the TLD_SUFFIX.
Errors occurred when trying to connect to www.example.com: cURL error 77: error setting certificate verify locations: CAfile: certificate ./ca/cacert.pem CApath: /etc/ssl/certs
This issue might arise if you set TLD_SUFFIX to an official top level domain such as
What happens is that the bundled DNS server does a catch-all on the TLD and redirects all name
resolution to the Devilbox’s PHP container IP address.
If you want to access
https://www.example.com in that case, the request goes to the PHP
container which does not have a valid SSL certificate for that domain.
Do not user official TLD’s for TLD_SUFFIX.
This error is most likely to only occur on Docker for Windows and is just a result of not working volumes mounts.
This error might occur for the Devilbox intranet or custom created projects.
On of the cause could be wrongly set file and directory permissions.
First ensure the cloned git directory is readable for users, groups and others.
For the Devilbox intranet, ensure the
.devilbox/ directory is readable for users, groups and
others. Also check files and directories within.
For projects, ensure an
index.html exists and that all files and directories
are readable for users, groups and others.
This error occurs when the upstream PHP-FPM server takes longer to execute a script, than the timeout value set in the web server for PHP-FPM to answer.
For that to fix one must increase the PHP-FPM/Proxy timeout settings in the
If you encounter this error, it is most likely that your current project declares the
go() and that you have enabled the
swoole module which also provides
an implementation of that function.
To mitigate that issue, make sure that the
swoole module is disabled in
This error might occure after changing the path of MySQL, PgSQL, Mongo or any other data directory.
When you change any paths inside
.env that affect Docker mountpoints, the container need to be
removed and re-created during the next startup.
Removing the container is sufficient as they will always be created during run if they don’t exist.
In order to remove the container do the following:
host> cd path/to/devilbox host> docker-compose stop # Remove the stopped container (IMPORTANT!) # After the removal it will be re-created during next run host> docker-compose rm -f
This warning might occur when using Docker Toolbox and the Devilbox on Windows and trying to apply custom MySQL configuration files. This will also result in the configuration file not being source by the MySQL server.
To fix this issue, you will have to change the file permission of your custom configuration files
to read-only by applying the following
# Nagivate to devilbox git directory host> cd path/to/devilbox # Navigate to the MySQL config directory (e.g.: MySQL 5.5) host> cd cfg/mysql-5.5 # Make cnf files read only host> chmod 0444 *.cnf