This issue respects the following points:
Description of the bug
The debugger fails with error "The proxy port must be an integer", after that the actual config stays on 'running' mode and console logs the following information:
"The debugger status is not idle, so it cannot be started"
"Failed to invoke hub method 'start'"
Not possible to continue using the config until restarting the console or deleting the config
Reproduction steps
- Click on config stacker
- Write any non-integer proxy: "http://test:8000:user:pass | quotation marks on the proxy to reproduce the issue
- Debugger stops working, even after refreshing the web-view / website. Isn't possible to stop it at all since "The debugger status is not idle, so it cannot be started"
What is the current bug behavior?
Unable to keep using the config at all due the debugger issue
What is the expected correct behavior?
Just a simple error display, but it ends on the debugger error / console error
Version of the client
v0.3.2 [beta]
Type of client
Web client
Environment
- OS: Windows 11 Pro, version 24H2 | OS build: 26100.4061
- Virtualization: None
- Browser: Vivaldi Desktop. Stable - 7.4 (3684.38) Snapshot - 3684.34.
OpenBullet2 logs
{"@t":"2025-05-21T20:38:46.8276088Z","@mt":"Failed to invoke hub method '{HubMethod}'.","@l":"Error","@x":"The debugger status is not idle, so it cannot be started","@tr":"89f13e11b2a060654adbfceb9d4593ab","@sp":"40380d8b13f89b28","HubMethod":"start","EventId":{"Id":8,"Name":"FailedInvokingHubMethod"},"SourceContext":"Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher","TransportConnectionId":"OiMm7RJGoJ6TqgwUyHx5RQ","RequestId":"0HNCOKK2AOE3G:00000001","RequestPath":"/hubs/config-debugger","ConnectionId":"0HNCOKK2AOE3G","ExceptionDetail":{"HResult":-2146233088,"Message":"The debugger status is not idle, so it cannot be started","Source":"OpenBullet2.Web","TargetSite":"RuriLib.Models.Debugger.ConfigDebugger CreateNew(System.String, RuriLib.Models.Debugger.DebuggerOptions)","ErrorCode":"CONFIG_DEBUGGER_NOT_IDLE","Type":"OpenBullet2.Web.Exceptions.ApiException"},"ApplicationName":"OpenBullet2"}
{"@t":"2025-05-21T20:38:47.7008740Z","@mt":"Failed to invoke hub method '{HubMethod}'.","@l":"Error","@x":"The debugger status is not idle, so it cannot be started","@tr":"89f13e11b2a060654adbfceb9d4593ab","@sp":"40380d8b13f89b28","HubMethod":"start","EventId":{"Id":8,"Name":"FailedInvokingHubMethod"},"SourceContext":"Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher","TransportConnectionId":"OiMm7RJGoJ6TqgwUyHx5RQ","RequestId":"0HNCOKK2AOE3G:00000001","RequestPath":"/hubs/config-debugger","ConnectionId":"0HNCOKK2AOE3G","ExceptionDetail":{"HResult":-2146233088,"Message":"The debugger status is not idle, so it cannot be started","Source":"OpenBullet2.Web","TargetSite":"RuriLib.Models.Debugger.ConfigDebugger CreateNew(System.String, RuriLib.Models.Debugger.DebuggerOptions)","ErrorCode":"CONFIG_DEBUGGER_NOT_IDLE","Type":"OpenBullet2.Web.Exceptions.ApiException"},"ApplicationName":"OpenBullet2"}
Client / Browser logs
No response
Relevant screenshots or videos

Relevant LoliCode if needed
Additional information
No response
This issue respects the following points:
Description of the bug
The debugger fails with error "The proxy port must be an integer", after that the actual config stays on 'running' mode and console logs the following information:
"The debugger status is not idle, so it cannot be started"
"Failed to invoke hub method 'start'"
Not possible to continue using the config until restarting the console or deleting the config
Reproduction steps
What is the current bug behavior?
Unable to keep using the config at all due the debugger issue
What is the expected correct behavior?
Just a simple error display, but it ends on the debugger error / console error
Version of the client
v0.3.2 [beta]
Type of client
Web client
Environment
OpenBullet2 logs
{"@t":"2025-05-21T20:38:46.8276088Z","@mt":"Failed to invoke hub method '{HubMethod}'.","@l":"Error","@x":"The debugger status is not idle, so it cannot be started","@tr":"89f13e11b2a060654adbfceb9d4593ab","@sp":"40380d8b13f89b28","HubMethod":"start","EventId":{"Id":8,"Name":"FailedInvokingHubMethod"},"SourceContext":"Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher","TransportConnectionId":"OiMm7RJGoJ6TqgwUyHx5RQ","RequestId":"0HNCOKK2AOE3G:00000001","RequestPath":"/hubs/config-debugger","ConnectionId":"0HNCOKK2AOE3G","ExceptionDetail":{"HResult":-2146233088,"Message":"The debugger status is not idle, so it cannot be started","Source":"OpenBullet2.Web","TargetSite":"RuriLib.Models.Debugger.ConfigDebugger CreateNew(System.String, RuriLib.Models.Debugger.DebuggerOptions)","ErrorCode":"CONFIG_DEBUGGER_NOT_IDLE","Type":"OpenBullet2.Web.Exceptions.ApiException"},"ApplicationName":"OpenBullet2"} {"@t":"2025-05-21T20:38:47.7008740Z","@mt":"Failed to invoke hub method '{HubMethod}'.","@l":"Error","@x":"The debugger status is not idle, so it cannot be started","@tr":"89f13e11b2a060654adbfceb9d4593ab","@sp":"40380d8b13f89b28","HubMethod":"start","EventId":{"Id":8,"Name":"FailedInvokingHubMethod"},"SourceContext":"Microsoft.AspNetCore.SignalR.Internal.DefaultHubDispatcher","TransportConnectionId":"OiMm7RJGoJ6TqgwUyHx5RQ","RequestId":"0HNCOKK2AOE3G:00000001","RequestPath":"/hubs/config-debugger","ConnectionId":"0HNCOKK2AOE3G","ExceptionDetail":{"HResult":-2146233088,"Message":"The debugger status is not idle, so it cannot be started","Source":"OpenBullet2.Web","TargetSite":"RuriLib.Models.Debugger.ConfigDebugger CreateNew(System.String, RuriLib.Models.Debugger.DebuggerOptions)","ErrorCode":"CONFIG_DEBUGGER_NOT_IDLE","Type":"OpenBullet2.Web.Exceptions.ApiException"},"ApplicationName":"OpenBullet2"}Client / Browser logs
No response
Relevant screenshots or videos
Relevant LoliCode if needed
Additional information
No response