Skip to content
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

wamp server using SSL/TLS #163

Closed
evgenyfedorenko opened this issue Dec 12, 2015 · 4 comments
Closed

wamp server using SSL/TLS #163

evgenyfedorenko opened this issue Dec 12, 2015 · 4 comments

Comments

@evgenyfedorenko
Copy link

We have a SSL installed on one of our test hosts where we want to use websockets. I wanted to ask whether thruway server needs to be started in any other way than normal to work over SSL ?
When we try to connect the client to running thruway router using 'wss://' we get the following error:

WebSocket connection to 'wss://servername:9090/' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
modules.0ac16270.js:2 Connection Closed: unreachable Object {reason: null, message: null, retry_delay: 1.6830165722661887, retry_count: 1, will_retry: true}

Thank you

@davidwdan
Copy link
Member

Thruway's Ratchet transport provider does not directly support SSL. You'll need to put some sort of proxy in front of it.

See #66

@evgenyfedorenko
Copy link
Author

So after we install mod_proxy_wstunnel implementation of thruway router won't change ?

@davidwdan
Copy link
Member

I'm not familiar with mod_proxy_wstunnel, but you shouldn't have to change anything in the router.

If you want to force public access through the proxy, you'll want to make sure that you start it on 127.0.0.1, but that's not required to get the proxy working.

@evgenyfedorenko
Copy link
Author

Thanks, will try it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants