Mod Organizer Spotty Downloading, Won't Log In

[atlasatlarge]

I'm having a very frustrating issues with a great tool. Mod Organizer worked just fine for a few hours and then I started having problems downloading consistently from Nexus.

 

Some mods download just fine and complete with no problem. The majority of mods stay at 0% for a few seconds until Mod Organizer pops up with an Error: Download Failed. Server Reported:. The download then immediately pauses and attempts at resuming it prompt the same error. This happens in both Chrome and Firefox. Sometimes when a file fails like this, the Mod Organizer replicates the file in the Downloads pane. The duplicate file is also paused. Attempts to delete the second file report a Failed to delete <path><mod>/7z.unfinished (obviously attempting to refer to an already deleted, unfinished file).

 

If Mod Organizer is not set to automatically log in to Nexus, the failure happens in another way. When a download is queued, Mod Organizer will prompt for a username/password. Though the combination is confirmed to be correct, the program will attempt to log in for about a minute and then display two error messages on top of each other: Server time-out and Failed to log in.

 

Regardless of what options are selected for log level in settings, the most recent file I can find in the Mod Organizer's log folder is named mo_interface and reports these two things:

[*]If using Firefox to download:

C:Program Files (x86)Mozilla Firefox

MO at: C:Program Files (x86)Mod Organizer

not primary instance, sending download message

[*]If using Chrome to download:

C:Program Files (x86)Mod Organizer

MO at: C:Program Files (x86)Mod Organizer

not primary instance, sending download message

 

I've also tried to use the .47 NMM version workaround, to no avail. What's happening here?

[Defaulteduser]

I'm having the exact same pattern, and right after I upgraded to premium so I could get all the files re-downloaded and put into MO without having to Query (which is fine, but only works sometimes). Eastern Canada for me. Nexus seems fickle at the best of times, and I suppose we are at the worst of times currently!

[DoubleYou]

I'm not sure what is up either. It is giving me the same stuff, so Nexus must have changed something, unless the recent sale on Fallout 3 is taking up all the servers, but I doubt it.

[CovertSlinky]

I just tried downloading again, this time it was a DSR patch on the nexus page, and MO downloaded it this time with no problems. I am going to try and 'check all for update" again and see if it works.

 

Yup, "check all for update" worked. So maybe the problem is resolved or something.

 

LOL, ok, after doing the check, I tried downloading the updated CBBE file, and it said download failed - server reported or some crap, I give up.

Edited August 18, 2014 by CovertSlinky

[CovertSlinky]

Yeah it's totally hit or miss, right now, I can download DSR mesh packs but it won't query the info. I can't download CBBE unless done manually, and AS-LAL just downloaded and queried the info fine. Gotta be a nexus issue with there servers, I tried using different servers for the downloads that wouldn't go through like CBBE, and it didn't make a difference.

[TheTroglodyte]

It appears to be working for me now as well! Huzzah! Thank you to everyone in this thread :)

[Shadriss]

Been like this for a few days - I wonder if Nexus went back to automatically assigned servers again? I remember we had problems like this when they tried it last time, which resulted in going back to what we had until recently. *shrug* Frustrating, but not a huge pain.

[phazer11]

Has anyone having this issue tried adding preferred servers to Mod Organizer under the Nexus tab in settings?

Mine's empty preference wise but maybe selecting some servers you know were good (or clearing the list if it's populated) might help.

[TheTroglodyte]

I did try that, unfortunately to no avail. But as I mentioned before the problem is gone.

 

 

Hmmm, now I am getting this message 

Edited August 19, 2014 by TheTroglodyte

[Darky57]

Interesting.. I am able to download today using MO without a problem. I will try playing with the preferred servers option if I have any issues again.

 

Nexus has to be experimenting with something on their servers, that is for sure.

[Nozzer66]

It's not the old issue where anything under 2 meg downloads ok, but anything above 2 meg doesn't? That's the old membership issue again if so...

 

And as a workaround, you should always be Ok to download manually.

[GSDFan]

Tannin has said on the Nexus MO page that they changed the login again and a update should be out sometime this week.

[phazer11]

Weird. It is funny that only some people were having the issue. I don't think it's a membership thing either since I am not a premium member.

[DoubleYou]

The reason is Mod Organizer stores the cookie for logged-in users. I'm already logged in back from the old login method, so I never experienced login errors. But Nexus also experienced some downtime at the same time. Everything is working for me atm, and that is because I still have my cookie.

[phazer11]

I didn't have the cookie since I installed MO 3-4 days ago (and only logged in via MO two days ago), so unless the change has been today or yesterday I don't know.

[Tannin]

Tbh. I have no clue how it could work if you don't have a cookie from an earlier attempt.

 

MO currently identifies itself with "Mozilla xyz" as the user-agent because originally the login went through the regular website-login-script (in contrast to the other request which go to separate scripts for applications) so it seemed prudent to identify as a web browser.

When the last login problems occured I changed (on request of nexus staff) the login to be the same url NMM used but I didn't change the useragent (because Mozilla continued to work so I didn't think to change it).

 

Now nexus checks the user-agent too. They have not locked out MO specifically, if I log-in with the same user-agent I use for all other requests ("Mod Organizer vX.Y (compatible with Nexus Client vA.B)") login works again, so there is no ill intend here.