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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebSocketError #67

Open
ryujimorimoto opened this issue Jul 29, 2022 · 14 comments
Open

WebSocketError #67

ryujimorimoto opened this issue Jul 29, 2022 · 14 comments

Comments

@ryujimorimoto
Copy link

When I launch tunnelto, I run into a WebSocketError.
It worked fine until the day before, but suddenly it stopped working.

馃寧 Opening remote tunnel...
> Ready on http://localhost:8082 , https://forestbook.tunne
 ERROR tunnelto > Control error: WebSocketError(Tls(Native(Error { code: -9806, message: "connection closed via error" }))). Retrying in 5 seconds.

Could you give me a way to solve this problem?

@mbcrute
Copy link

mbcrute commented Jul 29, 2022

I also am experiencing this, since about 3 PM EDT on July 28th...

禄 tunnelto --port 9909 --verbose
 INFO  tunnelto::config > Control Server URL: wss://wormhole.tunnelto.dev:443/wormhole
 DEBUG tunnelto::update > Using latest version.
 ERROR tunnelto         > Control error: WebSocketError(Protocol(HandshakeIncomplete)). Retrying in 5 seconds.
 INFO  tunnelto         > restarting wormhole
 ERROR tunnelto         > Control error: WebSocketError(Tls(Native(Error { code: -9806, message: "connection closed via error" }))). Retrying in 5 seconds.
 INFO  tunnelto         > restarting wormhole
 ERROR tunnelto         > Control error: WebSocketError(Http(Response { status: 502, version: HTTP/1.1, headers: {"server": "Fly/eefa7631 (2022-07-29)", "via": "1.1 fly.io", "fly-request-id": "01G9526VG7HT6KA4PX00105KVG-iad", "content-length": "0", "date": "Fri, 29 Jul 2022 13:27:10 GMT"}, body: None })). Retrying in 5 seconds.
 INFO  tunnelto         > restarting wormhole
馃實 Opening remote tunnel...

Lather. Rinse. Repeat. I sent an email to support yesterday but have yet to receive a response.

@malikid
Copy link

malikid commented Jul 29, 2022

+1

it fails quite frequently from the beginning of this week. Getting harder and harder to get it to work. keep getting the errors and it retries again and again...

Local Inspect Dashboard: http://localhost:61229
 INFO  tunnelto         > got ping
 WARN  tunnelto         > websocket read error: Protocol("Connection reset without closing handshake")
 INFO  tunnelto         > restarting wormhole
 WARN  tunnelto         > control flow didn't send anything!
 INFO  tunnelto         > connecting to wormhole as client tdO-EWB_a4kPuMcYzCC9Yhu8T5K_nuJRh1JJypcTC-4
 INFO  tunnelto         > Server accepted our connection.
=> Forwarding to localhost:3000

 INFO  tunnelto         > got ping
 WARN  tunnelto         > websocket read error: Protocol("Connection reset without closing handshake")
 INFO  tunnelto         > restarting wormhole
 WARN  tunnelto         > control flow didn't send anything!
 INFO  tunnelto         > connecting to wormhole as client zEuHDxnZi8sWQxFt5BsNZgkNtsesvc07JsoLFKJH8-8
 INFO  tunnelto         > Server accepted our connection.
=> Forwarding to localhost:3000

 INFO  tunnelto         > got ping

@drazen-popov-lepaya
Copy link

drazen-popov-lepaya commented Jul 29, 2022

+1
[TUNNEL] ERROR tunnelto > Control error: WebSocketError(Tls(Native(Ssl(Error { code: ErrorCode(5), cause: Some(Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })) }, X509VerifyResult { code: 0, error: "ok" })))). Retrying in 5 seconds.
[TUNNEL] ERROR tunnelto > Control error: WebSocketError(Tls(Native(Ssl(Error { code: ErrorCode(5), cause: Some(Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })) }, X509VerifyResult { code: 0, error: "ok" })))). Retrying in 5 seconds.
[TUNNEL] ERROR tunnelto > Control error: WebSocketError(Tls(Native(Ssl(Error { code: ErrorCode(5), cause: Some(Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })) }, X509VerifyResult { code: 0, error: "ok" })))). Retrying in 5 seconds.
[TUNNEL] ERROR tunnelto > Control error: WebSocketError(Tls(Native(Ssl(Error { code: ErrorCode(5), cause: Some(Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })) }, X509VerifyResult { code: 0, error: "ok" })))). Retrying in 5 seconds.
[TUNNEL] ERROR tunnelto > Control error: WebSocketError(Tls(Native(Ssl(Error { code: ErrorCode(5), cause: Some(Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })) }, X509VerifyResult { code: 0, error: "ok" })))). Retrying in 5 seconds.

