# Problem with Private Relay Server

**URL:** https://forum.syncthing.net/t/problem-with-private-relay-server/16759
**Category:** Support
**Created:** [May 4, 2021, 2:50pm UTC](https://forum.syncthing.net/t/problem-with-private-relay-server/16759 "2021-05-04T14:50:11Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![AudriusButkevicius](https://forum.syncthing.net/user_avatar/forum.syncthing.net/audriusbutkevicius/32/277_2.png) [@AudriusButkevicius](https://forum.syncthing.net/u/AudriusButkevicius)
#### Post date: [May 5, 2021, 7:20pm UTC](https://forum.syncthing.net/t/problem-with-private-relay-server/16759/5 "2021-05-05T19:20:34Z")

</div>

So no smoking gun.

Seems like the connection between relay and B just dies.

Maybe your tcp stack has very short keep alives/statefull firewall with a short timeout?

I guess you could set `-ping-interval=10s` on the relay and see if that helps, this will make sure there are some messages exchanged between the two every 10 seconds.

It’s a bit sad that a connection to the relay for the purposes of accepting new connections breaking, breaks existing connections, but I guess that’s just how the current architecture works, and it would be non-trivial to do something else.

Also, I guess it sort of makes sense, as it helps recover from cases where the relay genuinely disappeared, allowing quicker detection of dead connections.

---

_[View the full topic](https://forum.syncthing.net/t/problem-with-private-relay-server/16759)._