After rebooting my system after a successful update, I ran a quick checkupdates to make sure I was really up-to-date. It threw an error: ERROR: Cannot fetch updates, so I tried it as root and got the same message. Thinking that maybe the database was screwed up, I tried running yay -Dk, then yay -Syu:
yay -Dk
No database errors have been found!
yay -Syu
:: Synchronizing package databases...
core 138.4 KiB 423 KiB/s 00:00 [--------------------------------------------------------------------------------------] 100%
extra 1555.6 KiB 2.52 MiB/s 00:01 [--------------------------------------------------------------------------------------] 100%
community 6.0 MiB 9.68 MiB/s 00:01 [--------------------------------------------------------------------------------------] 100%
multilib is up to date
endeavouros is up to date
kernel-lts.db failed to download
chaotic-aur 1758.3 KiB 2.02 MiB/s 00:01 [--------------------------------------------------------------------------------------] 100%
error: failed retrieving file 'kernel-lts.db' from repo.m2x.dev : error:1408F10B:SSL routines:ssl3_get_record:wrong version number
error: failed to synchronize all databases (unexpected error)
-> error installing repo packages
ISP. I’ve been using this repo for about 2 weeks now and haven’t had any issues until this afternoon. What’s weird is that my full system update (ran this morning) updated the 5.10-LTS kernel without a hitch.
I wonder if updating the archlinux-keyring has anything to do with this. I don’t believe my internet connection has any effect, although the ping I ran was slow.
$ yay -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community 6.0 MiB 4.85 MiB/s 00:01 [################################] 100%
multilib is up to date
endeavouros is up to date
kernel-lts is up to date
Hopefully @jonathon can help; really don’t know what to try next. I guess I could purge the repo and remove all the relevant files and start over. But I’ll wait for now.
Whenever I’ve has similar SSL / TLS issues (ie curl download errors), they’ve been related to specific VPN exit nodes, config or maintenace changes which were fixed by the VPN provider (eventually).
I just used different exit nodes and / or different VPN providers as a workaround.
Are you using a wireless connection?
There have been issues with wpa_supplicant lastest version, you could try downgrading that and see if it helps.
OK, the last time I see your IP address was the 26th January (pacman checking for changes in the database). This is weird if you updated on 28th Jan., possibly suggests a change in your networking.
Can you check you are resolving the correct IP for the server (37.187.20.206/2001:41d0:a:14ce::1), and that you can access it via a web browser?
Before I start poking around on the server (also considering this is the first time someone has said there’s an issue) could you try accessing via a browser using an EnOS (or any) live installer environment to rule out changes to the local OS?
