Jump to content

fxhome

Supporter
 View Profile  See their activity

  • Posts

    5

  • Joined

  • Last visited

Nexus Mods Profile

About fxhome

Profile Fields

  • Country
    None

fxhome's Achievements

Rookie

Rookie (2/14)

2

Reputation

  1. fxhome
    Hey, I got an issue with the Vortex Client behind SSL Proxy. I already excluded decryption for Nexusmods and can login and download stuff via Vortex. But as of today, I cannot download big files (like the one in the picture). It was possible before and there were no changes from my end, small files are also possible to download, but if I try a bigger file, Vortex starts giving me the error. I'm using the newest Vortex Client 1.10.8 I already logged out of the client and installed the same version on top. Any help is appreciated. EDIT: Is it possible to see the chain Vortex is referring to somewhere?
  2. fxhome
    Thanks for the fix
  3. fxhome
    I also forward this! 1780 Mods installed for Skyrim:AE. No issues before the 1.10.6 Vortex client update. Vortex telling me some mods are redundant after the forced purge and rollout. They are most definetly not redundant nor are they overwritten by another mod. Was this update release without proper testing? EDIT: Changing rules also wont change a thing concerning the false positive on redundant mods. Also there is this annoing auto purge, everytime I do a rule change.
  4. fxhome
    It's now working again, guess it was a server issue on their end.
  5. fxhome
    Hey, I cannot login to Vortex. When I allow it via browser, it shows: "Authorisation successful! Vortex is now authenticated with your Nexus Mods account. Click below to log in to Vortex." But I cannot login and get this error message in the Vortex client: Error: Failed to parse failure response: "<!DOCTYPE html><html lang="en-US"><head><title>Jus" at IncomingMessage.<anonymous> (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:6847:101) at IncomingMessage.emit (node:events:525:35) at endReadableNT (node:internal/streams/readable:1359:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) - Vortex is up to date - Already restarted PC - Restarted Vortex App - New login in Browser - I use 2FA When I start Vortex, I get this error: https://ibb.co/4KNzC57 Edit: Token Login also won't work, it shows "Failed to get access key" with the same error message from above.
×
×
  • Create New...