-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does It Support Websocket? #24
Comments
I solved it by making /graphql websocket requests going directly to Daphne server. I still have no idea why websocket connection does not work when I route them to another nginx proxy server.
|
Anyway it looks like it does not work with remote website. I have tried remote URL as
Might it be because in config target is used as |
I got what was the issue, when rendora proxies to the server it does not include port, thus when for examples service is communicating with itself relatively ( |
My stack is like:
External World <-> nginx <-> rendora <-> nginx <-> daphne <-> django
I am using websocket connections. When I was doing
External World <-> nginx <-> daphne <-> django
It worked well. But when I implemented rendora and added another proxy to nginx, it does not work. Websocket connection fails while handshakes. My nginx conf is like below:
So location / 443 port sends all requests to 127.0.0.1:3001 where rendora is listening. And rendora forward them to 127.0.0.1:8000 nginx proxy to connect to daphne unix socket.
Rendora works well except the websocket requests.
It would be helpful if there is a nginx configuration example.
The text was updated successfully, but these errors were encountered: