Coder.comC
Coder.com3y ago
3 replies
dgdkfz

Agent is taking too long to connect - Starter template "Develop in Docker"

Hello everyone,
I am completely new to coder (and DevOps). When I want to start a workspace from one of the starter templates (in my case the "Develop in Docker"-container) the agent won´t start. Coder reports: "Agent is taking too long to connect We noticed this agent is taking longer than expected to connect. Troubleshoot.". Of course I followed the tipps of the troubleshoot (https://coder.com/docs/v2/latest/templates#troubleshooting-templates). However, ...
- curl is installed on the docker container that is started by coder as workspace, it can as well curl the coder start page from within the docker container
- in /tmp I can only find one directory called coder.v5Wj4i that does not contain any files. There is no coder-agent.log, coder-startup-script.log or coder-shutdown-script.log in tmp.
- to my knowledge there is also no reverse proxy in use. If I curl the server, the HTTP response gives no clues ("X-Forwarded-For", ...) for that as well. However, the console in Chrome gives back "Failed to load resource: the server responded with a status of 401 (Unauthorized)" and "index-be78aaa3.js:95 Refused to connect to 'https://aoanr3bf14ctk.pit-1.try.coder.app/latency-check?cache_bust=LJILQeC9' because it violates the following Content Security Policy directive: "connect-src 'self' wss://10.3.78.28:3000 ws://10.3.78.28:3000"."
Is there any way I can change the Content Security Policy of Coder? So far I have not found out how to do that in the docs. I installed coder via binary, so the binary file is in /usr/local/bin. Thanks for any help 🙂
Learn about templates, which define the infrastructure underlying workspaces
Templates - Coder v2 Docs
Was this page helpful?