I’ve been experiencing an issue with Manjaro where I cannot connect to the AUR or the package repositories, and I’m getting several errors related to TLS handshake timeouts. Here are the details of the problem I’ve encountered:
Description of the Problem:
I’m unable to install or update packages using both yay and pacman. I’ve encountered multiple errors when trying to connect to repositories, including TLS handshake timeouts and failure to reach AUR servers. For example, here’s the error I get:
System Information:
Manjaro Version: Manjaro Linux x86_64
Kernel: 6.17.0-rc1-1-MANJARO
Desktop Environment: KDE Plasma
AUR Helper: yay (
Network: Wi-Fi 5gh
error: failed retrieving file 'core.db' from manjaro.mirrors.uk2.net : Failed to connect to manjaro.mirrors.uk2.net port 443 after 69 ms: Could not connect to server
error: failed retrieving file 'extra.db' from ftp.tu-chemnitz.de : Failed to connect to ftp.tu-chemnitz.de port 443 after 34 ms: Could not connect to server
error: failed retrieving file 'multilib.db' from coresite.mm.fcix.net : Failed to connect to coresite.mm.fcix.net port 443 after 47 ms: Could not connect to server
Additionally, when I try to run traceroute to aur.archlinux.org, I see the following:
1 _gateway (192.168.100.1) 1.440 ms
...
21 aur.archlinux.org (95.216.144.15) 89.604 ms !X 96.691 ms !X 86.912 ms !X
Steps I’ve Taken:
I tried changing my mirrors using sudo pacman-mirrors -g --fasttrack 10 to select faster mirrors, but the issue persists.
I verified my internet connection is stable using ping and traceroute to google.com, and I get responses (though with a slight packet loss).
That’s a contradiction in terms, isn’t it? If there is packet loss — no matter how small — then the connection is far from stable.
The question of course is where the packet loss occurs, but considering that you’re connecting via WiFi, you’re already introducing a factor of unreliability there.
I m not sure what you mean by ‘using radio waves,’ but if you’re referring to network congestion or interference, I have checked my wireless connection. I don’t think it’s an issue of network overload, but I could try switching to a different channel or using a wired connection to test
I would advise the wired connection. Anything else is subject to interference.
WiFi signals themselves are only analog radio waves, and it’s the router that has to convert them into digital signals again, based upon frequency modulation.
Addendum: As you can see below, there is nothing wrong — or at least, not network-wise — with either the AUR or the Manjaro mirrors…
[nx-74205:/dev/pts/3][/home/aragorn]
[aragorn] > ping -c 10 aur.archlinux.org
PING aur.archlinux.org (2a01:4f9:c010:50::1) 56 data bytes
64 bytes from aur.archlinux.org (2a01:4f9:c010:50::1): icmp_seq=1 ttl=50 time=45.7 ms
64 bytes from aur.archlinux.org (2a01:4f9:c010:50::1): icmp_seq=2 ttl=50 time=59.5 ms
64 bytes from aur.archlinux.org (2a01:4f9:c010:50::1): icmp_seq=3 ttl=50 time=45.0 ms
64 bytes from aur.archlinux.org (2a01:4f9:c010:50::1): icmp_seq=4 ttl=50 time=50.6 ms
64 bytes from aur.archlinux.org (2a01:4f9:c010:50::1): icmp_seq=5 ttl=50 time=43.6 ms
64 bytes from aur.archlinux.org (2a01:4f9:c010:50::1): icmp_seq=6 ttl=50 time=52.1 ms
64 bytes from aur.archlinux.org (2a01:4f9:c010:50::1): icmp_seq=7 ttl=50 time=40.2 ms
64 bytes from aur.archlinux.org (2a01:4f9:c010:50::1): icmp_seq=8 ttl=50 time=46.0 ms
64 bytes from aur.archlinux.org (2a01:4f9:c010:50::1): icmp_seq=9 ttl=50 time=52.2 ms
64 bytes from aur.archlinux.org (2a01:4f9:c010:50::1): icmp_seq=10 ttl=50 time=61.8 ms
--- aur.archlinux.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 40.215/49.685/61.839/6.593 ms
[nx-74205:/dev/pts/3][/home/aragorn]
[aragorn] > ping -c 10 mirrors.manjaro.org
PING mirrors.manjaro.org (2a02:6ea0:c000::23) 56 data bytes
64 bytes from unn-ams.cdn77.com (2a02:6ea0:c000::23): icmp_seq=1 ttl=56 time=20.8 ms
64 bytes from unn-ams.cdn77.com (2a02:6ea0:c000::23): icmp_seq=2 ttl=56 time=20.8 ms
64 bytes from unn-ams.cdn77.com (2a02:6ea0:c000::23): icmp_seq=3 ttl=56 time=14.8 ms
64 bytes from unn-ams.cdn77.com (2a02:6ea0:c000::23): icmp_seq=4 ttl=56 time=16.5 ms
64 bytes from unn-ams.cdn77.com (2a02:6ea0:c000::23): icmp_seq=5 ttl=56 time=15.3 ms
64 bytes from unn-ams.cdn77.com (2a02:6ea0:c000::23): icmp_seq=6 ttl=56 time=15.6 ms
64 bytes from unn-ams.cdn77.com (2a02:6ea0:c000::23): icmp_seq=7 ttl=56 time=15.8 ms
64 bytes from unn-ams.cdn77.com (2a02:6ea0:c000::23): icmp_seq=8 ttl=56 time=17.8 ms
64 bytes from unn-ams.cdn77.com (2a02:6ea0:c000::23): icmp_seq=9 ttl=56 time=15.8 ms
64 bytes from unn-ams.cdn77.com (2a02:6ea0:c000::23): icmp_seq=10 ttl=56 time=13.7 ms
--- mirrors.manjaro.org ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9017ms
rtt min/avg/max/mdev = 13.728/16.689/20.789/2.282 ms
[nx-74205:/dev/pts/3][/home/aragorn]
[aragorn] >
If you can boot with another kernel you have installed; assuming maybe kernel 6.12 (LTS), 6.15, or 6.16 (and preferably on a wired connection); you could try:
