starred/tunnelto

Fork 0

mirror of https://github.com/agrinman/tunnelto.git synced 2026-04-26 01:06:01 +03:00

[GH-ISSUE #31] Websocket returns error through tunnel #28

New issue

Closed

opened 2026-03-02 23:01:51 +03:00 by kerem · 5 comments

kerem commented

2026-03-02 23:01:51 +03:00

Owner

Originally created by @jsmestad on GitHub (Nov 1, 2020).
Original GitHub issue: https://github.com/agrinman/tunnelto/issues/31

I had to switch back to ngrok for the time being as I cannot connect a websocket through the tunnel.

When trying to connect, the browser get's stuck throwing Invalid frame header while trying to connect. This is with a hello world Phoenix app that relies on LiveView if you need something to recreate it.

Let me know if I can help any more in tracking down the cause.

Originally created by @jsmestad on GitHub (Nov 1, 2020). Original GitHub issue: https://github.com/agrinman/tunnelto/issues/31 I had to switch back to ngrok for the time being as I cannot connect a websocket through the tunnel. When trying to connect, the browser get's stuck throwing `Invalid frame header` while trying to connect. This is with a hello world Phoenix app that relies on LiveView if you need something to recreate it. Let me know if I can help any more in tracking down the cause.

kerem

2026-03-02 23:01:51 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-02 23:01:52 +03:00

Author

Owner

@hirschenberger commented on GitHub (Nov 18, 2020):

Same issue here. Very sad.

@hirschenberger commented on GitHub (Nov 18, 2020): Same issue here. Very sad.

kerem commented

2026-03-02 23:01:53 +03:00

Author

Owner

@agrinman commented on GitHub (Nov 21, 2020):

Thanks for the bug report, will look into this

@agrinman commented on GitHub (Nov 21, 2020): Thanks for the bug report, will look into this

kerem commented

2026-03-02 23:01:53 +03:00

Author

Owner

@gzimh commented on GitHub (Jan 18, 2021):

I don't think this is realted to tunnelto. Inavlid frame header is usually a result of SSL mismatch.
The client request should be secured (e.g socket.io):

const socket = io.connect('https://<subdomian>.tunnelto.dev', {secure: true});

or, just use the http version of the generated tunnel:

const socket = io.connect('http://<subdomian>.tunnelto.dev');

@gzimh commented on GitHub (Jan 18, 2021): I don't think this is realted to tunnelto. Inavlid frame header is usually a result of SSL mismatch. The client request should be secured (e.g socket.io): ``` const socket = io.connect('https://<subdomian>.tunnelto.dev', {secure: true}); ``` or, just use the `http` version of the generated tunnel: ``` const socket = io.connect('http://<subdomian>.tunnelto.dev'); ```

kerem commented

2026-03-02 23:01:53 +03:00

Author

Owner

@agrinman commented on GitHub (Apr 26, 2021):

So yes it turns out this is something tunnelto needs to handle as it was previously not processing the WebSocket upgrade. #42 add supports for this and will be merged shortly...

@agrinman commented on GitHub (Apr 26, 2021): So yes it turns out this is something tunnelto needs to handle as it was previously not processing the WebSocket upgrade. #42 add supports for this and will be merged shortly...

kerem commented

2026-03-02 23:01:53 +03:00

Author

Owner

@agrinman commented on GitHub (May 1, 2021):

Fixed it 0.1.16!

@agrinman commented on GitHub (May 1, 2021): Fixed it 0.1.16!

kerem referenced this issue

2026-03-13 19:53:34 +03:00

[GH-ISSUE #28] Added to awesome-tunneling list #119