quasimodem Posted June 12 Share Posted June 12 updated vortex, got this error multiple times. connect ETIMEDOUT 185.199.108.133:443 connect ETIMEDOUT 185.199.108.133:443 Error: connect ETIMEDOUT 185.199.108.133:443 at __node_internal_captureLargerStackTrace (node:internal/errors:496:5) at __node_internal_exceptionWithHostPort (node:internal/errors:671:12) at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) Prior Context: at Object.withTmpDir (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:9532:27) at E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:2726:180 at tryCatcher (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23) at Promise._settlePromiseFromHandler (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31) at Promise._settlePromise (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18) at Promise._settlePromiseCtx (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:641:10) at _drainQueueStep (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:97:12) at _drainQueue (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9) at Async._drainQueues (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5) at Async.drainQueues (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14) Prior Context: at Object.withTmpDir (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:9532:27) at E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:2726:180 at tryCatcher (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23) at Promise._settlePromiseFromHandler (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31) at Promise._settlePromise (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18) at Promise._settlePromiseCtx (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:641:10) at _drainQueueStep (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:97:12) at _drainQueue (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9) at Async._drainQueues (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5) at Async.drainQueues (E:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14) Link to comment Share on other sites More sharing options...
insomnious Posted June 12 Share Posted June 12 Sorry you are having problems. Looks like your system was struggling to connect to GitHub. Is this still happening after restarting Vortex? Regards, insomnious Link to comment Share on other sites More sharing options...
zeeth3 Posted June 15 Share Posted June 15 Hi there, I've been getting the same error for a few weeks- somthing to do with the relase of the CDPR mod tools? The error appears on startup. Restarting Vortex doesn't work, as the error returns. ---- connect ETIMEDOUT 185.199.108.133:443 connect ETIMEDOUT 185.199.108.133:443 Error: connect ETIMEDOUT 185.199.108.133:443 at __node_internal_captureLargerStackTrace (node:internal/errors:496:5) at __node_internal_exceptionWithHostPort (node:internal/errors:671:12) at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) Prior Context: at Object.withTmpDir (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:9532:27) at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:2726:180 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._settlePromiseCtx (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:641:10) at _drainQueueStep (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:97: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) Prior Context: at Object.withTmpDir (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:9532:27) at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:2726:180 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._settlePromiseCtx (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:641:10) at _drainQueueStep (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:97: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) ---- Vortex still works as usual for other games after dismissing the error notification but is there a way to stop it from checking for these resources if they aren't available? Witcher 3 is not managed and no mods from Nexus for it are installed V1.11.7 Link to comment Share on other sites More sharing options...
363rdChemicalCompany Posted June 16 Share Posted June 16 I have received the exact same error message a couple days ago, yet I do not (to my knowledge) own that game, nor do I know what github is or how to connect with it.. Odd. Link to comment Share on other sites More sharing options...
showler Posted June 16 Share Posted June 16 That particular extension is one of the bundled extensions that are considered part of Vortex. So you get it regardless of whether or not you have the game. It received a needed update the other day due to changes to the game. That's the reason why they are extensions, actually. So they can be updated without needing to update the entirety of Vortex. Github is a code repository used for open source projects where code can be worked on collaboratively. Since Vortex is open source it houses the newly updated code there and draws it's updates from there. The error is because your computer is having trouble connecting to Github. Might be worth turning on a free VPN and see if that fixes the problem. You would only need to have it active long enough for the extension to update. Strange how many ISPs seem to interfere with Github, though. It's really well-known and respected site. Link to comment Share on other sites More sharing options...
Solution zeeth3 Posted June 24 Solution Share Posted June 24 It appears to be my VPN (always on) that was causing the issue. Disabling it allowed the Witcher 3 extension to update. Guess my VPN provider considers github a risk? 1 Link to comment Share on other sites More sharing options...
Pickysaurus Posted June 24 Share Posted June 24 Thanks for coming back with your solution - you should check with your VPN provider as to why they block this. Link to comment Share on other sites More sharing options...
downtone Posted August 17 Share Posted August 17 @Picksaurus, I'd guess it's the other way around. Github's provider blocking the vpn. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now