Default docker-code-server template is stuck on connecting

Hey all, I am trying to test coder but it just says connecting. I have tried both 127.0.0.1, the IP of the server and the external url as the CODER_ACCESS_URL but none seem to make it work.

Screen_Shot_2022-09-14_at_9.44.48_am.png

bpmct•9/14/22, 12:31 AM

Hmm... Can you check the logs of the container?

dorkbydesignOP•9/14/22, 1:26 AM

Thanks for following up, Ben. We've managed to figure it out. Turns out we needed to set our

CODER_ACCESS_URL

CODER_ACCESS_URL

to our localhost URL and also enable WebSocket forwarding/upgrade in nginx as per https://www.nginx.com/blog/websocket-nginx/

NGINXWeb Team

Using NGINX as a WebSocket Proxy

Learn how to use NGINX as a reverse proxy and load balancer for WebSocket applications

dorkbydesignOP•9/14/22, 1:26 AM

Hope this helps someone else with the same issue!

Ddorkbydesign Thanks for following up, Ben. We've managed to figure it out. Turns out we neede...

Phorcys•9/14/22, 5:10 AM

that shouldn't be the case though

Phorcys•9/14/22, 5:10 AM

my access url is my domain here

Phorcys•9/14/22, 5:10 AM

i'm afraid that setting your access URL to localhost will break stuff in the future

bpmct•9/14/22, 5:52 PM

Ideally, you'd set access URL to the domain / external IP of the server, yeah. As long as Coder/nginx is being served there it should work.

bpmct•9/14/22, 5:52 PM

The localhost access URLs will only work with Docker-based templates

Bbpmct The localhost access URLs will only work with Docker-based templates

Phorcys•9/15/22, 7:12 AM

well, it would work in others if you replaced in those too, no ?

bpmct•9/15/22, 5:14 PM

I guess if you changed the replace to the IP instead of . At that point, you should set an access URL, though

Phorcys•9/15/22, 5:30 PM

yeh