Vortex: "failed with status 500"

[Pickysaurus]

I'm afraid there hasn't been capacity in our dev team to look into this yet. I know it's frustrating.

[dcdoc]

What solution do you propose in the meantime? As we have been not able to use the service as intended for a long period of time.

 

I proposed the option to get temporary premium accounts as a solution until the issue is resolve. I sadly did not get any response from your side

 

P.S: As of today still broken

[Pickysaurus]

Is this impacting your ability to use any of the site features or is it just an annoying message each time you start Vortex?

 

Does Vortex still check for updates or is the entire process aborted?

 

Edit: On reviewing the source code, it appears that if the endorsement refresh fails, so does the update check: https://github.com/Nexus-Mods/Vortex/blob/838a073fa0a326eb4877ca721b0c9cf3b69d61e0/src/extensions/nexus_integration/util.ts#L1175

[Arikdefrasia]

  On 3/8/2023 at 4:45 PM, Pickysaurus said:

Does Vortex still check for updates or is the entire process aborted?

 

Edit: On reviewing the source code, it appears that if the endorsement refresh fails, so does the update check: https://github.com/Nexus-Mods/Vortex/blob/838a073fa0a326eb4877ca721b0c9cf3b69d61e0/src/extensions/nexus_integration/util.ts#L1175

Personally, I'm still able to download mods and enable them, but vortex returns that 500 error if I ask it to check if any mods have updates.

 

"it appears that if the endorsement refresh fails, so does the update check"

Is that a good thing / bad thing / means nothing in terms of finding out why this is happening?

[Pickysaurus]

It's not great, it means that the mods aren't actually checked for updates if the endorsement check errors.

 

This either needs to be fixed on your account or a workaround added to Vortex.

[Pickysaurus]

Can you please try again now?

 

One of our devs took a look at it today and we believe it's fixed.

 

The problem was that your account had endorsed a mod from 2015 which was fully deleted from the database. This wasn't something that was accounted for when generating your endorsement list.

[Arikdefrasia]

  On 3/16/2023 at 10:29 AM, Pickysaurus said:

Can you please try again now?

 

One of our devs took a look at it today and we believe it's fixed.

 

The problem was that your account had endorsed a mod from 2015 which was fully deleted from the database. This wasn't something that was accounted for when generating your endorsement list.

The 500 error is now replaced with this:

TypeError: Cannot read properties of null (reading 'toLowerCase')
    at convertGameIdReverse (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:6775:118)
    at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:6639:113
    at Array.reduce (<anonymous>)
    at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:6639:31
    at tryCatcher (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:729:18)
    at _drainQueueStep (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:93:12)
    at _drainQueue (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9)
    at Async._drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5)
    at Async.drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)

 

[Pickysaurus]

This is no longer an account problem (thankfully) but I have no idea how you're getting that error.

 

Try managing a game other than Skyrim SE, New Vegas or ESO and then swap back?

[Arikdefrasia]

  On 3/17/2023 at 9:10 AM, Pickysaurus said:

Try managing a game other than Skyrim SE, New Vegas or ESO and then swap back?

The error happened with Doom (2016) and Bloodstained ritual of the night and Kingdom Come: Deliverance. So not working regardless of the game.

 

Edit: Did a repair install of the .net runtime just to be safe and repaired/updated vortex to the latest version and still get the error.

 

Edit: Log out/in didn't fix it either.

 

Edit: Something changed.....hang on.

[Pickysaurus]

Ok, so it seems you had an endorsement without a game ID which was throwing Vortex off.

 

I've had the devs remove this bad data, so in theory it should work again.

 

We'll also review the data for other long-term members who may have a similar issue with their endorsements.