General Troubleshooting Strategies
- Start with a
ddev poweroffto make sure all containers can start fresh.
- Temporarily turn off firewalls and virus checkers while you're troubleshooting.
- If you have customizations (PHP overrides, nginx or Apache overrides, MySQL overrides, custom services, config.yaml changes) please back them out while troubleshooting. It's important to have the simplest possible environment while troubleshooting.
- Restart Docker. Consider a Docker factory reset in serious cases (this will destroy any databases you've loaded). See Docker Troubleshooting for more.
- Try the simplest possible ddev project to try to get i to work:
ddev poweroff && mkdir ~/tmp/testddev && cd ~/tmp/testddev && ddev config --project-type=php && ddev start. Does that start up OK? If so, maybe something is wrong with the more complicated project you're trying to start.
Webserver ports are already occupied by another webserver
ddev notifies you about port conflicts with this message:
Failed to start yoursite: Unable to listen on required ports, localhost port 80 is in use,
This means there is another webserver listening on the named port(s) and ddev cannot access the port.
(In some cases the conflict could be over port 8036 (PHPMyAdmin) or port 8025 (mailhog)).
To resolve this conflict, choose one of two methods:
- If you are using another local development environment (MAMP, WAMP, lando, etc.) that uses these ports, consider stopping it.
- Fix port conflicts by configuring your project to use different ports.
- Fix port conflicts by stopping the competing application.
Method 1: Fix port conflicts by configuring your project to use different ports
To configure a project to use non-conflicting ports, edit the project's .ddev/config.yaml to add entries like
router_http_port: 8000 and
router_https_port: 8443 depending on your needs. Then use
ddev start again.
For example, if there was a port conflict with a local apache http on port 80 add the following to the to the config.yaml file.
ddev start. This changes the project's http URL to http://yoursite.ddev.site:8000.
If the conflict is over port 8025, it's normally a conflict over the default port for mailhog. You can add to your .ddev/config.yaml
If the conflict is over port 8036, it's normally about PHPMyAdmin, and you can add to your .ddev/config.yaml
Method 2: Fix port conflicts by stopping the competing application
Alternatively, stop the other application.
Probably the most common conflicting application is Apache running locally. It can often be stopped gracefully (but temporarily) with:
sudo apachectl stop
Common tools that use port 80:
Here are some of the other common processes that could be using port 80 and methods to stop them.
- MAMP (macOS): Stop MAMP
- Apache: Temporarily stop with
sudo apachectl stop, permanent stop depends on your environment.
- nginx (macOS Homebrew):
sudo brew services stop nginxor
sudo launchctl stop homebrew.mxcl.nginx
- nginx (Ubuntu):
sudo service nginx stop
- apache (often named "httpd") (many environments):
sudo apachectl stopor on Ubuntu
sudo service apache2 stop
- vpnkit (macOS): You likely have a docker container bound to port 80, do you have containers up for Kalabox or another docker-based development environment? If so, stop the other environment.
- Kalabox: If you have previously used Kalabox try running
To dig deeper, you can use a number of tools to find out what process is listening.
On macOS and Linux, try the lsof tool:
$ sudo lsof -i :80 -sTCP:LISTEN COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME nginx 1608 www-data 46u IPv4 13913 0t0 TCP *:http (LISTEN) nginx 5234 root 46u IPv4 13913 0t0 TCP *:http (LISTEN)
On Windows CMD, try using netstat and tasklist to find the pid:
> netstat -aon | findstr ":80.*LISTENING" TCP 127.0.0.1:80 0.0.0.0:0 LISTENING 5760 TCP 127.0.0.1:8025 0.0.0.0:0 LISTENING 5760 TCP 127.0.0.1:8036 0.0.0.0:0 LISTENING 5760 > tasklist | findstr "5760" com.docker.backend.exe 5760 Services 0 9,536 K
The resulting output displays which command is running and its pid. Choose the appropriate method to stop the other server.
We welcome your suggestions based on other issues you've run into and your troubleshooting technique.
DDEV-Local reports container restarts and does not arrive at "ready"
Restarts of the database container
The most common cause of the database container not coming up is a damaged database, so the mariadb server daemon is unable to start. This is typically caused by an unexpected docker event like system shutdown or docker exit which doesn't give the db container time to clean up and close connections. See issue. In general, the easiest fix is to destroy and reload the database from either a database dump or a ddev snapshot. Otherwise, that issue has more ambitious approaches that may be taken if you have neither. But the easiest approach is this, which will destroy and then reload your project database:
ddev stop --remove-data --omit-snapshot
- mv .ddev .ddev.bak (renames the directory with config.yaml and docker-compose.yml and any custom nginx/php/mariadb config you may have added. Renaming it means .)
ddev restore-snapshot <snapshot-name>if you have a db to import or a snapshot to restore.
Another approach to destroying the database is to destroy the docker volume where it is =stored with
docker volume rm <projectname>-mariadb
"web service unhealthy" or "web service starting" or exited
The most common cause of the web container being unhealthy is a user-defined .ddev/nginx-site.conf or .ddev/apache/apache-site.conf - Please rename these to
ddev logs and review the error.
Changes to .ddev/nginx-site.conf and .ddev/apache/apache-site.conf take effect only when you do a
ddev restart or the equivalent.
No input file specified (404) or Forbidden (403)
If you get a 404 with "No input file specified" (nginx) or a 403 with "Forbidden" (apache) when you visit your project it may mean that no index.php or index.html is being found in the docroot. This can result from:
- Missing index.php: There may not be an index.php or index.html in your project.
- Misconfigured docroot: If the docroot isn't where the webserver thinks it is, then the webserver won't find the index.php. Look at your .ddev/config.yaml to verify it has a docroot that will lead to the index.php. It should be a relative path from the project root to the directory where the index.php is.
- Docker not mounting your code: If you
lsand there's nothing there, Docker may not be mounting your code. See docker installation for testing docker install. (Is Docker, the drive or directory where your project is must be shared. In Docker Toolbox it must be a subdirectory of your home directory unless you make special accommodations for Docker Toolbox).
ddev start fails and logs contain "failed (28: No space left on device)" - Docker File Space
ddev start fails, it's most often because the web container or db container fails to start. In this case the error message from
ddev start says something like "Failed to start
to find out why it failed". You canddev logs -s db` to find out what happened.
If you see any variant of "no space left on device" in the logs when using Docker Desktop, it means that you have to increase or clean up Docker's file space. To increase the allocated space, go to "Resources" in Docker's Preferences as shown in
If you see "no space left on device" on Linux, it most likely means your filesystem is full.
Windows Hosts File limited to 10 hosts per IP address line
On Windows only, there is a limit to the number of hosts that can be placed in one line. But since all ddev hosts are typically on the same IP address (typically 127.0.0.1, localhost), they can really add up. As soon as you have more than 10 entries there, your browser won't be able to resolve the addresses beyond the 10th entry.
There are two workarounds for this problem:
ddev stop --alland
sudo ddev hostname --remove-inactiveto prune the number of hosts on that hosts-file line. When you start a project, the hostname(s) associated with that project will be added back again.
- Manually edit the hosts file (typically
C:\Windows\System32\drivers\etc\hosts) and put some of your hosts on a separate line in the file.
Support options has a variety of options.