I ran into an issue trying to set up SpeedFusion in a secured environment managed by an external IT provider. The necessary firewall rules were applied (TCP 32015, UDP 4550), but SpeedFusion wouldn’t establish a connection due to the WAN health check failing DNS. Since we intended to route all traffic over the VPN, DNS access wasn’t requested.
I expected SpeedFusion to attempt connection despite the failed health check, but it didn’t. Remote access was impossible until we locally changed the health check to Ping, after which the VPN worked.
Has anyone else faced this issue where SpeedFusion doesn’t attempt to connect when the DNS health check fails? Is the only option to switch the health check to Ping?
WAN status on the dashboard wins always. Its how you control all traffic flow over your WANs, so you need to choose the most appropriate health check for your environment (or disable health checks if you only have a single WAN).