Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTPS doesn't work under mirrored network mode. #11629

Closed
1 of 2 tasks
xky0007 opened this issue May 29, 2024 · 5 comments
Closed
1 of 2 tasks

HTTPS doesn't work under mirrored network mode. #11629

xky0007 opened this issue May 29, 2024 · 5 comments

Comments

@xky0007
Copy link

xky0007 commented May 29, 2024

Windows Version

Microsoft Windows [Version 10.0.22631.3593]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.146.1-2

Distro Version

Ubuntu 24.04

Other Software

Docker Desktop v4.30.0

Repro Steps

  1. Set WSL to use mirrored network mode
  2. Deploy portainer docker run -d -p 8000:8000 -p 9443:9443 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest
  3. Access localhost:9000 and https://localhost:9443

Expected Behavior

Both http and https portainer server should work.

Actual Behavior

https servser shows error while http server page can be reached.
image

Diagnostic Logs

No response

Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@xky0007
Copy link
Author

xky0007 commented May 29, 2024

Copy link

Diagnostic information
.wslconfig found
Detected appx version: 2.1.5.0
Error while parsing the logs. See action page for details

@ghost
Copy link

ghost commented Jun 4, 2024

I don't see any logs inside that zip? Did you let log collection run while wsl and the web service start up?

What's the output of sudo ss -lntp?

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants