All of a sudden, a few days ago, the link to these forums on the Netrunner Web site stopped working. The link is “http://forums.netrunner-os.com” and it takes me to a blank page. If I add “/index.php” to the end of the URL, it works OK. Can anyone else reproduce this?
Later … I’ve just discovered if I click the “Forums” link at the top of these forums, that also takes me to a blank page.
That’s odd because if I click on the link in your post, I get a “404 Not Found” :huh:
@roadrunner:
Try again, the link had the “)” still there…
I see nothing wrong with the links at forum or wordpress.
I’m now getting the blank page.
Digging a bit further:
[code]Pinging forums.netrunner-os.com [109.228.28.14] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 109.228.28.14:
Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),[/code]
[code]Tracing route to forums.netrunner-os.com [109.228.28.14]
over a maximum of 15 hops:
1 9 ms 7 ms 7 ms 10.153.0.1
2 7 ms 8 ms 9 ms brad-core-1b-v700.network.virginmedia.net [62.252.40.6]
3 7 ms 7 ms 7 ms brad-core-2b-ae2-0.network.virginmedia.net [212.43.163.237]
4 30 ms 7 ms 8 ms leed-bb-1b-ae6-0.network.virginmedia.net [81.97.80.121]
5 98 ms 17 ms 12 ms popl-bb-1a-as1-0.network.virginmedia.net [213.105.175.130]
6 13 ms 13 ms 13 ms popl-tmr-1-ae4-0.network.virginmedia.net [213.105.159.2]
7 22 ms 21 ms 22 ms amst-ic-1-as0-0.network.virginmedia.net [213.105.175.6]
8 20 ms 21 ms 21 ms amsix.bb-c.nkf.ams.nl.oneandone.net [195.69.144.220]
9 28 ms 29 ms 40 ms te-1-2.bb-c.the.lon.gb.oneandone.net [212.227.120.134]
10 36 ms 34 ms 33 ms te2-1.prt0.fhcon.fasthosts.net.uk [88.208.255.57]
11 33 ms 33 ms 33 ms te2-1.nx01.fhcon.fasthosts.net.uk [88.208.255.237]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
Trace complete.[/code]
Looks like this could be a routing issue.
very odd…you mean a general routing issue or just on your side?
How do you post messages then here? 
Edit: I think it’s simply a browser cache thing since we switched servers overnight to EC2, so cleaning your cache or cookies should solve it…
I’ve just cleared my browser cache and that’s fixed it, thanks 