-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled runtime exception: ConnectionResetError #146
Comments
Hey @Quinten0508 I hope you are having a good day! The issue no longer happens when turning off Google One VPN; If you are using a VPN, try turning it off before launching LIFX Control Panel. Hope this helps shine some light on what might be the cause for anyone who knows how to fix this VPN incompatibility issue. |
Sorry for the late reply! Just got back home and confirmed that my VPN is turned off and the issue persists. I've also tried adding firewall rules (both in- and outbound) but without success. |
Nevermind, I had Tailscale enabled in the background. Disabling that fixed the connection issue :D |
I'm also getting this error, with no VPN running. |
Actually, I take that back. The symptoms appear the same, but the specific error I see is different. I will open a separate issue. |
Describe the bug
The application does not launch successfully, instead showing the following error message:
To Reproduce
Steps to reproduce the behavior:
lifx_control_panel.exe
from releaseExpected behavior
I'd expect the application to simply launch/open, but it errors out. When
ok
is pressed, both the error window and the purple splashscreen close. Running the executable with administrator rights does not do anything.Screenshots
error window:
error window and purple splashscreen(?) side-by-side. The error dialog can be dragged, the splashscreen cannot be moved.
Desktop (please complete the following information):
Please attach your logfile (lifx-control-panel.log)
No logfile is generated, nor is there any console output when ran through a terminal (powershell/command prompt). Running the debug build outputs the following (behaviour stays exactly the same):
Additional context
Running the same executable in Windows Sandbox (essentially a virtual machine) does not give this error. The application seems to work fine, albeit that it can't find any lights, but that is most likely related to how the VM is set up (no local network discovery).
The text was updated successfully, but these errors were encountered: