Hey all...So I am testing a failover WAN with VPN connectivity to my remote site. Everything works "except" some connectivity to PBS for sync jobs and monitoring API calls. Oddly I see the same on PVE but there is more information on teh PBS side.
When the WAN failed over, the VPN's came up as expected. I can ping PBS, I can get the web UI port 8007, log in etc. All that is verifyable.
What is strange is a sync job fails with just this message:
and a monitoring job has this which appears to be more information
Between the two I cannot tell what would be different after WAN failover when all the VPN routes remain the same before and after. The fact I can access the remote side on all aspects to manage it also has me puzzled. The second one seems to indicate the connection is just being killed out of the gate, but the source IP of the local PBS is unchanged after WAN failover and the traffic inside the site to site VPN should be the same regardless of the WAN making the remote connection.
this is the only issue after WAN failover I need to sort out but I am really puzzled...
Both local and remote are on PBS 4.1.6 as well and I also rebooted them both for good measure.
When the WAN failed over, the VPN's came up as expected. I can ping PBS, I can get the web UI port 8007, log in etc. All that is verifyable.
What is strange is a sync job fails with just this message:
Code:
2026-04-09T08:27:44-04:00: Starting datastore sync job 'PBS-VA:LOCAL:QNAP::s-ad005baa-b7be'
2026-04-09T08:27:44-04:00: sync datastore 'QNAP' to 'PBS-VA/LOCAL'
2026-04-09T08:27:54-04:00: queued notification (id=5640f5a5-ea83-4d9b-a57f-3fb0ac185293)
2026-04-09T08:27:54-04:00: TASK ERROR: client error (Connect)
and a monitoring job has this which appears to be more information
Code:
API Error: Client network socket disconnected before secure TLS connection was established
URL: https://172.16.100.4:8007/api2/json/nodes/localhost/tasks?errors=true&limit=100&since=1774445616707
Raw Error:
{
"code": "ECONNRESET",
"path": null,
"host": "172.16.100.4",
"port": 8007
}
Between the two I cannot tell what would be different after WAN failover when all the VPN routes remain the same before and after. The fact I can access the remote side on all aspects to manage it also has me puzzled. The second one seems to indicate the connection is just being killed out of the gate, but the source IP of the local PBS is unchanged after WAN failover and the traffic inside the site to site VPN should be the same regardless of the WAN making the remote connection.
this is the only issue after WAN failover I need to sort out but I am really puzzled...
Both local and remote are on PBS 4.1.6 as well and I also rebooted them both for good measure.
Last edited: