mirror of
https://github.com/agrinman/tunnelto.git
synced 2026-04-25 16:56:00 +03:00
[GH-ISSUE #36] Work within environments with proxy #125
Labels
No labels
Need more info
bug
duplicate
enhancement
good first issue
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tunnelto#125
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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?
@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?
@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_proxyenvironment variable is used for.What would be nice is if tunnelto checked that
http_proxyenvironment 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:
@ryujimorimoto commented on GitHub (Jul 29, 2022):
I'm having the same problem.
Is there a solution?