Failed to log-in, network disconnected (1.6.10)

[GlitteringIgnition]

Doing due diligence--error is persisting in 1.6.12

[rmm200]

!.6.12 is working fine here.

Sure wish we could help narrow down the differences.

[Tannin42]

This error (network offline) message doesn't mean Vortex failed to reach some server or something which might be a network/server issue.

It means that, according to the backend (chrome), you have no internet connection. As in: the network adapter is disabled or no network cable connected or the local network is not connected to the internet.

In this case Vortex doesn't even try to connect to servers because the expectation is that that would only cause timeouts and error messages.

 

Vortex has no reason to doubt what the backend is telling us, the way it's documented it should never produce a false negative, I quote:

  Quote

So while you can assume that the browser is offline when it returns a false value, you cannot assume that a true value necessarily means that the browser can access the internet.

 

 

If you create a ticket through the Vortex feedback system I may be able to build in a "Workaround" that would let you ignore the offline status and try connecting anyway but I _suspect_ it's your Windows or Firewall refusing Vortex access to the network so nothing Vortex does on its end would help.

[GlitteringIgnition]

  On 9/30/2022 at 9:21 AM, Tannin42 said:

This error (network offline) message doesn't mean Vortex failed to reach some server or something which might be a network/server issue.

It means that, according to the backend (chrome), you have no internet connection. As in: the network adapter is disabled or no network cable connected or the local network is not connected to the internet.

In this case Vortex doesn't even try to connect to servers because the expectation is that that would only cause timeouts and error messages.

 

Vortex has no reason to doubt what the backend is telling us, the way it's documented it should never produce a false negative, I quote:

  Quote

So while you can assume that the browser is offline when it returns a false value, you cannot assume that a true value necessarily means that the browser can access the internet.

 

If you create a ticket through the Vortex feedback system I may be able to build in a "Workaround" that would let you ignore the offline status and try connecting anyway but I _suspect_ it's your Windows or Firewall refusing Vortex access to the network so nothing Vortex does on its end would help.

By all accounts it seems like that kind of problem, yes, but if that's the case the normal fixes (bypassing firewall/other network securities, trying different wi-fi networks in case of built-in blockages) are not working. Thank you for the feedback suggestionI'll try that next.

[GlitteringIgnition]

Hmm tried to send the feedback through Vortex per request--predictably I received a very similar error message (network disconnected: sendFeedback) but with much more comprehensive details. I do not have the knowledge to understand it but pasting below for the sake of spreading information.

 

Error
at Disableable.get (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:6181:203)
at Proxy.<anonymous> (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:6187:242)
at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:6611:56
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)

Called from:

at null (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:6188:37)
at null (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:6611:56)
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)

[iMitchy]

  On 9/30/2022 at 9:21 AM, Tannin42 said:

This error (network offline) message doesn't mean Vortex failed to reach some server or something which might be a network/server issue.

It means that, according to the backend (chrome), you have no internet connection. As in: the network adapter is disabled or no network cable connected or the local network is not connected to the internet.

In this case Vortex doesn't even try to connect to servers because the expectation is that that would only cause timeouts and error messages.

 

Vortex has no reason to doubt what the backend is telling us, the way it's documented it should never produce a false negative, I quote:

  Quote

So while you can assume that the browser is offline when it returns a false value, you cannot assume that a true value necessarily means that the browser can access the internet.

 

 

If you create a ticket through the Vortex feedback system I may be able to build in a "Workaround" that would let you ignore the offline status and try connecting anyway but I _suspect_ it's your Windows or Firewall refusing Vortex access to the network so nothing Vortex does on its end would help.

I have gone as far to remove my AV (Kasperky) and disabled Windows Firewall with the same issue reproduced. I only have one network adapter currently enabled as it's the only one that will be able to connect to the internet, the others are ethernet which does not have anything plugged into it.

 

