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
{{ message }}
Repository navigation
Web terminal does not re-connect when agent is restarted (spot VM) #5292
When an agent disconnects, we can't close all Coder server -> workspace connections because it could be intermittent. e.g. if you have multiple Coder replicas, one shuts off due to an upgrade but that was where the agent was connected, we don't want to lose all other client connections.
The agent should have an "instance ID" associated with itself to identify when a new instance popped up. When it does, we should publish to all replicas to close connections that are for the old identifier.
Activity
bpmct commentedon Dec 5, 2022
I also ran into this with a template that creates workspaces as Kubernetes deployments, and then I deleted the pod. It re-created and the agent connected, but the web terminal never connected. I was able to connect over SSH okay. Agent logs
bpmct commentedon Jan 25, 2023
I'm also noticing this when I run
sudo rebooton an AWS VM.fix(wsconncache): only allow one peer per connection (#5886)