Error Connecting with id #### (Tarkov DEV remote management ID)

[Shibalba]

If I close browser and PC goes to sleep this text appears when sleep ended in messages multiple times with the same timestamp

Error Connecting with id ####: The CancellationTokenSource has been disposed. at Websocket.Client.WebsocketClient.StartBackgroundThreadForSendingText() at Websocket.Client.WebsocketClient.StartInternal(Boolean failFast) at TarkovMonitor.SocketClient.Connect() in TarkovMonitor\SocketClient.cs:line 104

[Razzmatazzz]

I was only able to replicate this issue accidentally when my computer went idle overnight. Tarkov Monitor was acting like I wasn't connected to the internet. Some other apps had similar problems, but others could connect to the internet just fine. The issues were resolved by restarting my PC. I think this is an issue with Windows managing network connections when a PC idles/sleeps, and therefore not fixable.

[AmaniZandalari]

Got this error even after restarting my PC.

Error Connecting with id ####: The CancellationTokenSource has been disposed.
at Websocket.Client.WebsocketClient.StartBackgroundThreadForSendingText()
at Websocket.Client.WebsocketClient.StartInternal(Boolean failFast)
at TarkovMonitor.SocketClient.Connect() in TarkovMonitor\SocketClient.cs:line 103

[Jadaju]

I have the same problem, tried restarting PC as well as reinstalling TarkovMonitor.

[anatole1234]

Same thing here

[tarkovplayer]

please don't just comment "affects me" if you don't have any additional information to provide.
this is just notifying everyone subscribed to the issue without any benefit.
it's clear that this affects multiple users, which also includes me, and in the future i recommend just putting a reaction on the issue or in this case the first comment from today, to indicate that you're affected without having this notify everyone.

[Razzmatazzz]

The recent errors should be fixed now. There was a certificate issue on the backend that has been resolved.

[Jadaju]

The recent errors should be fixed now. There was a certificate issue on the backend that has been resolved.

Seems fixed, thanks a lot.

[Kenishi99]

I am getting this error again for some reason.