I haven't been able to find a ticket page, if you could provide a link please? As the one in the app cannot be used.

 

Thanks for your time.

[GlitteringIgnition]

  On 9/30/2022 at 3:14 PM, iMitchy said:

 

  On 9/30/2022 at 9:21 AM, Tannin42 said:

This error (network offline) message doesn't mean Vortex failed to reach some server or something which might be a network/server issue.

It means that, according to the backend (chrome), you have no internet connection. As in: the network adapter is disabled or no network cable connected or the local network is not connected to the internet.

In this case Vortex doesn't even try to connect to servers because the expectation is that that would only cause timeouts and error messages.

 

Vortex has no reason to doubt what the backend is telling us, the way it's documented it should never produce a false negative, I quote:

  Quote

So while you can assume that the browser is offline when it returns a false value, you cannot assume that a true value necessarily means that the browser can access the internet.

 

 

If you create a ticket through the Vortex feedback system I may be able to build in a "Workaround" that would let you ignore the offline status and try connecting anyway but I _suspect_ it's your Windows or Firewall refusing Vortex access to the network so nothing Vortex does on its end would help.

I have gone as far to remove my AV (Kasperky) and disabled Windows Firewall with the same issue reproduced. I only have one network adapter currently enabled as it's the only one that will be able to connect to the internet, the others are ethernet which does not have anything plugged into it.

 

I haven't been able to find a ticket page, if you could provide a link please? As the one in the app cannot be used.

 

Thanks for your time.

 

 

Discovered another potential common thread--the response from Tannin inspired me to start rooting around through other device security and noticed something odd. Poking around in the settings for windows security brought me to realize I've been getting an error installing a windows update to fix the "App and Browser Control" section. If you've been getting a similar problem with your update that could be a potential reason for Vortex getting blocked

 

[iMitchy]

  On 9/30/2022 at 5:33 PM, GlitteringIgnition said:

 

  On 9/30/2022 at 3:14 PM, iMitchy said:

 

  On 9/30/2022 at 9:21 AM, Tannin42 said:

This error (network offline) message doesn't mean Vortex failed to reach some server or something which might be a network/server issue.

It means that, according to the backend (chrome), you have no internet connection. As in: the network adapter is disabled or no network cable connected or the local network is not connected to the internet.

In this case Vortex doesn't even try to connect to servers because the expectation is that that would only cause timeouts and error messages.

 

Vortex has no reason to doubt what the backend is telling us, the way it's documented it should never produce a false negative, I quote:

  Quote

So while you can assume that the browser is offline when it returns a false value, you cannot assume that a true value necessarily means that the browser can access the internet.

 

 

If you create a ticket through the Vortex feedback system I may be able to build in a "Workaround" that would let you ignore the offline status and try connecting anyway but I _suspect_ it's your Windows or Firewall refusing Vortex access to the network so nothing Vortex does on its end would help.

I have gone as far to remove my AV (Kasperky) and disabled Windows Firewall with the same issue reproduced. I only have one network adapter currently enabled as it's the only one that will be able to connect to the internet, the others are ethernet which does not have anything plugged into it.

 

I haven't been able to find a ticket page, if you could provide a link please? As the one in the app cannot be used.

 

Thanks for your time.

 

 

Discovered another potential common thread--the response from Tannin inspired me to start rooting around through other device security and noticed something odd. Poking around in the settings for windows security brought me to realize I've been getting an error installing a windows update to fix the "App and Browser Control" section. If you've been getting a similar problem with your update that could be a potential reason for Vortex getting blocked

 

 

 

Considering Vortex uses Chrome as it's backend, unfortunately I doubt this will have any effect.

[iMitchy]

Hi all, I have some good news. Finally found a fix for myself, I disabled UPnP in my router settings, then it instantly logged in!

[GlitteringIgnition]

That's great news! I only wish I wasn't getting it in the middle of my shift lol. I'll be back on in about 6 hours or so to see if it works on my end.