Cannot login to Vortex

[KoelianTheSecond]

In the meantime I tried myself with Wireshark, I think Vortex is trying to connect to IP 104.22.2.55 (Cloudflare) on the normal HTTPS port 443 during the login attempt from within the program.

This is the same IP that shows up if I ping Nexusmods.com and I can telnet to it without issue.

I can use the nexusmods.com website without any problem from a browser, so it's really looking like it's specifically an issue within Vortex unless I missed something in Wireshark. It is possible, it's not a program I use often or am particularly familiar with, I don't think I did though.

[Tannin42]

The connection you saw that error for was to api.nexusmods.com, for me that resolves to 172.67.15.252. It's not the same server that's hosting the site or the login system.

 

Now as to your issue: ECONNERESET literally means: Something between Vortex and the api server (not including either!) has terminated the connection

without

any

further

information.

 

All I can tell you from the error message is that it is *not* Vortex or the api server software(!).

It could be your OS, your firewall, your VPN, your http proxy, your network card, your router, your ISP, the great firewall of china as far as I know, the DDOS protection network, anything at the network center, anything on the server operating system or any router between.

 

ECONNRESET means "out of nowhere the connection was closed by the other end with no reason given" - but the other end, from Vortex's perspective is an onion with a lot of layers.

 

I know this is not satisfying but I just have very very little means of helping here. It's akin to you having a power outage while using Vortex and then expecting us to explain it.

 

What I can say is this: If this kind of problems happens to a lot of users in a short time, it's probably a server outage, server being overloaded, anything like that.

If it happens to few people over an extended period of time, it's just very unreasonable to assume it's at the server end.

 

It could be that something in your setup or your ISP or generally your location in the world causes the server to terminating your connection.

but since you've shared nothing about your end of the connection (country, ISP, ...) but only told us "trust me, it's not my end" there is nothing for anyone to work with.

[KoelianTheSecond]

I can reach api.nexusmods.com on port 443 without issue, if you want me to test some other url or ip just tell me.

 

It could be your OS

Windows 10 64 bit.

 

your firewall

Doesn't block anything outgoing and Vortex is explicitly allowed.

 

your VPN

I don't use a VPN for personal home use.

 

your http proxy

I don't have a proxy configured.

 

your network card

It would be an esoteric hardware issue indeed if it only caused one specific issue, for one specific program, every time with 100% repeatability, while not touching any other functionality of the computer in any way, shape or form over the course of months.

 

your router

It has no outgoing firewall.

 

your ISP

Telnet would verify this.

Still, as I stated before, there is no logic behind blocking only Vortex specifically. If the government hated you for some reason they'd block Nexus as a whole.

 

the great firewall of china

I can assure you I'm not a follower of Winnie. Tiananmen square massacre 1989 and all that.

 

the DDOS protection network

That would be something for you (not you specifically, whoever on Nexus' end handles this) to verify if you want my current public IP, though I have a dynamic IP and tried different internet connections so I don't see how this could be the issue.

 

anything at the network center

Should be verifiable with a Telnet, at least. If the telnet fails then this is possible. If the telnet goes through then it's Vortex.

 

anything on the server operating system

This is also on your end, unless you want to give me SSH access to the server for me to fix it myself. I'm joking of course.

 

any router between

Telnet Telnet Telnet.

 

If it happens to few people over an extended period of time

This is my case. Vortex has never worked, tried multiple times over months.

 

it's just very unreasonable to assume it's at the server end.

Doesn't seem unreasonable to me. I don't know what logging this server (or servers, depending on if it has some kind of load balancing) has but you should have something on there that says if it's even getting a communication from my IP or if it's getting interrupted before even getting there.

 

there is nothing for anyone to work with.

There is though. Tell me what IP/URL to test and on what port.

Ask me my IP (if the forum system doesn't give it to you) and check the logs.

Possibly more but whoever manages this system would surely know better than me.

 

In conclusion: Tell me what to telnet to. If it works it's not a broader connection issue.

If it doesn't work then.... I don't know. But I'll think about that possibility if and when we get there.

[Guest deleted34304850]

what version of vortex are you using?

[KoelianTheSecond]

Right now I'm on 1.5.11. Before I tried a couple versions (I had to manually update because auto updating doesn't work) all with the same behaviour.

 

EDIT:

So, I did a complete clean uninstall and reinstall. Now it works.

Guess I was right that it was a problem with Vortex and not a network issue.

Also guess I should have tried that sooner.

 

EDIT 2:

No, it is not actually fixed....

It worked the first time I opened Vortex after the reinstall. The news and other web related stuff was populated and I was able to login.

Then I closed it, reopened it and... no longer works. Same as before.

 

EDIT 3:

Does Vortex not run from a secondary disk? If I install it on my D: disk it never works.

If I install it on C: it actually seems to work...

I'm going to test it out for a bit but if that's the case you might want to fix it or at least put a warning on the download page that it must go on the system disk for Windows.

[KoelianTheSecond]

Nope, there's definitely something wrong with the program.

Yesterday once I installed it on C: instead of D: it worked fine.

Today I started it up and it's back to nothing that needs an internet connection working.

 

Now I'm trying to reinstall it but regardless of if it is on C: or D: it refuses to work.

 

EDIT:

Reinstalled many times on the default path, never worked.

Changed the path from "Vortex" to "Vortex2" and it immediately works.

 

Do I need to reinstall this bloody thing every single day in a new location for it to work?

[Guest deleted34304850]

that is totally and completely something unique to you and your set up. if it was a "program error" which you are seriously trying to frame it as, then why are you the only person reporting this?

[KoelianTheSecond]

Even if that were true, it would be completely irrelevant. This is the Vortex support forum.

Besides, maybe others who had the same issues as me were just told "Lol it's your firewall not our problem" and gave up, mister Tuxedo.

[Pickysaurus]

Nope, there's definitely something wrong with the program.

Yesterday once I installed it on C: instead of D: it worked fine.

Today I started it up and it's back to nothing that needs an internet connection working.

 

Now I'm trying to reinstall it but regardless of if it is on C: or D: it refuses to work.

 

EDIT:

Reinstalled many times on the default path, never worked.

Changed the path from "Vortex" to "Vortex2" and it immediately works.

 

Do I need to reinstall this bloody thing every single day in a new location for it to work?

 

Sounds like something locally on your PC is messing with Vortex after it has been installed.

[KoelianTheSecond]

That's possible but I don't see what could, no other program has ever had this kind of issues for me.

I'm more thinking it might be something wrong with either some temporary file or some configuration file somewhere that a reinstall doesn't clear. Something that's tied to the install path, explaining why changing it fixes the issue temporarily.

 

When it works it's actually pretty good as far as I can tell. I guess I could just reinstall it every day until I'm done with my modlist and then even if it goes "offline" it would keep working. Maybe reinstall it once a month or so to check updates.

It'd still be a thousand times better if it actually worked though.

 

Now that we've established that it's not a network issue and is in fact something with Vortex, isn't there some log file that might help you find out what's going on?