-
Notifications
You must be signed in to change notification settings - Fork 886
workspace proxies: unique health check error if being treated as a subdomain app #11116
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
Comments
@deansheather mind taking this one? |
This seems highly niche. We also output the appropriate values when you do
I am having trouble even setting this up. When you create a new proxy, it requests the
So you can't even start the workspace proxy here to set it up in the first place. |
Hey - I'm down to close this as not planned if this is a very unlikely setup. I don't know how to reproduce it. |
@bpmct I have already spent some time on this path, and I found some little things I can improve. I'll put up a PR or two, but I don't think I have the setup for this specific situation. |
Cli error improvements: #11584 |
Found the way to reproduce, had it backwards. Fixed |
Background
A customer may mistakenly put a proxy in the same DNS path as wildcard apps, where the wildcard app somehow takes priority.
e.g.
*.demo.coder.com
vsproxy.demo.coder.com
Proposal
Show a unique error in the health check to explain the conflict and resolution
The text was updated successfully, but these errors were encountered: