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
WebSocket and SSL certificate #215
Comments
Sorry, I don't really understand what you question is. |
I need to add this settings to the nginx that is doing the reverse proxy in order for the web sockets to work. How can I do it?
|
Any updates here ?
It looks like this is handled already meaning another solution is needed. Default nginx config ..relevent code..
@SteveLTN any ides ?
Error from simple npx create-react-app |
I am not sure. As @jmayergit mentioned you can just set ‘WEBSOCK=true’ to have the headers. But why react reports error I don’t know. |
I should have clarified that I'm running in a development environment. Production works as expected |
I guess it has something to do with the local self-signed certificate.
Since the self-signed certificates are not trusted by browsers by default,
it may refuse to connect via websocket . Maybe you can try manually trust
the certificates?
…On Wed, 11 Dec 2019 at 9:09 AM Julien Mayer ***@***.***> wrote:
I should have clarified that I'm running in a development environment.
Production works as expected
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#215?email_source=notifications&email_token=AAD4AZZHGOISKKVDETHWLBTQYCN2HA5CNFSM4JO6XMQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGSHQMA#issuecomment-564426800>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAD4AZ6IX3JLRLQVJMUBMX3QYCN2HANCNFSM4JO6XMQQ>
.
|
I would like to solve this issue as this gentleman explains but i don't know how to do it. Any suggestions? Thanks
socketio/socket.io#1942 (comment)
The text was updated successfully, but these errors were encountered: