0neGal / viper

Launcher+Updater for TF|2 Northstar
https://0negal.github.io/viper
GNU General Public License v3.0
151 stars 21 forks source link

bug: User unable to install mod due to connection issue despite being able to connect in browser #244

Open GeckoEidechse opened 1 month ago

GeckoEidechse commented 1 month ago

Describe the bug Bug report made from a ticket on Discord.

Describe your issue for us. When I try downloading Mods i get an error message. Have you read the Wiki and announcements? Yes What OS? What Installer (Viper/VTOL/R2MM)? Windows 11, Viper v1.26.4 Are you trying to host a server? no What have you tried so far? Reinstalling Viper, deleting everything then reinstalling. image

image

To Reproduce Steps to reproduce the behavior: ???

Expected behavior Installing a mod should just work assuming internet connection.

Screenshots

image

image

Version: ???

Additional Info Made by me as proxy for a ticket on Northstar Discord. Link for anyone with access to tickets: https://discord.com/channels/920776187884732556/1267446113569603699/1267446122914254901

0neGal commented 1 month ago

That's a strange bug, might be related to an application specific firewall, VPN or similar, though, I'm not sure I can actually look into this without being able to reproduce it in any way... Mostly because this isn't entirely in Viper's control, best Viper can do in this situation is show a better error message :/

I will keep this open in case it's an actual issue and not just a network misconfiguration of some kind.

GeckoEidechse commented 1 month ago

Yeah pretty sure Viper is blocked from internet access in this case

image

So way to go would be to have a connection check (ping cloudflare, google, ) and show user friendly error message accordingly.

GeckoEidechse commented 1 month ago

Definitely something blocking network connection for some applications

image

0neGal commented 1 month ago

So way to go would be to have a connection check (ping cloudflare, google, ) and show user friendly error message accordingly.

We actually do have a check for navigator.onLine albeit, it isn't always accurate, I do however realize now, it is only ever checked on startup. I'll look into making it check more frequently, and doing extra checks to remedy/help with this...