As you can see here it is complaining about an IPv6 address – and this is an odd choice given the lack of IPv6 address, and having gone through the steps to disable IPv6 and having rebooted.

At this point, I am pulling at my already greyed hair. A lot.

So what is happening here?

Well, the IPv6 address is a red herring basically. It is not telling you what the problem is – just confirming that it indeed cannot get to where it wants to be.

What is occurring is an inability to get out of port 80 to the server in question. It is failing over IPv4, and then falling back to trying over IPv6. Which… no surprises fails.The error while technically correct is steering you in the wrong direction.

Changing the upstream (YES, I had checked local iptables and ip6tables) firewall for allowing more than ping et al – and suddenly – update action!