Can't update; remote fix doesn't work

[bcg]

throws different error now with firewall back on:

garuda-update -a --skip-mirrorlist -- --ignore miniupnpc
[sudo] password for bcg:
:: Synchronizing package databases...
garuda is up to date
core is up to date
extra is up to date
multilib                                                   132.1 KiB   506 KiB/s 00:00 [---------------------------------------------------] 100%
chaotic-aur is up to date
error: failed retrieving file 'garuda.db' from cdn-mirror.chaotic.cx : SSL certificate problem: unable to get local issuer certificate
error: failed retrieving file 'chaotic-aur.db' from cdn-mirror.chaotic.cx : SSL certificate problem: unable to get local issuer certificate
error: failed retrieving file 'garuda.db' from geo-mirror.chaotic.cx : SSL certificate problem: unable to get local issuer certificate
error: failed retrieving file 'chaotic-aur.db' from geo-mirror.chaotic.cx : SSL certificate problem: unable to get local issuer certificate
spawn pacman -Su --ignore miniupnpc
:: Starting full system upgrade...
warning: appimagelauncher: local (2.2.0-9.8) is newer than chaotic-aur (2.2.0-9)
warning: kf6-servicemenus-rootactions: local (1.1.0-5) is newer than chaotic-aur (1.1.0-1.1)
warning: snapper-tools: local (1.3.1-1.6) is newer than chaotic-aur (1.3.1-1)
warning: zmusic: local (1.1.14.r13.ge5fecbe-1) is newer than chaotic-aur (1.1.14-1)
there is nothing to do

--> Updating AUR packages with paru..
:: Looking for devel upgrades...
:: packages not in the AUR: kinit  libretro-citra  packagekit-qt5  proton-ge-custom
:: marked out of date: cairo-dock-themes  systemtap-git
:: orphans: cairo-dock-themes  libretro-retrodream
there is nothing to do

System updated! 🐧

--- System Health Check Report ---
23/23 checks run in 0.48 seconds ⌛
Powered by garuda-health 🦅

✅ System health check passed. No issues found.

[bcg]

but now I got the whitelisting working in zenarmor, so all other parked domains will be blocked

[TNE]

That’s as expected, in this case!

The problem with the previous errors was that pacman was told the download completed successfully (by your firewall) but then failed to verify the signature (because the download obviously wasn’t successful).

The logs here show that pacman failed to download the files (which is expected with your firewall blocking things), but it also managed to find another way to successfully download the files → the end result is a success!

Someone with the same firewall will not have the same problem in the future anymore because of you!

Thanks for testing.

[Apocalypticus]

Great collaboration guys