Jump to content

Can't login to Vortex


harlandgg

Recommended Posts

(I am copy/pasting the feedback I was trying to send via the Vortex app, since it wouldn't send it, see the log at the end.)

Hi, my username is harlandgg.

I installed Vortex and was able to login only the first time. Tried to download the Gate to Sovngard collection but interrupted the process, and deleted everything bacause I didn't proprely set up my folders.
Then ,for the last four days, each time I tried to log in, the app would take me on the browser and ask me to authorise, to no effect on the app. The tokens provided were always invalid.
I tried reinstalling the app several time, deleting every folder left behind when uninstalling, restarted my computer, switched the default broswer to Chrome and Edge, disabled kaspersky while trying to log in, add the app to "trusted" in kaspersky, tried an earlier version of Vortex, searched on many forums topics for solutions... None of this solved the issue.
Obviously since the first reinstall, I have no mod installed, and no game managed.
Also, each time I start the app, I have a "check for update failed" notification.
My version of Vortex is 1.12.6. on Windows 10.

Here is the log of the error that pops when I'm trying to send this feedback via vortex:

Error: read ECONNRESET
    at __node_internal_captureLargerStackTrace (node:internal/errors:496:5)
    at __node_internal_errnoException (node:internal/errors:623:12)
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)

Called from:

  at null (A:\Jeux\Vortex\Installation 1.12\resources\app.asar\renderer.js:6451:37)
  at null (A:\Jeux\Vortex\Installation 1.12\resources\app.asar\renderer.js:6943:188)
  at tryCatcher (A:\Jeux\Vortex\Installation 1.12\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
  at Promise._settlePromiseFromHandler (A:\Jeux\Vortex\Installation 1.12\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31)
  at Promise._settlePromise (A:\Jeux\Vortex\Installation 1.12\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18)
  at Promise._settlePromise0 (A:\Jeux\Vortex\Installation 1.12\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10)
  at Promise._settlePromises (A:\Jeux\Vortex\Installation 1.12\resources\app.asar\node_modules\bluebird\js\release\promise.js:729:18)
  at _drainQueueStep (A:\Jeux\Vortex\Installation 1.12\resources\app.asar\node_modules\bluebird\js\release\async.js:93:12)
  at _drainQueue (A:\Jeux\Vortex\Installation 1.12\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9)
  at Async._drainQueues (A:\Jeux\Vortex\Installation 1.12\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5)
  at Async.drainQueues (A:\Jeux\Vortex\Installation 1.12\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14)
  at processTicksAndRejections (node:internal/process/task_queues:95:5)


EDIT : I can't seem to be able to attach a log file to this due to a server error...
 

Edited by harlandgg
Link to comment
Share on other sites

After a few days, I finally found what caused the issue : the installation folder in wich I installed vortex had a "." in it's name.
Replaced it with a "-" and I could then log in.

EDIT : Actually, the issue came back as soon as I closed and reopened the aplication, the only solution that works is to actually rename the installation folder each time I launch the app, meaning the "." wasn't part of the issue. This is a problem...

I was able to attach the log file this time.

vortex.log

Link to comment
Share on other sites

I have no trouble believing that the problem is on my end, but I can't really make anything of your answer. Do you have any suggestions on where I should look or what should I do ?
Because like I've expressed, I've tried just about everything I could think of, for days. And it's not like I had similar issues with any other app, this is specific to Vortex.

Link to comment
Share on other sites

  • 2 weeks later...

It's been weeks, are you just not going to answer ?

I'm sorry to say, but this kind of response would be okay if all of this was free, but I happen to be paying for a service that does not properly work despite my best efforts, and indeed would not be working at all if I didn't figure out  that bizarre fix of changing the installation folder's name every time I want to use the app.

Please don't take it the wrong way, but what good is it to ask to provide a log and a maximum of details about our issues if your just going to say it's a problem with our setup and leave it at that ? And again, weither my setup is interfering with your app or not, this is still an issue exclusive to Vortex, and I don't have neither the time nor the knowledge that you have to solve it, hence why I'm paying in the first place. 

So could you please help me, or at the very least point me in the right direction ?

Thank you.
 

Link to comment
Share on other sites

On 10/21/2024 at 3:42 AM, Pickysaurus said:

This is almost certainly a problem with your local setup. Your PC is either interfering with Vortex's network requests or blocking its communication with our API. 

@harlandgg Check and any firewalls on your PC, your router or modem, etc.  If you aren't using a third-party antivirus or firewall on your PC (like McAfee, Norton, Avast, etc), then start at the built-in Windows Security/Microsoft Defender in your Windows settings.

(I don't use Vortex or Windows myself, so I don't know the steps for this offhand.  I went from Win7 to Linux, and never used MS's antivirus/security stuff.)

Link to comment
Share on other sites

  • 2 weeks later...

Having checked everything I could, like I initially did, I still haven't find out where the issue is coming from.

Each time I want to dowload something, I rename the installation folder of Vortex, but each time I use a folder name, I can never use it again to make it work. I have to give it a new name each time and even then it doesn't always work.

At this point I feel that even if the issue is that there's a conflict between Vortex and my setup, then that has more to do with Vortex than anything else, since again, I don't have any such issues with any other app including other mod manager that can connect to Nexusmod.

I hope this will get fixed in a future update or that at least some way to fix/prevent this will get mentionned in the troubleshooting section.

Thank you nonetheless.

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...