[GH-ISSUE #36] Work within environments with proxy #33

New issue

Open

opened 2026-03-02 23:01:53 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @naulacambra on GitHub (Mar 8, 2021).
Original GitHub issue: https://github.com/agrinman/tunnelto/issues/36

I've tested the .exe file on a Windows 10, and it doesn't seem to be able to create the tunnel.

The pc is in a proxy'd network, and I guess that is the problem.

There is any way to set the proxy settings?

Originally created by @naulacambra on GitHub (Mar 8, 2021). Original GitHub issue: https://github.com/agrinman/tunnelto/issues/36 I've tested the .exe file on a Windows 10, and it doesn't seem to be able to create the tunnel. The pc is in a proxy'd network, and I guess that is the problem. There is any way to set the proxy settings?

kerem added the

Need more info

label

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

kerem commented

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

Author

Owner

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

Proxy settings shouldn't affect tunnelto. It communicates to the outside world via web sockets. What error are you getting?

@agrinman commented on GitHub (Apr 18, 2021): Proxy settings shouldn't affect tunnelto. It communicates to the outside world via web sockets. What error are you getting?

kerem commented

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

Author

Owner

@barroudjo commented on GitHub (Jun 24, 2021):

I have the same problem as @naulacambra : in order to access the outside internet (as opposed to the corporate intranet) we have to go through a corporate proxy (so that they can check that we're not doing things we shouldn't be doing...).
That means that tunnelto when it attempts to make any kind of request to the internet (which it must) has to go through that proxy. That's what the http_proxy environment variable is used for.
What would be nice is if tunnelto checked that http_proxy environment variable and used it if it exists.
Currently it does not, which means that when I'm the corporate network, where going through the corporate proxy is required to access the outside internet, I currently get errors (timeouts) like this when launching tunnelto:

tunnelto --port 8000 -v
 INFO  tunnelto::config > Control Server URL: wss://wormhole.tunnelto.dev:443/wormhole
 ERROR tunnelto::update > Failed to check version: reqwest::Error { kind: Request, url: Url { scheme: "https", username: "", password: None, host: Some(Domain("api.github.com")), port: None, path: "/repos/agrinman/tunnelto/releases/latest", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 10060, kind: TimedOut, message: "Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu." })) }
 ERROR tunnelto         > Control error: WebSocketError(Io(Os { code: 10060, kind: TimedOut, message: "Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu." })). Retrying in 5 seconds.
 INFO  tunnelto         > restarting wormhole
 ERROR tunnelto         > Control error: WebSocketError(Io(Os { code: 10060, kind: TimedOut, message: "Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu." })). Retrying in 5 seconds.
 INFO  tunnelto         > restarting wormhole
🌎 Opening remote tunnel...

@barroudjo commented on GitHub (Jun 24, 2021): I have the same problem as @naulacambra : in order to access the outside internet (as opposed to the corporate intranet) we have to go through a corporate proxy (so that they can check that we're not doing things we shouldn't be doing...). That means that tunnelto when it attempts to make any kind of request to the internet (which it must) has to go through that proxy. That's what the `http_proxy` environment variable is used for. What would be nice is if tunnelto checked that `http_proxy` environment variable and used it if it exists. Currently it does not, which means that when I'm the corporate network, where going through the corporate proxy is required to access the outside internet, I currently get errors (timeouts) like this when launching tunnelto: ``` tunnelto --port 8000 -v INFO tunnelto::config > Control Server URL: wss://wormhole.tunnelto.dev:443/wormhole ERROR tunnelto::update > Failed to check version: reqwest::Error { kind: Request, url: Url { scheme: "https", username: "", password: None, host: Some(Domain("api.github.com")), port: None, path: "/repos/agrinman/tunnelto/releases/latest", query: None, fragment: None }, source: hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 10060, kind: TimedOut, message: "Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu." })) } ERROR tunnelto > Control error: WebSocketError(Io(Os { code: 10060, kind: TimedOut, message: "Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu." })). Retrying in 5 seconds. INFO tunnelto > restarting wormhole ERROR tunnelto > Control error: WebSocketError(Io(Os { code: 10060, kind: TimedOut, message: "Une tentative de connexion a échoué car le parti connecté n’a pas répondu convenablement au-delà d’une certaine durée ou une connexion établie a échoué car l’hôte de connexion n’a pas répondu." })). Retrying in 5 seconds. INFO tunnelto > restarting wormhole 🌎 Opening remote tunnel... ```

kerem commented

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

Author

Owner

@ryujimorimoto commented on GitHub (Jul 29, 2022):

I'm having the same problem.
Is there a solution?

@ryujimorimoto commented on GitHub (Jul 29, 2022): I'm having the same problem. Is there a solution?

kerem referenced this issue

2026-03-13 19:54:57 +03:00

[GH-ISSUE #33] Connect to HTTPS localhost #124