@ryujimorimoto
Copy link
Author

The error is now resolved when you access it after a while.
The cause of this error is unknown.

@drazen-popov-lepaya
Copy link

worked for a short period of time, but it is still broken

ERROR tunnelto > Control error: WebSocketError(Protocol(ResetWithoutClosingHandshake)). Retrying in 5 seconds.
ERROR tunnelto > Control error: WebSocketError(Protocol(ResetWithoutClosingHandshake)). Retrying in 5 seconds.
ERROR tunnelto > Control error: WebSocketError(Http(Response { status: 502, version: HTTP/1.1, headers: {"server": "Fly/b2c77cc8 (2022-07-31)", "via": "1.1 fly.io", "fly-request-id": "01G9CNVDE90TZF128RRNYG4M74-ams", "content-length": "0", "date": "Mon, 01 Aug 2022 12:24:49 GMT"}, body: None })). Retrying in 5 seconds.
ERROR tunnelto > Control error: WebSocketError(Http(Response { status: 502, version: HTTP/1.1, headers: {"server": "Fly/b2c77cc8 (2022-07-31)", "via": "1.1 fly.io", "fly-request-id": "01G9CNVKFS5CDKR7WENPQ5MCAH-ams", "content-length": "0", "date": "Mon, 01 Aug 2022 12:25:09 GMT"}, body: None })). Retrying in 5 seconds.
ERROR tunnelto > Control error: WebSocketError(Http(Response { status: 502, version: HTTP/1.1, headers: {"server": "Fly/b2c77cc8 (2022-07-31)", "via": "1.1 fly.io", "fly-request-id": "01G9CNW6P8707QSXEJFBKHAV8R-ams", "content-length": "0", "date": "Mon, 01 Aug 2022 12:25:25 GMT"}, body: None })). Retrying in 5 seconds.
ERROR tunnelto > Control error: WebSocketError(Protocol(ResetWithoutClosingHandshake)). Retrying in 5 seconds.

@mbcrute
Copy link

mbcrute commented Aug 1, 2022

Still not working for me either. I've not gotten a response from the Twitter account or the email I sent to support so I'm canceling my account and self-hosting.

@malikid
Copy link

malikid commented Aug 4, 2022

Still getting errors...

@KTruong008
Copy link

Just started getting this error this morning. Also had some odd loading issues prior where it'd take minutes to load pages that took seconds just days ago.

@onlysumitg
Copy link

onlysumitg commented Sep 17, 2022

Same issue for me.
anyone found a solution for this issue?

ERROR tunnelto > Control error: WebSocketError(Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })). Retrying in 5 seconds.
ERROR tunnelto > Control error: WebSocketError(Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })). Retrying in 5 seconds.

@j0no
Copy link

j0no commented Sep 18, 2022

I'm getting this issue as well.

ERROR tunnelto > Control error: WebSocketError(Io(Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" })). Retrying in 5 seconds.

@iGhoneim
Copy link

I'm getting "An existing connection was forcibly closed by the remote host."

ERROR tunnelto > Control error: WebSocketError(Tls(Native(Os { code: 10054, kind: ConnectionReset, message: "An existing connection was forcibly closed by the remote host." }))). Retrying in 5 seconds.

@Ryusuke-Kawasaki
Copy link

Hi.
I'm getting same issue. After I ran tunnelto command, I got the following error message.

 ERROR tunnelto > Control error: WebSocketError(Tls(Native(Error { code: -9806, message: "connection closed via error" }))). Retrying in 5 seconds.

@Ryusuke-Kawasaki
Copy link

I ran the tunneldev command again today.
As a result, I confirmed that the following problems reported yesterday did not occur and the tunneldev command was executed successfully.

ERROR tunnelto > Control error: WebSocketError(Tls(Native(Error { code: -9806, message: "connection closed via error" }))). Retrying in 5 seconds.

@j0no
Copy link

j0no commented Sep 27, 2022

I ran a tunnel and I no longer get the error.

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

9 participants