Unable to update

Started by walkerx, September 24, 2020, 09:00:03 PM

Previous topic - Next topic
I've previously had an issue early last year on performing an update and getting the error

Could not authenticate the selected mirror.

I had some advice and changed settings and was then able to update from 19 to 20.1.7 but now if I try to update I get the same issue as before so unable to update to 20.7, but have not changed my settings

Are there still issues with updating when using ipv6? Is there a way to force the update via ipv4 without having to mess about with configuration changes?

Thanks

Hi,

It means TLS authentication failed. Make sure your system time is correct and the root certificates are properly installed.


Cheers,
Franco

September 25, 2020, 12:07:31 AM #2 Last Edit: September 25, 2020, 10:21:01 AM by walkerx
i think i've fixed it and not sure if the issue was caused by the update

I checked the settings of the wan_v6_monitor gateway and noticed that the ip address had been changed to full ip instead of ::1, so set this back to how I originally set this up and immediately I was able to get update information.

also have just noticed @ 9:19 (current uk time) that it reports a crash on the main dashboard page, which was for roughly around the time (7am uk time) i was fixing this, but have submitted it just incase something else a miss





Might be an intermittent issue, although TLS verification fail is something that requires both a client and a server to interact. Either the client or the server was wrong and if your client worked I'm not sure which server answered. Maybe a redirect to a self-signed server somewhere else depending on your network setup? Hitting a HTTPS proxy maybe?


Cheers,
Franco

September 25, 2020, 06:10:46 PM #4 Last Edit: September 25, 2020, 07:07:40 PM by walkerx
Quote from: franco on September 25, 2020, 12:45:39 PM
Might be an intermittent issue, although TLS verification fail is something that requires both a client and a server to interact. Either the client or the server was wrong and if your client worked I'm not sure which server answered. Maybe a redirect to a self-signed server somewhere else depending on your network setup? Hitting a HTTPS proxy maybe?


Cheers,
Franco

never changed anything else on the configuration as was all setup with the help of @marjohn56

The only info I noticed when went into the gateway monitor was that the ip address was set to full ipv6 address instead of :::1 which it originally was set to

The updates are set to look at defaults, the time is correct on the system and I've never made changes to the certificates either, so these would have been as was when installed

I'm now on the latest version

You should be able to turn off ipv6 under Interfaces. Pick None for IPv6 configuration.

:::1 means it is localhost. Does your "new" ip6 address starts with an f? If so it might be a private one.