How can I get Axum WebSockets to work in a fullstack Dioxus app?

[idanarye]

I'm trying to run Dioxus in fullstack mode with an Axum router as described here. The routing works - but for some reason, not for WebSockets.

I'm adding the WebSocket route using https://github.com/idanarye/kivnun/blob/58cf00cf095ed700424fc1438aa23b8f4a571579/src/main.rs#L15-L28

Where the WebSocket upgrade and handling are https://github.com/idanarye/kivnun/blob/58cf00cf095ed700424fc1438aa23b8f4a571579/backend/src/wsjrpc/mod.rs

But it fails - when I'm trying to connect a WebSocket client, it complains about an I/O failure:

$ websocat ws://127.0.0.1:8080/ws
hello

websocat: WebSocketError: I/O failure
websocat: error running

And dx serve prints the following logs:

04:44:03 [dev] [101] /ws
04:44:03 [server]  INFO Send was successful
04:44:03 [server] ERROR Recv failed: Error { inner: Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }) }

So basically - the server thinks it managed to send its message, but the client does not see it, and when the server tries to receive a message - it gets a ConnectionReset.

If I use the same code but connect to the socket manually: https://github.com/idanarye/kivnun/blob/58cf00cf095ed700424fc1438aa23b8f4a571579/examples/regular_axum_ws.rs

Then everything works:

$ websocat ws://127.0.0.1:8080/ws
Welcome!
hello

$ cargo run --example regular_axum_ws --features server
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.18s
     Running `target/debug/examples/regular_axum_ws`
2025-03-28T01:47:12.463803Z  INFO backend::wsjrpc: Send was successful
2025-03-28T01:47:14.884249Z  INFO backend::wsjrpc: Got Text("hello\n") from socket

What's wrong? I suspect that maybe dx serve is doing some proxying which messes up with WebSockets?

[ealmloff]

Yes, the CLI doesn't proxy websockets correctly today. #3895 fixes that issue

[idanarye]

I've tried with that version of the CLI and can confirm that it works (initially I tried to build with that version of Dioxus as the dependencies, and it didn't work, but then I realized my mistake)

Is it safe to assume that if I don't use dx serve and build my application as a standalone executable (still using the fullstack mode), it should work even without that fix?

[ealmloff]

I've tried with that version of the CLI and can confirm that it works (initially I tried to build with that version of Dioxus as the dependencies, and it didn't work, but then I realized my mistake)

Is it safe to assume that if I don't use dx serve and build my application as a standalone executable (still using the fullstack mode), it should work even without that fix?

Yes, or even if you build your app with dx and run the server manually it should work without the proxy fix