-
Notifications
You must be signed in to change notification settings - Fork 881
Warn users if their access URL is localhost or 127.0.0.1 #1528
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
This seems like a ticket that should be complete for the CE milestone. Nice details @bpmct ! |
Adding this to community in case Lucy gets free time to work on it. It may need to be brought in later depending on load. |
I implemented this as a warning, rather than an error, because we don't know with certainty that a localhost access URL is an invalid configuration. For one thing -- as the message points out -- even if the default access URL uses a loopback address, individual templates could override it. That's what our example Docker template does (replacing |
Agreed. I think a warning is definitely preferable here. |
Ah, I just noticed I used the word "error" in the description but "warning" in the title. I'll look out for that. |
What is your suggestion?
When
coder server
orcoder templates create
is run (unsure which is best), I suggest displaying an error:I was chatting with @kylecarbs about this on Discord:
Why do you want this feature?
When workspaces are created, the Coder agent on the workspace needs to dial the Coder access URL. If the access url is a loopback address, then the workspace would end up dialing itself instead of the control plane.
Resources will just start and hang on
Waiting for connection from dev
.Related: #1345
Are there any workarounds to get this functionality today?
Each example template we provide could include a warning. Templates only leverage resources on the host (e.g docker) can also override the access URL, as done for the
docker
template in #1507. However, no public cloud templates would work unless Coder is exposed.Somewhat related: #1176 would allow users to tunnel within Coder itself without the need to use up ngrok, Caddy, or another service to publish and secure a Coder access URL. However, it's a complex undertaking.
The text was updated successfully, but these errors were encountered: