On 12/1/25 1:57 PM, Ariadna Vigo wrote:
3. Connecting to a*different* network whatsoever doesn't fix this either.
I had fits with this when Arch moved its services into the cloud (a year, two, three ago?) The problem was the cloud IP that archlinux-keyring-wkd-sync used was part of a CIDR block that was banned at my firewall due to prior abuse from that block.
The thread was "What is/are the IPv4 addresses used by archlinux-keyring-wkd-sync? I need to tell iptables" from 2/26/2023.
Since the IP for rchlinux-keyring-wkd-sync is not exposed in any of the config files, etc., it took a bit of trial and error to identify what the issue was.
After determining what IP was being used and whitelisting those used by Arch cloud services - instantly the problem was solved.
So when you say "Connecting to a*different* network whatsoever doesn't fix this either.", does this "different" network share a common firewall or blocklist that may be blocking the IP forarchlinux-keyring-wkd-sync?
That's the only other thing I could think of that may be relevant to your issue.
-- David C. Rankin, J.D.,P.E.
