From IP 114.41.23.209 I sent
GET / HTTP/1.1
Host: codex.buddypress.org
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:19.0) Gecko/20121207 Firefox/19.0 Iceweasel/19.0a2
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Encoding: gzip, deflate
Cookie: …
Connection: keep-alive
Cache-Control: max-age=0
We’ve heard reports but not been able to recreate this which is hindering further investigation. If you can reliably recreate, are you able to do a traceroute to codex.buddypress.org and see if something’s timing out?
Well I don’t think traceroute will help as it is a logged in vs. logged out problem, but here you go anyway:
$ tcptraceroute codex.buddypress.org
Selected device ppp0, address 114.41.23.209, port 50340 for outgoing packets
Tracing the path to codex.buddypress.org (72.233.56.139) on TCP port 80 (http), 30 hops max
1 168.95.98.254 (168.95.98.254) 33.760 ms 38.454 ms 33.979 ms
2 fyfy-3301.hinet.net (168.95.150.6) 39.644 ms 36.723 ms 35.416 ms
3 CHCH-3111.hinet.net (220.128.18.18) 46.183 ms 50.956 ms 43.635 ms
4 220-128-18-34.HINET-IP.hinet.net (220.128.18.34) 44.443 ms 40.464 ms 43.420 ms
5 r4101-s2.tp.hinet.net (220.128.7.1) 40.937 ms 43.177 ms 42.678 ms
6 r4001-s2.tp.hinet.net (220.128.7.213) 42.175 ms 44.737 ms 43.021 ms
7 r11-pa.us.hinet.net (211.72.108.217) 167.351 ms 175.713 ms 162.387 ms
8 TenGigE0-0-4-0.GW5.SCL2.ALTER.NET (152.179.112.69) 181.372 ms 170.692 ms 173.893 ms
9 0.xe-2-0-2.XT1.SCL2.ALTER.NET (152.63.56.21) 196.219 ms 173.055 ms 172.949 ms
10 0.xe-5-1-0.XL3.DFW7.ALTER.NET (152.63.101.86) 216.396 ms 216.984 ms 301.883 ms
11 TenGigE0-6-0-0.GW4.DFW13.ALTER.NET (152.63.101.5) 221.692 ms 227.942 ms 224.156 ms
12 internapGIGE1-gw.customer.alter.net (65.208.15.230) 218.617 ms 223.888 ms 222.930 ms
13 border1.pc1-bbnet1.dal004.pnap.net (216.52.191.19) 220.379 ms 224.200 ms 220.880 ms
14 layered-11.border1.dal004.pnap.net (63.251.44.74) 221.068 ms 213.366 ms 213.383 ms
15 * * *
16 wordpress.org (72.233.56.139) [open] 218.273 ms 216.009 ms 223.296 ms
I bet it is some kind of anti-spam thing against smaller countries like Taiwan. But I am able to use http://codex.wordpress.org just fine when logged in or not.
All I had to do was change
$ HEAD -PSU -H 'Cookie: buddyorg_logged_in=jidanni...efd6' https://codex.buddypress.org/ to
$ HEAD -PSU -H 'Cookie: buddyorg_logged_in=jidanni...efd5' https://codex.buddypress.org/
and I could get in fine. Same results no matter if my IP is via the USA or TW.
So perhaps: create a new account, login, then try to connect to https://codex.buddypress.org/
Then logout, and try again.
Sorry about that. I fixed what was causing the error for your first account. A bit of code I wrote to automatically grant the “Editor” role to the codexes wasn’t working theme-side. If you visited wp-admin, it would grant the role, and everything would fix itself.
This is why reports have been sporadic. Users with roles already, could see the codex fine. Logged out users, also could see it fine. Users that have never visited the codex before, and were trying to now, were seeing the error.
Anyways, fixed!
Fantastic. Closing this, as resolved.
