This causes git and ssh to try to connect via ipv6, time out after a few min, then succeed over ipv4. I tried via two completely independent internet connections, so it's highly likely to not be on my end. http[s] is mostly fine since most browsers will try to connect simultaneously over ipv6 and ipv4 and just use the first one to connect.
a temporary fix while troubleshooting could be to remove the ipv6 address from libre-soc.org's dns
the ipv6 address being reassigned when the server was rebooted might be a cause
The address is: 2a00:1098:82:f::1 This is set up in DNS and the interface has this address. Locally the address can be pinged. Remotely they get lost traceroute shows echos somewhere in Mythic Beasts, makes sense since whois says that that is who owns the address. I'll dig more and prob talk to MB
alain what's this 6to4 doing? 6to4: flags=193<UP,RUNNING,NOARP> mtu 1480 inet6 ::46.235.227.77 prefixlen 96 scopeid 0x80<compat,global> inet6 2002:2eeb:e34d::1 prefixlen 16 scopeid 0x0<global> sit txqueuelen 1 (IPv6-in-IPv4) RX packets 792 bytes 64609 (63.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 211225 bytes 19684697 (18.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ens3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 46.235.227.77 netmask 255.255.255.128 broadcast 46.235.227.127 inet6 2a00:1098:82:f::1 prefixlen 64 scopeid 0x0<global> inet6 fe80::5054:ff:fe12:7997 prefixlen 64 scopeid 0x20<link> ether 52:54:00:12:79:97 txqueuelen 1000 (Ethernet) RX packets 102166455 bytes 9177043110 (8.5 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 6778508 bytes 9243984362 (8.6 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
No idea why we have a 6to4 interface. Why do we need it. Before I play at turning 6to4 off - how do I access the console directly ? I do not want to fiddle and make the machine completely unreachable!
Mythic Beasts provide VNC access to the machine's console. For that I need access to the "virtual server's page on the control panel", where do I find that and what authentication do I need ?
(In reply to Alain D D Williams from comment #6) > Mythic Beasts provide VNC access to the machine's console. > For that I need access to the "virtual server's page on the control panel", > where do I find that and what authentication do I need ? i will email it to you: bear in mind i could not get it to work.
This appears to be resolved, no issues connecting to libre-soc.org over IPv6 for me.
IPv6 is broken again... jacob@jacob-desktop:~$ curl --verbose --ipv6 https://libre-soc.org * Trying 2a00:1098:82:f::1:443... * TCP_NODELAY set <just hangs> From talos1: jacob@75-224-155-23:~$ curl --verbose --ipv6 https://libre-soc.org/ * Trying 2a00:1098:82:f::1:443... * TCP_NODELAY set * Immediate connect fail for 2a00:1098:82:f::1: Network is unreachable * Closing connection 0 curl: (7) Couldn't connect to server I discovered that I can do: git push -4 --- handy option to force connecting over ipv4
nothing's been altered, and i don't know enough about IPV6 (and don't like it, and don't have time)
(In reply to Luke Kenneth Casson Leighton from comment #10) > nothing's been altered, and i don't know enough about IPV6 > (and don't like it, and don't have time) can you please, as a temporary workaround, remove ipv6 from libre-soc's dns then? it'll make it non-annoying to use until someone can get around to fixing ipv6.
turns out that ipv6 was just broken on my end and the talos server has no ipv6 connection...so of course I can't reach libre-soc via ipv6. rebooting the router at my house fixed the ipv6 problem.