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

DAB stopped listening at https://localhost:5001 after 2025-01 updates on Windows Server 2022 21H2 #2525

Open
GustavBrock opened this issue Jan 15, 2025 · 2 comments
Labels
cri Customer Reported issue

Comments

@GustavBrock
Copy link

I have a Cloudflared tunnel listening at https://localhost:5001 which failed after this night's regular Windows update.

A restart of DAB showed that it listened to http://localhost:5000.
I modified the tunnel to listen to that host, and at once the API was again accessible.

But where did https://localhost:5001 go? I have no clue.

dab.exe is version 0.9.7.0

@JerryNixon JerryNixon added the cri Customer Reported issue label Jan 24, 2025
@JerryNixon
Copy link
Contributor

JerryNixon commented Jan 24, 2025

@GustavBrock why not upgrade to dab.exe version 1.3?

I ask this because version 0.9 is pre-release and very far behind on bug and security fixes.

@GustavBrock
Copy link
Author

@JerryNixon Simple answer: It ain't broke (here), so why fix it? So much else to do. But, of course, added to the to-do list. Thank you.

By the way, the happening could be related to the Known Issue posted by you: https://localhost:5001 not in Console Logs after dab start #2237 as I recall I had the setting applied that you posted as a work-around. Somehow it was lost; I considered to reapply it but found it simpler to "go with the defaults" and change the listening port of Cloudflared.

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

No branches or pull requests

2 participants