telepresenceio / telepresence

Local development against a remote Kubernetes or OpenShift cluster
https://www.telepresence.io
Other
6.53k stars 513 forks source link

RuntimeError: vpn-tcp tunnel did not connect #1235

Closed brian-lutz closed 4 years ago

brian-lutz commented 4 years ago

What were you trying to do?

Connect to my Google Cloud cluster with Telepresence

What did you expect to happen?

Successfully connect

What happened instead?

Check the traceback? Honestly, I'm not sure. I use the tool, but I don't know a lot about how it works. I got the below traceback. I think it has something to do with the VPN software I'm using. I have an open connection using Pulse Secure (https://www.pulsesecure.net/)

EDIT: Yup, I tried to use telepresence again with the VPN turned off, and it worked. It looks like it's a bug with something shared between telepresence and the Pulse Secure software.

Automatically included information

Command line: ['/usr/local/bin/telepresence'] Version: 0.103 Python version: 3.7.6 (default, Dec 30 2019, 19:38:26) [Clang 11.0.0 (clang-1100.0.33.16)] kubectl version: Client Version: v1.15.5 // Server Version: v1.13.11-gke.14 oc version: (error: [Errno 2] No such file or directory: 'oc': 'oc') OS: Darwin c02zv641md6t-c 19.2.0 Darwin Kernel Version 19.2.0: Sat Nov 9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64 x86_64

Traceback (most recent call last):
  File "/usr/local/bin/telepresence/telepresence/cli.py", line 135, in crash_reporting
    yield
  File "/usr/local/bin/telepresence/telepresence/main.py", line 82, in main
    runner, remote_info, env, socks_port, ssh, mount_dir, pod_info
  File "/usr/local/bin/telepresence/telepresence/outbound/setup.py", line 112, in launch
    runner_, remote_info, command, args.also_proxy, env, ssh
  File "/usr/local/bin/telepresence/telepresence/outbound/local.py", line 126, in launch_vpn
    connect_sshuttle(runner, remote_info, also_proxy, ssh)
  File "/usr/local/bin/telepresence/telepresence/outbound/vpn.py", line 310, in connect_sshuttle
    raise RuntimeError("vpn-tcp tunnel did not connect")
RuntimeError: vpn-tcp tunnel did not connect

Logs:

EL | [58] timed out after 1.01 secs.
  51.0 TEL | Wait for vpn-tcp connection: hellotelepresence-9
  51.0 TEL | [59] Capturing: python3 -c 'import socket; socket.gethostbyname("hellotelepresence-9")'
  51.0  39 | c : DNS request from ('10.128.9.9', 50065) to None: 52 bytes
  51.1  28 | 2020-01-24T18:03:59+0000 [stdout#info] Result for b'hellotelepresence-9.tradeshift.com' is ['127.0.0.1']
  52.0  39 | c : DNS request from ('10.128.9.9', 50065) to None: 52 bytes
  52.1  28 | 2020-01-24T18:04:00+0000 [stdout#info] Result for b'hellotelepresence-9.tradeshift.com' is ['127.0.0.1']
  56.0 TEL | [59] timed out after 5.01 secs.
  56.0 TEL | [60] Capturing: python3 -c 'import socket; socket.gethostbyname("hellotelepresence-9.a.sanity.check.telepresence.io")'
  56.0  39 | c : DNS request from ('10.128.9.9', 57567) to None: 68 bytes
  56.1  28 | 2020-01-24T18:04:04+0000 [stdout#info] Sanity check: b'hellotelepresence-9.a.sanity.check.telepresence.io'
  57.0 TEL | [60] timed out after 1.01 secs.
ark3 commented 4 years ago

The default vpn-tcp method does not work with other VPNs.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. Issue Reporter: Is this still a problem? If not, please close this issue. Developers: Do you need more information? Is this a duplicate? What's the next step?