[Hussam Nasir]

If you VM is using an IPv6 address, which is the case with all FABRIC sites except MAX, then sites like github and dockerhub may not be accessible wince they are IPv4 only. A temporary solution is to use a NAT64 as mentioned on https://nat64.net/

[Hussam Nasir]

This maintenance has been completed. Thank you for your co-operation.

[Hussam Nasir]

The issue still exists.  Users will be informed when the site is back online.

[Hussam Nasir]

This issue was been resolved. Please continue your work.

[Hussam Nasir]

This maintenance is now complete You can now resume your work.

[Hussam Nasir]

The IPs you are trying are not your VMs. Those were examples mentioned in the documentation. You should replace those with the IPs you obtain after creating your VMs

[Hussam Nasir]

This maintenance has been completed. You can safely resume using this site.

[Hussam Nasir]

Here is my version of the ssh config file. Its advisable to save it in ~/work/.ssh/config rather than ~/.ssh/config since ~/work is persistent upon re-creation of the jupyterhub instance

 

UserKnownHostsFile /dev/null
StrictHostKeyChecking no
ServerAliveInterval 120

Host bastion-?.fabric-testbed.net
User <your bastion host username>
ForwardAgent yes
Hostname %h
IdentityFile <path to your bastion host private key>
IdentitiesOnly yes

Host * !bastion-?.fabric-testbed.net
ProxyJump <your bastion host username>@bastion-1.fabric-testbed.net:22
##ProxyJump <your bastion host username>@bastion-2.fabric-testbed.net:22

Once this file is saved, you no longer need the -J param as long as this file is included in your ssh command .

For example.

ssh -F ~/work/.ssh/config centos@63.239.135.94 should work

[Author]

Posts