ddev: wsl pre-release 1.1.0.0 has trouble: ddev-routing ports 80 and 443 error

Is there an existing issue for this?

I have searched the existing issues

Run a Diagnostic and Paste Link Here

Hi everyone, when i try run ddev start i have this problem:

Error response from daemon: Ports are not available: exposing port TCP 127.0.0.1:443 -> 0.0.0.0:0: listen tcp 127.0.0.1:443: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted. Failed to start xxxxx: failed to start ddev-router: ComposeCmd failed to run 'COMPOSE_PROJECT_NAME=ddev-xxxxx docker-compose -f /home/xxxxx/.ddev/.router-compose-full.yaml -p ddev-router up -d', action='[-p ddev-router up -d]', err='exit status 1', stdout='', stderr='Container ddev-router Creating Container ddev-router Created Container ddev-router Starting Error response from daemon: Ports are not available: exposing port TCP 127.0.0.1:443 -> 0.0.0.0:0: listen tcp 127.0.0.1:443: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.'

Expected Behavior

start ddev -.-

Actual Behavior

not start ddev -.-

Steps To Reproduce

No response

Anything else?

No response

About this issue

Original URL
State: closed
Created a year ago
Comments: 31 (12 by maintainers)

Commits related to this issue

Add recreation of mutagen sync session if mutagen.yml changes, fixes #4573 — committed to rfay/ddev by rfay a year ago
Add recreation of mutagen sync session if mutagen.yml changes, fixes #4573 — committed to rfay/ddev by rfay a year ago
Add recreation of mutagen sync session if mutagen.yml changes, fixes #4573 — committed to rfay/ddev by rfay a year ago
Add recreation of mutagen sync session if mutagen.yml changes, fixes #4573 — committed to rfay/ddev by rfay a year ago
Add recreation of mutagen sync session if mutagen.yml changes, fixes #4573 — committed to rfay/ddev by rfay a year ago
Add recreation of mutagen sync session if mutagen.yml changes, fixes #4573 — committed to rfay/ddev by rfay a year ago
Add recreation of mutagen sync session if mutagen.yml changes, fixes #4573 — committed to rfay/ddev by rfay a year ago
Add recreation of mutagen sync session if mutagen.yml changes, fixes #4573 — committed to rfay/ddev by rfay a year ago

Most upvoted comments

@azovsky those files are created every time you ddev start. The most common reason for having trouble with port 443 though is that something is listening on it. See https://ddev.readthedocs.io/en/latest/users/usage/troubleshooting/#web-server-ports-already-occupied

And yes, a variety of problems with WSL2 have popped up lately, including

#4809

rfay on Apr 14, 2023

I imagine you’re all have a prerelease version of WSL higher than 1.0.3.0 (`wsl --version)

https://github.com/microsoft/WSL/issues/9508#issuecomment-1396866615 and you’ll need to downgrade to wsl 1.0.3.0 using the instructions in
https://github.com/microsoft/WSL/issues/9516#issuecomment-1400254692

rfay on Jan 24, 2023

I’d love to hear from all why you were using wsl --update --pre-release, was there another problem you were chasing? I was also tempted by a different bug fix.

Related Discord conversation: https://discord.com/channels/664580571770388500/1065984069751554048

I didn’t do wsl --update --pre-release

WSL got updated automatically from the Microsoft Store

damchey on Jan 24, 2023

Hi @gabrielpaoli - There’s a full set of debugging and mitigation instructions for this problem in https://ddev.readthedocs.io/en/latest/users/usage/troubleshooting/

You didn’t provide the requested ddev debug test so I don’t have any more I can offer. Normally there’s a check for these ports that gives you a link to that doc. Could you please do the ddev debug test and put the results in a gist on gist.github.com and update the issue?

The problem is you have something else running on port 443. You may be able to figure out what it is with curl https://localhost. Sometimes Docker Desktop gets confused as well, and restarting Docker Desktop can be an answer.

rfay on Jan 21, 2023