Thanks for looking, and indeed signal still works fine on my desktop computers with the VPN running.
Really feels like their tech support was lying. I do just enough of this that the recommendation makes my eyes glaze over while sounding transparently wrong. Suddenly I need open UDP and TCP ports, but only on my phone (computer is fine) and only as of a few weeks ago (prior to that it was fine)? What?
Allow *.whispersystems.org, *.signal.org, updates.signal.org, TCP port 443, and UDP traffic. If you have a transparent or reverse proxy it needs to support WebSockets. Signal uses a non-standard TCP port to catch filtering issues at the signaling step and also utilizes a random UDP port. All UDP ports will need to be opened. The underlying IPs are constantly changing, so it'd be hard to define accurate firewall rules.
If the wildcard FQDN config is not working properly and you notice issues with calling, allow turn2.voip.signal.org, turn3.voip.signal.org and sfu.voip.signal.org. These are subject to change at anytime.
File Recovery and Data Recovery (com.spot.music.filedate) with over 1 million installs, and File Manager (com.file.box.master.gkd) with over 500,000 installs>
Not foregoing per say, but I have found indications that insurance companies are becoming very strict (smart?) in the questions and assessments of business they provide insurance to.
Infosec
Hot