Matching service start/stop loop in production deployment

Thanks for the quick turnaround! It looks like the issue was caused because my temporal-server peers could reach each other. I was able to resolve it by setting the broadcast address to each host’s public ip and then binding on 0.0.0.0. I also opened up additional ports for peer-to-peer communication.

I found some useful info deep in the support tickets, linking here for others: