IP blocked, not sure what the problem is.

[Dionysia222]

I've just assumed the Nexus was down or something, but apparently nexusmods.com is IP banned for me. I can't contact my ISP right now, so I'm just trying to determine what's gone wrong, and how it can be fixed.

 

Feel free to tell me if this is the wrong location for this.

Edited October 8, 2015 by Dionysia222

[LadyMilla]

I checked our IP block list, neither your registration IP address nor your recently used IP addresses are included.

[DrakeTheDragon]

If you're IP banned, you should be seeing a page and message informing you of such still. At least I think that's how it worked so far, staff correct me, if I'm wrong. So if you rather mistook it with "Nexus was down" here, it's more than unlikely it's a block introduced by the website. You need to "reach" the website first in order for it to be able to block you. If your browser gives you anything telling you it couldn't load the site or find the server, it can't be a block.

 

Falsely perceived down times of the Nexus for only individual persons or groups of persons rather sounds like an issue somewhere on the tracks from yourself towards the Nexus servers. It not being the same "for all users" almost eliminates the possibility of anything on the Nexus' end to be responsible for it.

 

More likely are those several DNS servers out there, directing you from the node closest to you along a network of multiple different routes until you reach the Nexus servers, for some reason choosing a wrong route and dead-ending correspondingly. They aren't always the quickest to update their routing plans, based on region and/or service provider driving them, on a regular basis, so chances are at some times they just can't connect you through.

 

Also possible is an issue with one of the CDN servers, again a 3rd party driven thing spread widely all over the world, not being up-to-date with the content they cache or just simply down without any alternatives or evade routes present, especially if the forums are still cached on CloudFlare servers or similar.

 

What the devs will need to see where exactly the issue lies, and if it's perhaps something they could/should fix for you instead, is a "trace route" listing of the nodes your request to "nexusmods.com" is hopping along until it runs into a dead end without response, a node that's down or similar. If it happens somewhere close to you, there's nothing they could do, but it also will fix itself over time. If it happens somewhere inside the Nexus server network or gateways rather, well, then they're sure to investigate any possible reasons for that to happen, even if it only affected 1 single person at this point.

 

Mine is this one for example (removed the IPs too close to me/part of our private network, as they're nobody's business but my company's):

 

 

traceroute www.nexusmods.com

traceroute: Warning: www.nexusmods.com has multiple addresses; using 77.72.3.1

traceroute to nexusmods.com (77.72.3.1), 64 hops max, 52 byte packets

1 ----------------------------- 2.531 ms 1.454 ms 2.038 ms

2 ----------------------------- 18.931 ms 18.845 ms 18.676 ms

3 ----------------------------- 20.342 ms 19.422 ms 20.140 ms

4 hh-ea8-i.hh.de.net.dtag.de (62.154.32.126) 25.990 ms 23.345 ms 23.565 ms

5 80.150.168.162 (80.150.168.162) 25.211 ms 25.075 ms 24.028 ms

6 hbg-bb4-link.telia.net (80.91.249.202) 24.195 ms

hbg-bb1-link.telia.net (80.91.246.6) 25.300 ms

hbg-bb4-link.telia.net (213.155.135.84) 23.745 ms

7 adm-bb4-link.telia.net (80.91.248.242) 34.342 ms

adm-bb3-link.telia.net (80.91.250.134) 31.734 ms

adm-bb3-link.telia.net (62.115.113.240) 29.904 ms

8 adm-b2-link.telia.net (62.115.141.17) 31.692 ms

adm-b2-link.telia.net (62.115.141.57) 33.108 ms

adm-b2-link.telia.net (213.155.137.195) 32.671 ms

9 pni-as1299-ams1.staminus.net (69.197.1.80) 38.315 ms 40.548 ms 38.279 ms

10 * * *

11 (72.8.137.62) 40.698 ms 41.900 ms 41.331 ms

12 77.72.0.6 (77.72.0.6) 40.772 ms 40.575 ms 43.083 ms

13 77-72-3-1.hosted-at.kloud.co.uk (77.72.3.1) 41.237 ms 39.423 ms 40.016 ms

But mind I'm on a Mac, and I don't know what the command or the response will look like on your system.

As you can see, mine goes through, from the Deutsche Telekom AG server closest to me, hopping over several different DNS nodes from Telia.net, until one of the Nexus servers' endpoints, without interruption or a dead end.

If your browser can't reach the domain, your's will stop at one point. And that's the point of interest to the devs, along with several of the points before that to see when it "took the wrong diversion" so to say.

 

It may be advisable to only give this info to the devs "in private" though, as giving away the wrong info in public may open your system to outside attacks. But you need to be in contact with one of them first.

 

And while I first was a little surprised how you could access "forums.nexusmods.com" without a hitch but "www.nexusmods.com" was causing a problem (if that actually "is" what you're encountering), but another quick trace route to the forums revealed a completely different route to a completely different target server, so that is that I guess. Now it's up to you.

 

 

One more thing first though! Is it only a particular game site you're having issues with or "all" of them as well as the front page? People have been reported page load issues with the Skyrim Nexus main pages quite a lot in the past, only for it to turn out it was a setting in their feed preferences for the tabs they see and certain mods they tracked making the scripts run indefinitely to obtain their tracking lists for display. Most of it was fixed long ago, but there's no saying something similar can't happen again with a different thing and under different circumstances.