jcorrea
Bandit websocket server connection terminated reason={:error, :closed}
Hi everyone! 
I’m building a WebSocket server with Bandit inside a Plug app, and the experience has been fantastic so far, really clear semantics and great performance out of the box.
I’ve run into one issue, though: I occasionally see connections terminate with {:error, :closed}. I’m trying to figure out the best way to diagnose what’s causing these closures, since there’s nothing in the server logs that seems to explain them, and our code never returns a {:stop, reason, state}.
Has anyone dealt with this before or have suggestions on how to track down the source of these disconnects?
Thanks in advance!
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #elixirconf-us
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 3 of 3 Posts!
jcorrea
I was able to capture some additional information using Bandit / Thousand island telemetry.
It turns out the error that is causing those disconnections is:
with
krasenyp
If this is deployed somewhere, it might be your infrastructure provider not allowing long-lived connections.
jcorrea
Yes, that definitely makes sense!
Additionally, in my testing I noticed that some WebSocket clients don’t actually send a close frame or status code when they disconnect, they just close the underlying TCP connection. That was a bit surprising and explains why the server sees it as an abrupt disconnect rather than a regular shutdown, which in turn makes it harder to differentiate network interruptions from regular application-level connection terminations.