You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when using an access URL without specifying a protocol, (e.g. --access-url=35.xxx.xxx.206), the Coder agent will default to dialing the server over HTTPS, causing the connection to hang:
⢎⡀ Waiting for connection from main ...
the fix here is to simply update the access URL to be --access-url=http://35.xxx.xxx.206. however, to prevent this behavior in the future, the Coder agent should default to HTTP (as curl does), or attempt to dial over both HTTP & HTTPS.
The text was updated successfully, but these errors were encountered:
Hmm... some context on the decision here: #2874. @ericpaulsen@ammario What are your thoughts if it only defaulted to HTTP if it was an IP address but HTTPS for domains?
Hmm... some context on the decision here: #2874. @ericpaulsen@ammario What are your thoughts if it only defaulted to HTTP if it was an IP address but HTTPS for domains?
This trade off makes sense to me. We could also fail to start if a domain is provided w/o a protocol.
when using an access URL without specifying a protocol, (e.g.
--access-url=35.xxx.xxx.206
), the Coder agent will default to dialing the server over HTTPS, causing the connection to hang:the fix here is to simply update the access URL to be
--access-url=http://35.xxx.xxx.206
. however, to prevent this behavior in the future, the Coder agent should default to HTTP (ascurl
does), or attempt to dial over both HTTP & HTTPS.The text was updated successfully, but these errors were encountered: