Cant Log In To Nexus Mod Manager
Track tasks and feature requests
Fo4 Can't login with Nexus Mod Manager? Fallout 4 (self.FalloutMods) submitted 11 months ago by deleted When I try to login, it says the NMM can't connect to the server or that my firewall is blocking NMM. I don't think the server is down and I can't see any evidence of my firewall blocking NMM, and this has never happened until today. Removing Nexus Mod Manager without breaking Vortex Due to the way Nexus Mod Manager (NMM) handles mods, there are a few extra steps to remove it, to ensure you don’t get any headaches. The safest way to remove your NMM installation without impacting Vortex would be to do the following.
Join 36 million developers who use GitHub issues to help identify, assign, and keep track of the features and bug fixes your projects need.
Sign up for free See pricing for teams and enterprisesHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
commented Jan 29, 2018
Like the title says. Whenever I try to login, it gives me this error 'Cannot reach the Nexus login server. Either your firewall is blocking NMM or the login server is down.' I can however, log in on the website.. This has been going on since yesterday morning. Hp smart app not opening. |
commented Jan 30, 2018
Did you check to make sure your Firewall allows NMM to connect to the internet? |
commented Feb 3, 2018
Yes I did, I went to check in Windows Defender and I allowed NMM to have acces to the internet. The thing is that I never had problems with NMM before, it worked fine at first. I didn't download anything either, it just stopped working one day. |
commented Feb 5, 2018
Have you tried the most recent version? |
referenced this issue Feb 5, 2018
Closed'Cannot reach the Nexus login server. Either your firewall is blocking NMM or the login server is down.' #240
commented Feb 9, 2018
I'm having the same issue. Never happened before, allowed NMM in Windows Defender, and tried uninstalling and updating to the latest version. I still can't log in. |
commented Feb 10, 2018
Can you post log please? Pastebin preferred |
commented Mar 12, 2018
sorry, I am having the same issue, I have had the same issue since I downloaded NMM. would you mind telling me what log? and where to get it? and I will happily post a log with Pastebin. |
commented Mar 12, 2018
Is in documents under nexus mod manage |
commented Mar 15, 2018
i'm an old lady you gotta be a bit more specific, what is it labeled as? i see nothing in that folder that says 'log'. there is one under the steam/steamapps/common/fallout4/logs/ |
commented Mar 16, 2018
Sorry, the full path is: Or very close to it as I'm on my phone |
commented Mar 16, 2018
I am afraid I don't have anything called logs in my NMM ? idk i am at a loss sorry |
commented Mar 16, 2018
Hmm have a look around the folder them, I can't get near my computer at the moment |
commented Mar 17, 2018 • edited
edited
Having same issue on 0.64.3 version, but did not have it with 0.64.2. Also, the 0.64.3 hasn't created any logs; the only logs I have are from 0.64.2 or older versions Edit: Correction, I thought I had 0.64.3 but had 0.64.2. In 0.64.3 I can log in again, 0.64.2 was the problematic version for me. Thanks! |
commented Mar 17, 2018
OK, the first login that worked said it was sending a token. On the next reload of NMM, it asked me to enter username and password and is giving me this error again (version is 0.64.3 for certain this time) |
commented Mar 17, 2018
I'm not reading this, put it on paste bin for the love of everything |
commented Mar 17, 2018
There's no point in reading it at all. No log entries in it relate to login to Nexus, they stop after the app is done finding mods and initializing. I just deleted it since it seemed to bug you. There is an issue with login, but the logs don't have any interesting data for it. |
commented Mar 18, 2018
Well then do you want to post your Firewall rules for allowing NMM through? Or specifically add it to the Firewall so it's allowed through explicitly. |
commented Mar 18, 2018
Sure thing. Here is my physical firewall's rule for outgoing connections (allow all) I have Bitdefender for the local, software firewall. I have NMM whitelisted, and I can see it logging that it has let it pass: I have no issues logging in with versions <= 0.63.1 |
commented Mar 18, 2018
For the sake of it do you want to check Window's firewall just to appease my attention to detail |
commented Mar 18, 2018
Here you go: |
commented Mar 18, 2018
Did some poking around. The log from Bitdefender must have been when I was using 0.63.1 in earlier testing. Neither the physical firewall nor Bitdefender logs a connection attempt from 0.63.4 at all when I try to log in. On 0.63.1, I see logs in both. On 0.64.3, I can see in Resource Monitor that it is attempting to open a connection to 77.72.3.39. I am still looking for anything else that might help. I am able to ping, trace, and connect to an nginx on EPEL! page when using chrome with that IP. |
commented Mar 18, 2018
Something else for you. If I run netstat -b, I do not see any data for NexusClient.exe when spamming logon attempts. After sitting idle for about 2 minutes, one entry showed up in the netstat output. The IP address corresponds to GitHub, so I am guessing it was probably checking for NNM updates at that time. I am going to run Wireshark and attempt some more log-on's. [NexusClient.exe] |
commented Mar 18, 2018
Checked with Wireshark and confirmed with Microsoft Message Alayzer, NMM 0.64.3 does not make any network connections when attempting to sign-in. The only time it makes network connections appears to be when checking GitHub for a new version. Here are the various versions from the tracelogs, in case there is something unique about my setup. OS version: Microsoft Windows NT 6.2.9200.0 |
commented Mar 21, 2018
I haven't found any more data that seems useful. For now, I have 0.64.3 and 0.64.1 installed to separate directories so I can continue to download mods, but still test 0.64.3 for you if you need more feedback. |
commented Apr 7, 2018
This issue magically resolved itself recently. I can log in on 0.64.3 now. I haven't used my computer in a couple weeks, so I am not sure exactly when it started working. |
commented May 10, 2018
I'm having exactly the same issue as the original poster 'Cannot reach the Nexus login server. Either your firewall is blocking NMM or the login server is down.'. I've updated to Nexus.Mod.Manager-0.65.4. I've disabled Windows & Norton firewalls. Initially it prompts me to enter username & password. If I type a random username it says 'Invalid Username or password'. If I type the correct username or wrong or correct password, then it give the above 'cannot reach..' error. |
commented May 10, 2018
@PeterHughes This issue was impacting me 2 months ago and self-resolved. TL;DR: It's probably not your firewall if it you were able to login on previous versions. No idea why it started to work for me, nothing had been recently changed to cause that. I believe there is an issue either with the logon server or an ISP/interchange level issue. Some in the forums have suggested that the login server gets DDoS'd from time to time, but it doesn't make sense if that is only impacting certain users. ISP level issues would impact all users from the same ISP, so it could be that. One of the really telling things I saw was that when using an older version of NMM, I could log in fine. If they use the same server to login, then it doesn't make much sense that one version would work and the other wouldn't unless something outside of your system configuration was causing it. |
commented May 10, 2018 • edited
edited
Fixed: I was using the wrong username. Not sure why that would return a 'cannot reach server..' error, but it did.. |
commented May 11, 2018
Same problem; Can login just on the website, but NMM will not let me login. |
commented May 12, 2018
Installing the 0.65.2 version fixed it for me -- thanks for that! |
commented May 19, 2018 • edited
edited
I had 0.63 version installed and had the same issue. After I've updated to 0.65.2, the error went away and I was able to login again. |
commented Jul 19, 2018
This issue has several problems listed, and is getting pretty old, so grab NMM 0.65.9 and see if you still have problems. If you still can't log in with 0.65.9, create a new issue with a good description of what doesn't work, and include as much info as you can (trace log file if applicable). Closing this issue as inactive/bloated :) |
commented Dec 11, 2018 • edited
edited
Adding both inbound and outbound connections in firewall and using your display name (not associated email) and password as allowed me to connect on 35.2 |
Like many Bethesda games, modding is one of the big draws of games like Skyrim and Fallout 4 on the PC. Nexus Mod Manager is one of the best ways to install mods on your favorite games, and we’re here to show you how to use it.
Nexus Mod Manager actually supports many other games, too, including The Witcher games, Dragon Age, Dark Souls, and other Fallout and Elder Scrolls games, so you should be able to adapt the instructions for any other game Nexus Mod Manager supports. We’ll use Fallout 4 in today’s example.
How to Enable Modding in Fallout 4
Even though you’ll be using the Nexus Mod Manager, you’ll still have to perform a quick tweak to Fallout 4’s game files before it will accept the mods you install. (Other games, like Skyrim, won’t require this tweak, and you can skip to the next section).
First, navigate to the Fallout 4 folder in your documents directory. You’ll find it under C:UsersYOURNAMEDocumentsMy GamesFallout4
.
Double-click the Fallout4Prefs.ini
file to open it in your default text editor. It’ll open in Windows Notepad unless you’ve installed another text editor like Notepad++.
Scroll down to the very bottom of the text file and you’ll see a [Launcher]
section. Add the following line below it:
Click File>Save to save the file, and then close Notepad.
Double-click the Fallout4Custom.ini
file to open it in your default text editor. Add the following lines to the end of the file:
Click File > Save to save the file, and then close Notepad. Fallout 4 will now accept and use the mods you install.
How to Install and Configure Nexus Mod Manager
It’s possible to manually install mods for a lot of games, or use Steam’s built-in Workshop (for games that support it). However, we recommend using the Nexus Mod Manager tool to make this process easier and reduce the risk you’ll break something while installing a mod.
Download Nexus Mod Manager and install it on your PC. If you don’t yet have a Nexus Mods account, you’ll be informed you need to register for a free account to download it. You’ll be asked to sign up for a paid supporter membership during the sign-up process, but you can just scroll down to the bottom of the page and click “Create Account” to continue.
Launch Nexus Mod Manager after you install it and it will search your PC for games. If you have Fallout 4 installed, it will find it. Just click the checkmark to confirm Fallout 4 is installed at that location and then click “OK.”
Select “Fallout 4” in the list of installed games and click “OK.” If you always want to use this program to manage Fallout 4 mods, click the “Don’t ask me next time” checkbox here.
You’ll be informed that you need to set up the paths where Nexus Mod Manager will store mod-related files. Click “OK” to continue and you’ll see a Fallout 4 Setup screen. By default, Nexus Mod Manager will store these files under C:GamesNexus Mod ManagerFallout4
.
There’s a problem with these default folder settings. It won’t work unless you run Nexus Mod Manager as Administrator. If you run it normally, you’ll see an error informing you that Nexus Mod Manager is “unable to get write permissions for” the directory.
To solve this, set the folder paths to something like C:UsersYOURNAMEDocumentsNexus Mod ManagerFallout4
. Alternatively, keep the default folders and run Nexus Mod Manager as an Administrator. To do so, right-click the Nexus Mod Manager shortcut and select “Run as administrator.”
To always run it as Administrator, right-click the shortcut and select “Open file location.” Right-click the “Nexus Mod Manager” Shortcut, select “Properties, click the “Compatability” tab, and enable the “Run this program as an administrator” checkbox. Click “OK” to save your settings and Windows will always launch Nexus Mod Manager with Administrator permissions.
How to Install Fallout 4 Mods
You’ll want to sign into Nexus Mod Manager with your Nexus account for easy mod installation. To do so, click the profile icon next to “You are not logged in” at the bottom-left corner of the Nexus Mod Manager window. Enter your Nexus Mods username and password here.
You’ll then see a “Logged in” message here, informing you you’re logged in.
You can now head to the Fallout 4 Mods category page to browse and search the available mods. If you’re logged in, you’ll see “[Name]’s account” at the top-right corner of each web page. If you’re not, click the “Log in” link at the top-right corner of the web page.
Locate a mod you want to install and click the “Download (NMM)” button to download the mod with Nexus Mod Manager. Your browser will hand off to the Nexus Mod Manager application, which will download the mod you chose.
The Download link at the top of each mod’s page will download the main, current version of the mod. However, some mods offer multiple versions, or additional files.
To download multiple versions or optional files a mod offers, scroll down on its download page and click the “Files” tab. You’ll see the various files the mod offers, along with explanations from the mod author about what they do. Click “Download With Manager” to download the mod files you want.
Once it’s downloaded and installed, locate the mod in the list, select it, and click the green checkmark button in the sidebar to enable it. You can click the red cancel button that appears in this location afterwards to disable a mod.
Some mods will walk you through a setup process the first time you enable them. You’ll be able to choose different options, depending on the mod. Go through the setup process and select your desired options to enable the mod.
To change these options later, right-click the mod in the Nexus Mod Manager list and select “Reinstall Mod.” You’ll see the same setup screens again.
Now all you need to do is launch Fallout 4. You can do so using the “Launch Fallout4” button at the top-left corner of the screen or just launch it through Steam normally. Load your existing game or create a new one–either way, the mods you installed will immediately take effect.
To disable or uninstall a mod later, close Fallout 4 and open Nexus Mod Manager. Right-click the mod you want to disable or uninstall and select “Deactivate” to disable the mod or “Uninstall and Delete” to remove the mod from your system.
You can also click the settings icon at the top of the Nexus Mod Manager window and use the “Disable All Active Mods” or “Uninstall All Active Mods” options to quickly disable or uninstall all currently activate mods.
How to Configure Your Mod Load Order (and Why It Matters)
The above process should work perfectly if you’re only using one mod. However, if you plan to install several mods, you may need to think about your mod load order.
This is exactly what it sounds like. Fallout 4 will load mods one by one, in the order you specify.
If you have multiple mods installed, some of them may overwrite each other’s changes. For example, you may have one “total overhaul mod” that tweaks a large amount of things in the game, including all the weapons. Second, you may have a small mod that makes a single weapon function in a certain way. If the game loads the small mod before the larger mod, its tweaks will be overwritten by the total overhaul mod. To have the second mod function, the larger total overhaul mod needs to be loaded first.
This only applies to mods that have plugins. If you install a mod with a plugin, it’ll appear on the “Plugins” tab, as well as the “Mods” tab. To control the load order, click over to the “Plugins” tab. Select a mod you’ve installed and click the up and down arrows in the left pane to adjust the load order. The “Masters” information for a plugin tells you when a mod depends on another mod. For example, in the screenshot below, “Homemaker – SK Integration Patch.esp” depends on Fallout4.esm, SettlementKeywords.esm, and Homemaker.esm. It must appear after all these other plugins in the list. Nexus Mod Manager won’t let you move it above those other plugins in your load order.
It may take some trial and error to get the load order working the way you want it. Some mod authors may provide information about recommended load order on their mod’s download page.
If you want some additional help, you can try using LOOT, the Load Order Optimization tool. It works by examining your mods and attempting to decide the correct order so that all dependencies are satisfied and that each mod has a maximum impact on your game. It will recommend you a load order you can configure in Nexus Mod Manager.
How to Deal With Mod Conflicts, or “Overwrites”
Can't Log In To Nexus Mod Manager Fix
There’s another way mods can conflict, and it’s totally separate from your plug-in load order. Sometimes, two mods overwrite the same files in your game, and you’ll need to decide which one you want to take precedence. We’ll use Skyrim here as an example. Skyrim and Fallout 4 share the same engine, and work similarly.
Can T Log Into Nexus Mod Manager Server Error
Texture packs are a great example of this. For example, the Skyrim HD mod adds over 2,000 high-res textures to the game, making it look absolutely fantastic. But there are also smaller mods for specific textures–like this Real Ice and Snow mod–that (sometimes) look even better. Let’s say you want to replace most of your game with the Skyrim HD pack, but want the ice and snow from the Real Ice and Snow mod.
First, you select the Skyrim HD mod and enable it, just like you would any other mod. If you start the game at this point, you’d see that the Skyrim HD textures have been applied. Then, when you enable the Real Ice and Snow mod, you’ll get this message:
This happens because you have two mods–Skyrim HD and Real Ice and Snow–attempting to modify Skyrim’s snow and ice textures. If you want Real Ice and Snow, you’ll click “Yes to All” or “Yes to Mod” to overwrite Skyrim HD’s textures. If you prefer Skyrim HD’s textures, you’d click “No to All” or “No to Mod”, and any conflicting textures from Real Ice and Snow would not be applied.
You could load these mods in the opposite order, too. If you loaded Real Ice and Snow first, you’d get the ice from that mod, and decide whether to overwrite it with Skyrim HD after the fact.
If you’re installing a lot of mods, we recommend loading the bigger, game-sweeping mods first as your “base layer”–in the example above, that’s Skyrim HD. Then, load the smaller, more specific mods after, always choosing “Yes to All.”
The more mods you install, the more complex the process becomes, and we’ve only scratched the surface here–there are many mods that require even more steps outside of Nexus Mod Manager to work (like ENBs or interface modifications). But the more you do it, the more it’ll become second nature. If you ever have questions, check the Discussion tab on the offending mod’s Nexus page–there’s a lot of good info to be had, and developers are often pretty responsive.
READ NEXT- › How Do Internet Speed Tests Work? (and How Accurate Are They?)
- › How to Stream UFC 239 Jon Jones vs. Santos Online
- › How to Check Your Wi-Fi Signal Strength
- › What Is “Upscaling” on a TV, and How Does It Work?
- › How to See the Applications Using Your Network on Windows 10