Comment 0 for bug 1669501

Encountered a problem with connecting to long running GCE instance and only using juju scp and juju ssh to connect to this VM. I believe juju is doing something irregular that is getting my IP address blocked from connecting to the VM.

I was actively using a juju ssh session to jenkins/1 in one terminal, and trying to scp a file up to the jenkins/1 in another terminal. I was able to connect earlier and transfer a file down (using juju scp). When trying to upload the file I got disconnected and it appears my IP address is blocked. Here is the actual commands I was running and what happened in the terminal:

$ juju scp juju_gce.tar.gz jenkins/1:/var/lib/jenkins/juju/juju_gce_new.tar.gz
ERROR exit status 1 (Timeout, server 104.197.80.216 not responding.
lost connection)
$ juju scp juju_gce.tar.gz jenkins/1:
ERROR cannot connect to any address: [104.197.80.216:22 10.240.0.3:22 172.17.0.1:22]
$ juju ssh jenkins/1
ERROR cannot connect to any address: [104.197.80.216:22 10.240.0.3:22 172.17.0.1:22]
$ ping 104.197.80.216
PING 104.197.80.216 (104.197.80.216) 56(84) bytes of data.
^C
--- 104.197.80.216 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1031ms

The terminal using juju ssh timed out at the same time I got this error:

Timeout, server 104.197.80.216 not responding.

- - - - -

I was blocked out at my home address, so I traveled to a coffee shop where I was able to connect for a short time before getting blocked again. It appears to me that Juju is doing something irregular and getting blocked on GCE instances.