Agent suddenly not connecting due to `/api/v2/workspaceagents/aws-instance-identity` 404 / 400
This is the case both for new workspaces and for existing workspaces that worked yesterday.
The workspace agent log is attached, the relevant bit is:
5 Replies
I ran into the same issue as well.
The strange thing is, if I don’t specify a domain, it automatically uses a coder.app domain, and through that domain, the workspace can be created successfully ,the agent works fine in that case.
What are you doing to not specify a domain @alex ?
If I comment out my
CODER_ACCESS_URL I do see the agent trying to connect to https://myassignedproxy.pit-1.try.coder.app but it still gets a 400Potentially related to https://github.com/coder/coder/issues/20704
GitHub
bug: aws-instance-identity fails intermittently on v2.27.3 · Issue...
Is there an existing issue for this? I have searched the existing issues Current Behavior After upgrading to Coder v2.27.3, workspace agents fail to authenticate intermittently when using aws-insta...
The only way I was able to get around this issue was to roll back before the 2.7 update to 2.6.3
This has been fixed:
https://github.com/coder/coder/issues/20704#issuecomment-3518894266
GitHub
bug: aws-instance-identity fails intermittently on v2.27.3 · Issue...
Is there an existing issue for this? I have searched the existing issues Current Behavior After upgrading to Coder v2.27.3, workspace agents fail to authenticate intermittently when using aws-insta...