HTPPS and HTTP issue #1977
Replies: 7 comments 8 replies
-
|
This isn't really a concern of Flask-SocketIO. If you host your app on HTTPS and use https:// URLs to connect to Socket.IO everything should work the same as in your local environment. This error occurs because your front end is using a http:// URL to connect to the Socket.IO server. |
Beta Was this translation helpful? Give feedback.
-
|
Oh thanks! That never came to my mind! Thanks again!
…On Sat, 22 Apr 2023 at 15:12, Miguel Grinberg ***@***.***> wrote:
This isn't really a concert of Flask-SocketIO. If you host your app on
HTTPS and use https:// URLs to connect to Socket.IO everything should
work the same as in your local environment. This error occurs because your
front end is using a http:// URL to connect to the Socket.IO server.
—
Reply to this email directly, view it on GitHub
<#1977 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVKC2Y2UUK5ZXOBGWJR6TLDXCORZ7ANCNFSM6AAAAAAXHS5FF4>
.
You are receiving this because you authored the thread.Message ID:
<miguelgrinberg/Flask-SocketIO/repo-discussions/1977/comments/5692543@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
What about
`Socket connection to 'wss://../
socket.io/?EIO=4&transport=websocket&sid=CQTIKIcJrqgzaCUpAAAA' failed:
WebSocket is closed before the connection is established`.?
On Sat, 22 Apr 2023 at 15:28, Prateek Pathak ***@***.***>
wrote:
… Oh thanks! That never came to my mind! Thanks again!
On Sat, 22 Apr 2023 at 15:12, Miguel Grinberg ***@***.***>
wrote:
> This isn't really a concert of Flask-SocketIO. If you host your app on
> HTTPS and use https:// URLs to connect to Socket.IO everything should
> work the same as in your local environment. This error occurs because your
> front end is using a http:// URL to connect to the Socket.IO server.
>
> —
> Reply to this email directly, view it on GitHub
> <#1977 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AVKC2Y2UUK5ZXOBGWJR6TLDXCORZ7ANCNFSM6AAAAAAXHS5FF4>
> .
> You are receiving this because you authored the thread.Message ID:
> <miguelgrinberg/Flask-SocketIO/repo-discussions/1977/comments/5692543@
> github.com>
>
|
Beta Was this translation helpful? Give feedback.
-
|
I can't really debug your application for you. If I had to guess I'd say you do not have a working WebSocket set up, but it would be up to you to debug this and figure out why your WebSocket connection is not working. Flask-SocketIO has documentation, which may help. |
Beta Was this translation helpful? Give feedback.
-
|
Any difference between prod and dev which might cause this? Because it works locally. |
Beta Was this translation helpful? Give feedback.
-
|
What is meant by invalid session? I read https://stackoverflow.com/questions/74596602/flask-socket-invalid-session-lwmxdnrmai59brflaaaa-further-occurrences-of-this. but I'm not using any websocket like gunicorn or eventlet. It's a prod problem I think. Can it possibly be related to the versions? |
Beta Was this translation helpful? Give feedback.
-
|
Im getting invalid session |
Beta Was this translation helpful? Give feedback.
-
|
I know! It works properly locally! There's no more information to share , except that the url returned invalid session! Everything has been done according to the documentation, and if it had not, it would not have run locally! I have been struggling with this issue for half a year, and nothing works. Forget it, I'll fix it myself |
Beta Was this translation helpful? Give feedback.
-
Like on prod do you have a reverse proxy running? Do you got any kind of load balancing going? Sounds like you got https and http running on prod. Sounds like there can be a number of differences between prod and dev for you. |
Beta Was this translation helpful? Give feedback.
-
|
I made some changes, did some debugging, and got a new error. |
Beta Was this translation helpful? Give feedback.
-
|
You are using an unsupported deployment platform. As I mentioned before, please review the deployment section of the documentation to learn what the supported options are. CPanel or other shared hosting platforms are unlikely to work. |
Beta Was this translation helpful? Give feedback.
-
Hi, I had the same issue here. In my case it was a misconfigured socketio = SocketIO(app, async_mode='gevent')It worked fine after I changed it to: socketio = SocketIO(app, async_mode='gevent_uwsgi')I know at the end it wasn't the same problem you had, but it had the same symptoms so I decided to write my solution in case someone else happens to have the same problem. Have a nice day! |
Beta Was this translation helpful? Give feedback.
-
|
Update: My hosting provider says: However, for a websocket to work you'd usually need a dedicated port for inbound connections. or something like a proxy-pass configuration. Although, such setup cannot be performed on a Shared Hosting server. I would recommend running either a third-party web-socket server, or consider upgrading to our private server solutions and configuring your application with a proxypass configuration. What kind of a third-party web-socket server? |
Beta Was this translation helpful? Give feedback.
-
|
I think they mean something that runs on a non-standard port, any of the deployment options listed here: https://flask-socketio.readthedocs.io/en/latest/deployment.html Maybe you can followup with them what they mean. I suspect anything on their share hosting server will be unsatisfactory though. |
Beta Was this translation helpful? Give feedback.
-
Mixed Content: The page at 'https://.../chat' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://.../socket.io/?EIO=4&transport=polling&t=OUdK2XB'. This request has been blocked; the content must be served over HTTPS. cWhen I worked locally, my chat app worked perfectly, but I pushed the changes to my site, which is https, it gave the error. I'm not very qualified with networking and sockets and such , so help would be greatly appreciated as soon as possible. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions