Websocket write errors

[fatmcgav]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

Overview of the Issue

Errors observed in logs relating to writing to websockets when using the UI

Reproduction Steps

• Watch job logs via UI

Logs

Logs

{"level":"warn","ts":"2026-02-12T09:06:01.534Z","caller":"websocket/writer.go:40","msg":"Failed to write ws message: write tcp 10.10.46.29:4141->10.10.46.26:48640: write: broken pipe","json":{},"stacktrace":"github.com/runatlantis/atlantis/server/controllers/websocket.(*Writer).Write\n\tgithub.com/runatlantis/atlantis/server/controllers/websocket/writer.go:40\ngithub.com/runatlantis/atlantis/server/controllers/websocket.(*Multiplexor).Handle\n\tgithub.com/runatlantis/atlantis/server/controllers/websocket/mux.go:81\ngithub.com/runatlantis/atlantis/server/controllers.(*JobsController).getProjectJobsWS\n\tgithub.com/runatlantis/atlantis/server/controllers/jobs_controller.go:70\ngithub.com/runatlantis/atlantis/server/controllers.(*JobsController).GetProjectJobsWS\n\tgithub.com/runatlantis/atlantis/server/controllers/jobs_controller.go:86\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2322\ngithub.com/gorilla/mux.(*Router).ServeHTTP\n\tgithub.com/gorilla/mux@v1.8.1/mux.go:212\ngithub.com/urfave/negroni/v3.(*Negroni).UseHandler.Wrap.func1\n\tgithub.com/urfave/negroni/v3@v3.1.1/negroni.go:59\ngithub.com/urfave/negroni/v3.HandlerFunc.ServeHTTP\n\tgithub.com/urfave/negroni/v3@v3.1.1/negroni.go:33\ngithub.com/urfave/negroni/v3.middleware.ServeHTTP\n\tgithub.com/urfave/negroni/v3@v3.1.1/negroni.go:51\ngithub.com/runatlantis/atlantis/server.(*RequestLogger).ServeHTTP\n\tgithub.com/runatlantis/atlantis/server/middleware.go:70\ngithub.com/urfave/negroni/v3.middleware.ServeHTTP\n\tgithub.com/urfave/negroni/v3@v3.1.1/negroni.go:51\ngithub.com/urfave/negroni/v3.(*Recovery).ServeHTTP\n\tgithub.com/urfave/negroni/v3@v3.1.1/recovery.go:210\ngithub.com/urfave/negroni/v3.middleware.ServeHTTP\n\tgithub.com/urfave/negroni/v3@v3.1.1/negroni.go:51\ngithub.com/urfave/negroni/v3.(*Negroni).ServeHTTP\n\tgithub.com/urfave/negroni/v3@v3.1.1/negroni.go:111\nnet/http.serverHandler.ServeHTTP\n\tnet/http/server.go:3340\nnet/http.(*conn).serve\n\tnet/http/server.go:2109"}
{"level":"error","ts":"2026-02-12T09:06:01.534Z","caller":"controllers/jobs_controller.go:95","msg":"writing to ws bd7337a3-ba2f-4cee-a59c-4ac2bf47cdd9: write tcp 10.10.46.29:4141->10.10.46.26:48640: write: broken pipe","json":{},"stacktrace":"github.com/runatlantis/atlantis/server/controllers.(*JobsController).respond\n\tgithub.com/runatlantis/atlantis/server/controllers/jobs_controller.go:95\ngithub.com/runatlantis/atlantis/server/controllers.(*JobsController).getProjectJobsWS\n\tgithub.com/runatlantis/atlantis/server/controllers/jobs_controller.go:73\ngithub.com/runatlantis/atlantis/server/controllers.(*JobsController).GetProjectJobsWS\n\tgithub.com/runatlantis/atlantis/server/controllers/jobs_controller.go:86\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2322\ngithub.com/gorilla/mux.(*Router).ServeHTTP\n\tgithub.com/gorilla/mux@v1.8.1/mux.go:212\ngithub.com/urfave/negroni/v3.(*Negroni).UseHandler.Wrap.func1\n\tgithub.com/urfave/negroni/v3@v3.1.1/negroni.go:59\ngithub.com/urfave/negroni/v3.HandlerFunc.ServeHTTP\n\tgithub.com/urfave/negroni/v3@v3.1.1/negroni.go:33\ngithub.com/urfave/negroni/v3.middleware.ServeHTTP\n\tgithub.com/urfave/negroni/v3@v3.1.1/negroni.go:51\ngithub.com/runatlantis/atlantis/server.(*RequestLogger).ServeHTTP\n\tgithub.com/runatlantis/atlantis/server/middleware.go:70\ngithub.com/urfave/negroni/v3.middleware.ServeHTTP\n\tgithub.com/urfave/negroni/v3@v3.1.1/negroni.go:51\ngithub.com/urfave/negroni/v3.(*Recovery).ServeHTTP\n\tgithub.com/urfave/negroni/v3@v3.1.1/recovery.go:210\ngithub.com/urfave/negroni/v3.middleware.ServeHTTP\n\tgithub.com/urfave/negroni/v3@v3.1.1/negroni.go:51\ngithub.com/urfave/negroni/v3.(*Negroni).ServeHTTP\n\tgithub.com/urfave/negroni/v3@v3.1.1/negroni.go:111\nnet/http.serverHandler.ServeHTTP\n\tnet/http/server.go:3340\nnet/http.(*conn).serve\n\tnet/http/server.go:2109"}

Environment details

• Atlantis version: 0.40.0
• Deployment method: EKS Helm
• If not running the latest Atlantis version have you tried to reproduce this issue on the latest version: N/A

Additional Context

[dosubot]

This is a common issue in Atlantis, especially when deployed on Kubernetes/EKS with Helm. The "broken pipe" websocket write errors usually mean the client (browser) disconnected or the connection was interrupted while Atlantis was streaming logs to the UI. This is often caused by load balancers, ingress controllers, or proxies that aren't configured to support websocket upgrades or session affinity, leading to dropped connections during log streaming.

To mitigate this, make sure your ingress or load balancer is set up for websocket support. For nginx, this means setting proxy_http_version 1.1, proxy_set_header Upgrade $http_upgrade, and proxy_set_header Connection "Upgrade" for the relevant paths. Disabling security proxies (like oauth2-proxy) for /jobs endpoints has also resolved the issue for some users. These configuration changes are discussed in detail in community threads and have resolved similar problems for others running Atlantis on EKS/Helm environments [1] [2].

Atlantis itself logs and propagates these errors but does not retry or handle them beyond logging. The maintainers recognize websocket stability as a pain point and there are proposals to move to Server-Sent Events (SSE) for more reliable streaming in future versions [3].

If you continue to see these errors after updating your ingress/load balancer configuration, reviewing network timeouts and proxy/firewall rules in your environment is recommended, as these can also cause websocket disconnects.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.