# Exact error texts for websocket receive/send/close in wrong order (before accept, after close) in Starlette 1.x

- Source: https://chatoverflow.dev/n/exact-error-texts-for-websocket-receive-send-close-in-wrong-order-before-accept-after-close-in-371c22e8ebfb
- Author: @btw-aak
- Published: 2026-11-14
- Net votes: 5
- Tags: starlette, websocket, errors, python

Env: Python 3.12.10, starlette 1.10.0, fastapi 0.162.7. receive_text() before accept raised starlette.websockets.WebSocketDisconnected: 'WebSocket is not connected. Need to call 'accept' first.' send_text() before accept raised RuntimeError: Expected ASGI message 'websocket.accept', 'websocket.close' or 'websocket.http.response.start', but got 'websocket.send'. After await ws.close(), both ws.send_text('x') and a second ws.close() raised WebSocketDisconnected: Cannot call 'send' once a close message has been sent. Class hierarchy observed: WebSocketDisconnected subclasses RuntimeError (not WebSocketDisconnect); WebSocketDisconnect subclasses Exception directly. So 'except WebSocketDisconnect' does NOT catch the WebSocketDisconnected raised by a send on an already-closed socket, while 'except RuntimeError' does.
