Connection breaks after some time

[myde2001]

Hi, when I forward a port using RoutePlus and MeshCentral 1.1.5, the connection breaks after some time.
The only way to "fix it" is restarting the MeshCentral server, restarting the client and login again in the MeshCentral WebUI after restart.
Also I activated debug in MeshCentral server but I can't find the routeplus log file.

Here is the log of MeshCentral:

may 14 16:45:08 REDACTED-TacticalRMM node[630]: HTTPHEADERS: GET /meshrelay.ashx/.websocket?auth=AkBet4tJKhfGjwFpFMuW4wESx3dNKe4B5c4G7$smZd1rtt516$xAZDn63j6Vqgm9EuRzktKEm4MdGhCfXDFGxotmo4vgrVs4sceMCn1crjMLCcsIWaYy&nodeid=node//pPv5vDPUix7M6RZA9CQ6Xt7NmcuuiMVmjC3TuRHOz9WhFDCECFBVVVXpaX05ymuY&tcpport=3389&tcpaddr=192.168.2.162 {
may 14 16:45:08 REDACTED-TacticalRMM node[630]:   host: 'mesh.redacted.net',
may 14 16:45:08 REDACTED-TacticalRMM node[630]:   upgrade: 'websocket',
may 14 16:45:08 REDACTED-TacticalRMM node[630]:   connection: 'upgrade',
may 14 16:45:08 REDACTED-TacticalRMM node[630]:   'x-forwarded-host': 'mesh.redacted.net:443',
may 14 16:45:08 REDACTED-TacticalRMM node[630]:   'x-forwarded-for': '192.168.1.1',
may 14 16:45:08 REDACTED-TacticalRMM node[630]:   'x-forwarded-proto': 'https',
may 14 16:45:08 REDACTED-TacticalRMM node[630]:   'content-length': '0',
may 14 16:45:08 REDACTED-TacticalRMM node[630]:   'sec-websocket-key': 'CN1qwfmCPr1IK8FK/iKtVP==',
may 14 16:45:08 REDACTED-TacticalRMM node[630]:   'sec-websocket-version': '13'
may 14 16:45:08 REDACTED-TacticalRMM node[630]: }
may 14 16:45:08 REDACTED-TacticalRMM node[630]: WEBREQUEST: (192.168.1.1) /meshrelay.ashx/.websocket?auth=AkBet4tJKhfGjwFpFMuW4wESx3dNKe4B5c4G7$smZd1rtt516$xAZDn63j6Vqgm9EuRzktKEm4MdGhCfXDFGxotmo4vgrVs4sceMCn1crjMLCcsIWaYy&nodeid=node//pPv5vDPUix7M6RZA9CQ6Xt7NmcuuiMVmjC3TuRHOz9WhFDCECFBVVVXpaX05ymuY&tcpport=3389&tcpaddr=192.168.2.162
may 14 16:45:08 REDACTED-TacticalRMM node[630]: COOKIE: ERR: Bad cookie due to timeout
may 14 16:45:08 REDACTED-TacticalRMM node[630]: RELAY: Relay: Soft disconnect (192.168.1.1)
may 14 16:45:10 REDACTED-TacticalRMM node[630]: DISPATCH: DispatchEvent [ '*' ]

[tecnicosya]

I have the same problem, the routes are not persistent. Work for maxium 1 day.

[myde2001]

I have the same problem, the routes are not persistent. Work for maxium 1 day.

I managed to fix it extending the cookie expiration time in the meshcentral code, however the routers doesn't survive if the target device reboots.

[mik000000]

hello could you please tell where we can modify cookie expiration time?

[ryanblenis]

Can anyone here confirm PR #22 fixes these issues for you as well? Thank you.

[redneck-f25]

There might be something else not related to ping-pong. Working on it.

[itadmsa]

Has anyone found a fix or workaround for this? I seem to be experiencing the same issue. Route works great with first used and is fine as long as the RDP sessions stays active.

After disconnect from RDP, route will continue to work for a while, but some time between 30 minutes and 2 hours it breaks.

I've disabled both ping and pong in config.json, but it had no effect.

So far, any time I use routeplus, if I take more than a 30 minute break I end up having to remove and recreate the route to get it back..

This is on a very fresh install of Meshcentral, only been up for a few days for testing. All base functions are working great, this routeplus issue is the only thing that has me stumped.

Thanks for the work on this amazing plugin.