Hey are yall banning ips?

reggieArchExpert · 2026-10-17 15:39:19

For whatever reason, recently I have been having trouble accessing the wiki.archlinux.org site. Unsure if I it was because my ip was banned as I noticed I could freely access the site after restarting systemd-networkd, though I had to do this after every reboot. I mailed the accountsupport@archlinux.org team about whether or not my public ip was benned, I am not sure if they fixed this because this morning it seems like everything is working fine even after a reboot. This is very frustrating because I have frequently noticed this problem with the 'wiki.archlinux.org' site specifically though it tends to happen on rare occasion. Is there something wrong with the site, perhaps it only works with public ipv4 address?(idk I'm just guessing here)
Regardless, I would like to know as I have been experiencing this problem for about a year or so,
Thank You!

seth · 2026-10-17 16:04:00

https://status.archlinux.org says the wiki was not down - what were the exact symptoms of "having trouble accessing the wiki.archlinux.org site"?

The wiki sits behind anubis, typical problems are the hash calculation being too expensive for older™ systems and restarting systemd-networkd or rebooting will not hand you an new WAN segment but the randomized part of an IPv6 might change - do you use IPv6 to access the wiki?

reggieArchExpert · Yesterday 00:48:45

Yup! I tried inputting

 Ipv6LinkLocalAddressGenerationMode=stable-privacy

based off https://wiki.archlinux.org/title/IPv6 however this seemed to only have worked for a while. Eventually the connections eventually went back to always dropping, returning "This site can't be reached... wiki.archlinux.org unexpectedly closed the connection".

This is what I mean by "having trouble accessing the site". The packets seem to never reach the wiki but does for almost any other just fine! I would of course still like to keep both ip versions(4 and 6), I have uncommented

 precedence ::ffff:0:0/96 100

in '/etc/gai.conf' as recommended for 'prefering IPv4'. I am sure there is something I have missed, plus I have yet to reboot(though see no reason to) but will do so upon sending this reply and upgrading. If problem is somehow magically fixed, and this seems to be for certain(not random like a while ago), will let you know.
Thank You!

seth · Yesterday 07:12:47

If this fails again please post the output of

curl -vL 'https://wiki.archlinux.org/' > /dev/null

reggieArchExpert · Yesterday 20:25:22

Sure, just before I do I just wanna confirm that yes it looks like I am still receiving the same problems as before

*   Trying [2604:cac0:a104:d::4]:443...
* Host wiki.archlinux.org:443 was resolved.
* IPv6: 2604:cac0:a104:d::4
* IPv4: 209.126.35.81
* ALPN: curl offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [1573 bytes data]
* SSL Trust Anchors:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
* Recv failure: Connection reset by peer
* TLS connect error: error:00000000:lib(0)::reason(0)
* OpenSSL SSL_connect: Connection reset by peer in connection to wiki.archlinux.org:443 
* closing connection #0
curl: (35) Recv failure: Connection reset by peer

Also as mentioned before, I emailed the support team about this issue and weirdly enough it has been a couple weeks and I have yet to receive a response. I hope this is normal, I would hate to send them my ip and turns out it ends up backfiring on me . I am sure the support team is trustworthy, just a little concern I am having

seth · Yesterday 21:05:19

This indeed looks like a ban (or other firewall-related drop)

openssl s_client wiki.archlinux.org:443

The response time isn't ideal, see https://bbs.archlinux.org/viewtopic.php?id=312932 (likely understaffed and overworked)

reggieArchExpert · Yesterday 21:10:19

https://github.com/ is also giving me similar problems, returning the same output the archwiki gave 'This site can't be reached...'

Here is the output from ->

 curl -vL 'https://github.com/' > /dev/null

* Host github.com:443 was resolved.
* IPv6: (none)
* IPv4: 140.82.116.4
*   Trying 140.82.116.4:443...
* connect to 140.82.116.4 port 443 from 10.0.0.98 port 58210 failed: No route to host
* Failed to connect to github.com:443 after 3149 ms: Could not connect to server
* closing connection #0
curl: (7) Failed to connect to github.com:443 after 3149 ms: Could not connect to server

Thought to post this one as well as I found it interesting that the output from github was different versus the archwiki, simply complaining about there being no route to host(which was what I expected would come from the archwiki) unlike the wiki which seems like it is having trouble resolving due to some problems with my certificates(possible security concern?)

seth · Yesterday 21:29:32

ip a; ip r

Are you using some VPN?
Docker?

reggieArchExpert · Yesterday 21:31:02

seth wrote:

This indeed looks like a ban (or other firewall-related drop)
openssl s_client wiki.archlinux.org:443
The response time isn't ideal, see https://bbs.archlinux.org/viewtopic.php?id=312932 (likely understaffed and overworked)

Ahh as I thought. I am definitely going to send another mail to the support team to see if I can get my arch sso account on the 'allowlist', as I am tired of dealing with this(again for over a year now), and as someone who is a big fan of the wiki I should honestly be on the list anyways. So thanks for sending me the link as it reminded me to sign up for the arch sso account.

Poor staff, I will ignore the fact that it is taking a long time to get back to me on this. I have always been aware that many teams in areas involving linux were heavily understaffed but your response calms many of my concerns. On the flip side, I really hope the staff working on the archwiki(and hopefully others surrounding arch) really commit to hiring more developers and maintainers, and really beefing up their team. As I can't think of a more perfect opportunity for them to do this other than now(with the current political environment).

Last edited by reggieArchExpert (Yesterday 21:46:04)

reggieArchExpert · Yesterday 21:43:19

seth wrote:

ip a; ip r
Are you using some VPN?
Docker?

Nope but I was reading up on virsh and playing around with it a while ago. I have a virbr0 interface that is always down, barely messed around with it. Could this be the cause? If so, I definitely don't mind completely getting rid of it.

Moreover, I always try to never mess with docker as every single time I install and configure docker, it always somehow gives me problems in the end. I tend to stick to more nativey solutions(such as qemu and others). Plus I don't even have docker on my system so I definitely know the problem isn't stemming from it or even podman in particular(I disabled its service). But perhaps the problem could stem from some other type of VM?

reggieArchExpert · Yesterday 21:44:39

seth wrote:

ip a; ip r
Are you using some VPN?
Docker?

Nope but I was reading up on virsh and playing around with it a while ago. I have a virbr0 interface that is always down, barely messed around with it. Could this be the cause? If so, I definitely don't mind completely getting rid of it.

Moreover, I always try to never mess with docker as every single time I install and configure docker, it always somehow gives me problems in the end. I tend to stick to more nativey solutions(such as qemu and others). Plus I don't even have docker on my system so I definitely know the problem isn't stemming from it or even podman in particular(I disabled its service). But perhaps the problem could stem from some other type of VM?

seth · Yesterday 22:00:14

No route to host then probably means you don't have a usable IPv4 lease and are pot. operating on an IPv6 LLA only?

ping -c1 209.126.35.81

(next to ip a; ip r)

reggieArchExpert · Today 03:50:47

seth wrote:

(next to ip a; ip r)

Little bit confused what you mean by this. What do you mean by next to ip a; ip r...

reggieArchExpert · Today 07:52:18

Regardless, I don't think thats an issue because

 ping -c1 209.126.35.81

always sends and transmits packets with no loss

Arch Linux

#1 2026-10-17 15:39:19

Hey are yall banning ips?

#2 2026-10-17 16:04:00

Re: Hey are yall banning ips?

#3 Yesterday 00:48:45

Re: Hey are yall banning ips?

#4 Yesterday 07:12:47

Re: Hey are yall banning ips?

#5 Yesterday 20:25:22

Re: Hey are yall banning ips?

#6 Yesterday 21:05:19

Re: Hey are yall banning ips?

#7 Yesterday 21:10:19

Re: Hey are yall banning ips?

#8 Yesterday 21:29:32

Re: Hey are yall banning ips?

#9 Yesterday 21:31:02

Re: Hey are yall banning ips?

#10 Yesterday 21:43:19

Re: Hey are yall banning ips?

#11 Yesterday 21:44:39

Re: Hey are yall banning ips?

#12 Yesterday 22:00:14

Re: Hey are yall banning ips?

#13 Today 03:50:47

Re: Hey are yall banning ips?

#14 Today 07:52:18

Re: Hey are yall banning ips?

Board footer