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.
I saw the writing on the wall a few years back, it was so painfully obvious. I started switching to KiCAD early, and feel so bad for ever recommending Eagle to people who will now have to learn yet another new tool in order to find something usable.
Fusion360 is so bad, I had to explain why SolidWorks was different earlier today and they were shocked by things like “if I move the case the board I say is attached to the case moves to” and “I don’t have to align it by eye, it’s a computer”.
And I’m definitely not starting VMWare to run Fusion360 with nonsense online components that slow it down to uselessness and integrate it into a tool that doesn’t need to be on at all… it’s just not possible. It was obvious once they stopped updating the version. It’s pathetic nonetheless that they cannot think beyond the one-true-way of integrating a dozen mediocre tools into one extra-mediocre product.