Skip to content

error 3 Bad request #4467

Answered by gibloor
rantianhua asked this question in Q&A
Sep 5, 2022 · 1 comments · 1 reply
Discussion options

You must be logged in to vote

It seems like you're encountering an issue where the frontend is likely using WebSocket, but when Nginx (or whatever you're using) forwards the request to the server, it switches the transport to polling. When the server tries to send a signal using WebSocket, this error occurs.

Configure NGINX!

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@darrachequesne
Comment options

Answer selected by darrachequesne
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants