Titan Network
More Titan Projects => ParagonWiki => Feedback => Topic started by: Roderick on July 10, 2012, 03:31:31 PM
-
EVERY page of the wiki is redirecting to the main page after a few second delay. I'm using Firefox, and haven't tested any other browsers, FWIW.
EDIT: I use http://paragonwiki.com . I just tested http://wiki.cohtitan.com and it worked fine; only the former address seems to be messed up.
-
That's odd. I'm not seeing that at all.
Running Firefox 13.0.1 here.
-
Getting same issue here - tested on Chrome and IE 9.
IE works fine, Chrome does not
Trying to log in to see if it's related to that, and logging in also redirects (can not actually get logged in)
Edit also - can confirm that http://wiki.cohtitan.com does work as well
-
That's odd. I'm not seeing that at all.
Running Firefox 13.0.1 here.
Are you using the paragonwiki link or the cohtitan one? I'm only having that issue on paragonwiki.
-
I'm specifically using Paragonwiki. (www.paragonwiki.com is on the whitelist here at work, wiki.cohtitan.com is not and is blocked)
Also tried in IE8 and IE8 64-bit with no observed issue. Chrome won't install, so I can't check it.
-
Strange. I'm also on 13.0.1, so I don't know why it's happening for me, but not you. Try a forced refresh (Ctrl+F5)? Maybe you're loading an old cached version.
-
http://paragonwiki.com/wiki/Main_Page works
click Badges http://paragonwiki.com/wiki/Badges laods then redirects to http://paragonwiki.com/w/index.php
http://paragonwiki.com/w/index.php infinite redirect to http://paragonwiki.com/w/index.php
installed no script for chrome, and retested with JS turned off - no redirects and links work correctly
enabled JS for paragonwiki.com - works
enabled JS for cloudfare.com - fails with redirects
Edit - followup - wiki.cohtitan with all JS enabled including cloudfare works fine
-
I turned off JS and logged in using paragonwiki.com - once i was logged in I turned back on all JS. Everything worked fine. I then logged out (with JS still turned on) and started getting redirects
-
Strange. I'm also on 13.0.1, so I don't know why it's happening for me, but not you. Try a forced refresh (Ctrl+F5)? Maybe you're loading an old cached version.
Nope. Tried the forced refreshes as well. I even used the links that MultipleGirl placed in the post above and forced refreshes. I was able to get to the Badges page with no issues.
Just on a very outside chance, I wonder if the last few IP addresses in a tracert command would reveal anything. (I can't do that from here at work since tracert dies at the proxy server.)
Based on MultipleGirl's last post, let me try logging out and see what happens.
Edit: Nevermind. I was already logged out.
-
tracert pargonwiki.com
3 14 ms 15 ms 15 ms adsl-108-65-95-254.dsl.rcsntx.sbcglobal.net [108.65.95.254]
4 16 ms 17 ms 17 ms 12.83.33.49
5 17 ms 17 ms 17 ms gar27.dlstx.ip.att.net [12.123.16.77]
6 64 ms 19 ms 19 ms ae-9.r01.dllstx04.us.bb.gin.ntt.net [129.250.8.237]
7 17 ms 20 ms 16 ms ae-9.r07.dllstx09.us.bb.gin.ntt.net [129.250.2.208]
8 44 ms 23 ms 19 ms xe-2-0-2.ar1.dfw1.us.nlayer.net [69.31.63.172]
9 18 ms 19 ms 19 ms ae0-50g.cr1.dfw1.us.nlayer.net [69.31.63.125]
10 42 ms 43 ms 41 ms xe-0-2-1.cr1.ord1.us.nlayer.net [69.22.142.4]
11 45 ms * 41 ms ae1-30g.ar1.ord1.us.nlayer.net [69.31.111.134]
12 42 ms 45 ms 46 ms as13335.xe-8-0-3.ar1.ord1.us.nlayer.net [69.31.110.90]
13 39 ms 43 ms 42 ms 141.101.125.164
tracert wiki.cohtitan.com
3 16 ms 17 ms 17 ms adsl-108-65-95-254.dsl.rcsntx.sbcglobal.net [108.65.95.254]
4 17 ms 17 ms 17 ms 12.83.34.13
5 17 ms 17 ms 17 ms gar27.dlstx.ip.att.net [12.123.16.77]
6 18 ms 19 ms 20 ms ae-9.r01.dllstx04.us.bb.gin.ntt.net [129.250.8.237]
7 16 ms 17 ms 17 ms ae-9.r07.dllstx09.us.bb.gin.ntt.net [129.250.2.208]
8 19 ms 25 ms 21 ms xe-4-0-1.ar1.dfw1.us.nlayer.net [69.31.63.170]
9 16 ms 17 ms 15 ms ae0-50g.cr1.dfw1.us.nlayer.net [69.31.63.125]
10 41 ms 41 ms 42 ms xe-0-2-1.cr1.ord1.us.nlayer.net [69.22.142.4]
11 42 ms * 42 ms ae1.ar2.ord1.us.nlayer.net [69.31.111.146]
12 43 ms 41 ms 43 ms 69.31.105.34
13 40 ms 41 ms 42 ms 108.162.192.101
-
I turned off JS and logged in using paragonwiki.com - once i was logged in I turned back on all JS. Everything worked fine. I then logged out (with JS still turned on) and started getting redirects
This worked for me as well. After I logged out, I went to wiki.cohtitan and logged in, then switched to paragonwiki, and it didn't recognize me as logged in. Is that normal?
-
Yes, that's normal because they're two different URLs so the cookies can't talk to each other.
-
tracert pargonwiki.com
...
13 39 ms 43 ms 42 ms 141.101.125.164
tracert wiki.cohtitan.com
...
13 40 ms 41 ms 42 ms 108.162.192.101
You know, I wasn't actually expecting to learn anything here, but I did.
The final address for paragonwiki.com (141.101.125.164) seems to be owned by CloudFlare-EU in the UK according to http://ip-lookup.net.
The final address for wiki.cohtitan.com (108.162.192.101) is owned by CloudFlare in San Francisco.
I would have expected the two final addresses to match since they're both supposed to be retrieving the data from the same server. And I certainly didn't expect one to be hitting an address in the US and another to be hitting an address in the UK.
Is that relevant? I'm not sure, but it certainly seems like it could be.
-
here's more followup - if i change my DNS servers from 4.2.2.1 (Verizon's?) to 173.45.59.100 (alex.ns.cloudflare.com) and 173.245.58.144 (sara.ns.cloudflare.com) from the http://whois.domaintools.com/paragonwiki.net everything works fine
could this be more related to whatever DNS thing the FBI did in response to the botnet
-
Funny you ask that, because that's what I was originally wondering when I suggested running the tracert.
-
If I clear my cache in Chrome, I can load up the main page, and click a link. Then about 3-5 seconds later the redirects will start.
Once they start, if I open a new instance and retry the main page - redirects start immediately. I then clear my cache again, and all seems well for about 3-5 seconds.
-
Yes, that's normal because they're two different URLs so the cookies can't talk to each other.
Makes sense. If I'd thought further on it, I should have been able to figure that one out myself. I'm going to back out of the testing now, since eabrace and MultipleGirl seem to know what they're doing, and any testing I contributed from this point on would be completely random, and probably won't help much, if at all.
-
I just disabled Cloudflare for these domains. Please reply if you continue to have this issue.
-
That did correct the issue (right in the middle of typing a post with other feedback on the problem)
-
That did correct the issue (right in the middle of typing a post with other feedback on the problem)
Awesome! :D
-
I just disabled Cloudflare for these domains. Please reply if you continue to have this issue.
That didn't clear up the issue for me, then I realized I was using the same page to test that I had been earlier. Using different pages didn't trigger the issue, and clearing my cache resolved the issue on previously loaded pages.
Thanks for looking into it, everyone!