search

d4l3k / webrtc-lobby

A lobby service for webrtc.
MIT License
6 stars 0 forks source link

Testing URL #2

Open lazydino opened 7 years ago

lazydino commented 7 years ago

I deploy your repository with letsencrypt using dokku on my server, but failed to do simple connection test with https://www.websocket.org/echo.html

What should be the url for testing? wss://myserver.com/lobby ? wss://myserver.com ? Both are failed for echo test.

d4l3k commented 7 years ago

As of right now it's listening on port 5000 by default.

So you would try and connect to ws://myserver.com:5000/ws

Not sure exactly what it'll be with let's encrypt in front of it.

https://github.com/d4l3k/webrtc-lobby/blob/master/main.go

lazydino commented 7 years ago

Thanks! it works fine now. Letsencrypt just add the SSL/TLS layer. My dokku deployment ( like heroku ) maps 5000 to 80, so in my case, I can test with wss://myserver.com/ws

d4l3k commented 7 years ago

Glad I could help. I should probably add more documentation to ease setup issues.

On Tue, May 9, 2017, 10:49 Reggie Chen notifications@github.com wrote:

Thanks! it works fine now. Letsencrypt just add the SSL/TLS layer. My dokku deployment ( like heroku ) maps 5000 to 80, so in my case, I can test with wss://myserver.com/ws

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/d4l3k/webrtc-lobby/issues/2#issuecomment-300247766, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3fMDafcsq644hUgS4JzIvTCO_C-WA0ks5r4KdAgaJpZM4NVoth .