TygerKD Posted June 5, 2013 Share Posted June 5, 2013 It won' let me access the skyrim.nexusmods.com for some reason is it down or did I do something wrong? all I've been able to do is download he mod manager. Link to comment Share on other sites More sharing options...
badboy64 Posted June 5, 2013 Share Posted June 5, 2013 I am getting the samething. The problem isn't on your end at all. I wish they would fix as it has been happening most of the day. Link to comment Share on other sites More sharing options...
Lothak Posted June 5, 2013 Share Posted June 5, 2013 Past few Days have been Slow, but today the site is unreachable. Link to comment Share on other sites More sharing options...
whistlingbomb Posted June 5, 2013 Share Posted June 5, 2013 This has been happening to me for a while too, 502s and 504s left and right. Other users have had these exact same problems as far back as April, has anyone in the Nexus staff even acknowledged the problem yet? Link to comment Share on other sites More sharing options...
Reynard131 Posted June 5, 2013 Share Posted June 5, 2013 Has anyone done a trace route ?? Until you do that you are jerkin the gherkin !! hehe :wallbash: :wallbash: Link to comment Share on other sites More sharing options...
JakeDragon555 Posted June 5, 2013 Share Posted June 5, 2013 8 38 ms 105 ms 37 ms 107.14.19.1549 * * 36 ms ae1.pr1.dfw10.tbone.rr.com [107.14.17.234]10 35 ms 36 ms 46 ms te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.54.11.49]11 52 ms 37 ms 37 ms be2031.ccr21.dfw01.atlas.cogentco.com [154.54.7.45]12 40 ms 43 ms 44 ms te0-0-0-2.mpd22.iah01.atlas.cogentco.com [154.54.25.222]13 59 ms 64 ms 61 ms te0-0-0-2.mpd21.atl01.atlas.cogentco.com [154.54.24.5]14 58 ms 61 ms 59 ms te0-5-0-7.mpd21.dca01.atlas.cogentco.com [154.54.25.253]15 60 ms 61 ms 59 ms te0-7-0-8.mpd21.jfk02.atlas.cogentco.com [154.54.5.97]16 144 ms 142 ms 143 ms te0-2-0-2.mpd22.lon13.atlas.cogentco.com [154.54.42.54]17 132 ms 140 ms 144 ms te0-3-0-1.ccr22.lon01.atlas.cogentco.com [130.117.0.237]18 139 ms 143 ms 145 ms te2-1.mag02.lon01.atlas.cogentco.com [154.54.74.114]19 146 ms 138 ms 146 ms 130.117.123.16220 141 ms 147 ms 132 ms 77.72.0.621 149 ms 142 ms 146 ms skyrim.nexusmods.com [77.72.6.50] Link to comment Share on other sites More sharing options...
Lothak Posted June 5, 2013 Share Posted June 5, 2013 Tracing route to skyrim.nexusmods.com [77.72.6.50] over a maximum of 30 hops: 4 13 ms 11 ms 12 ms ool-4353e38d.dyn.optonline.net [67.83.227.141] 5 12 ms 11 ms 14 ms 65.19.121.33 6 15 ms 14 ms 12 ms 64.15.2.190 7 12 ms 12 ms 12 ms te0-7-0-3.ccr21.jfk04.atlas.cogentco.com [154.54.11.249] 8 14 ms 12 ms 12 ms te0-1-0-2.mpd22.jfk02.atlas.cogentco.com [154.54.1.161] 9 102 ms 88 ms 100 ms te0-0-0-5.mpd22.lon13.atlas.cogentco.com [154.54.42.45] 10 91 ms 90 ms 97 ms te0-3-0-6.ccr22.lon01.atlas.cogentco.com [154.54.74.61] 11 87 ms 88 ms 95 ms te2-1.mag02.lon01.atlas.cogentco.com [154.54.74.114] 12 99 ms 90 ms 100 ms 130.117.123.162 13 85 ms 94 ms 86 ms 77.72.0.6 14 94 ms 100 ms 101 ms skyrim.nexusmods.com [77.72.6.50] Trace complete. Link to comment Share on other sites More sharing options...
Lothak Posted June 5, 2013 Share Posted June 5, 2013 Seems to me that the problem lies with the site itself. Link to comment Share on other sites More sharing options...
CrispyWalrus Posted June 5, 2013 Share Posted June 5, 2013 (edited) Has anyone done a trace route ?? Until you do that you are jerkin the gherkin !! hehe :wallbash: :wallbash: Traceroute is useless here. You are reaching their site (at least the point of contact receiving your domain:80 http request). If you weren't you would not get a 502/504 code. 5xx codes denote server error, while if it was client connectivity likely you would be seeing 4xx. Seems to me that the problem lies with the site itself. It is their site. Basically the site front end is not talking to the backend (or the middle-- we can't be entirely sure as that would require an insider's knowledge of their site and server architecture. Likely beyond the web server itself the rest are even on a private network and not publicly reachable-- i.e. only the web server can actually talk to the db server who likely then talks to file servers when sending you a download. The Nexus makes use of Ajax-- using javascript and xml to collate bits of a page that get pieced together for you. 502 Bad Gateway: The server was acting as a gateway or proxy and received an invalid response from the upstream server. 504 Gateway Timeout: The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. They did have the recent downtime trying to upgrade and backed any changes out so theoretically nothing changed... Also search Nexus and 502 and you'll see this is nothing new, just more common of late. My best guess is that it is just heavy traffic lately unless something really changed. I only make this guess because the 502 is sporadic and not constant. Refresh the page and sometimes it corrects instantly and other times stalls. Without that architectural layout, knowledge of their code, server logs, and a sniffer on their backend network who can say for sure what the problem is... Welcome to the dark. :smile: Edited June 5, 2013 by CrispyWalrus Link to comment Share on other sites More sharing options...
Dark0ne Posted June 5, 2013 Share Posted June 5, 2013 Just come back from dinner; seems to be working fine for me! Link to comment Share on other sites More sharing options...
Recommended Posts