You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was having a persistent issue where sometimes the hqpwv command prompt window would just close after I tried to open it, with no error or explanation. I figured out that the issue was hqpwv being blocked by Windows Defender firewall, one of my home networks was set as a "public network" and hqpwv wasn't whitelisted in the firewall settings. I'm not sure if you have any control over this, but if hqpwv's network connection is blocked, could it be made to stay open and give an error message, rather than just closing instantly? It would have been much faster to diagnose the issue if I got an error like "UDP socket blocked" or "network timeout" or something.
I'm on Win10 LTSC.
Steps to reproduce:
Enable Windows Defender Firewall.
Set your current network to "Public", so that network connections for many apps are blocked by default.
Don't add the hqpwv server to the firewall's whitelist.
Run hqpwv server.
Result: The hqpwv server CMD window opens for a moment, gets as far as "creating udp socket; udp socket listening on 0.0.0.0:58080; waiting for response from HQPlayer...", then a moment later, the CMD window closes. No error message, and there's no log file that I have found.
The text was updated successfully, but these errors were encountered:
I was having a persistent issue where sometimes the hqpwv command prompt window would just close after I tried to open it, with no error or explanation. I figured out that the issue was hqpwv being blocked by Windows Defender firewall, one of my home networks was set as a "public network" and hqpwv wasn't whitelisted in the firewall settings. I'm not sure if you have any control over this, but if hqpwv's network connection is blocked, could it be made to stay open and give an error message, rather than just closing instantly? It would have been much faster to diagnose the issue if I got an error like "UDP socket blocked" or "network timeout" or something.
I'm on Win10 LTSC.
Steps to reproduce:
Result: The hqpwv server CMD window opens for a moment, gets as far as "creating udp socket; udp socket listening on 0.0.0.0:58080; waiting for response from HQPlayer...", then a moment later, the CMD window closes. No error message, and there's no log file that I have found.
The text was updated successfully, but these errors were encountered: