Hi tux84, Viscosity 1.11 provides a new compatibility setting that will allow it to connect to servers running legacy versions of OpenVPN. Please run through the steps listed in the following article, which should get you connecting again: https://www.sparklabs.com/support/kb/article/migrating-from-...

Hi buh,

Please run through the steps listed in the following article:
https://www.sparklabs.com/support/kb/ar ... envpn-2-6/

Cheers,
James

Hi patrikr, You can convert them to OpenVPN syntax, and then add them to the advanced commands area for your connection. For example, the first IP range ("3.7.35.0/25") in the txt file would become: route 3.7.35.0 255.255.255.128 net_gateway The second IP range ("3.21.137.128/25"...

Hi andy_p, Frustratingly this is a limitation that Apple introduced a number of macOS updates ago: WebAuthn requests are now blocked in web views. WebAuthn is the browser API used to communicate with FIDO authentication keys. At the time we heard that Apple was working on a solution to re-allow WebA...

Hi floatingpurr, It's difficult to tell without the full connection log, however as a guess it sounds like the VPN server isn't setting any DNS servers, or setting an invalid one. With Full DNS mode, this means that when you connect your computer won't have any DNS servers set. If this is the case, ...

Hi klausus, You'll want to use Full DNS Mode, rather than Split DNS Mode, to ensure that DNS lookups by default use your VPN DNS servers. To exclude your local domain from using the VPN DNS servers, you can make use of macOS's "/etc/resolver/" feature. This allows you to specify to macOS t...

Hi Benny, It appears you have a TUN (routed) connection. These are known as point-to-point network interfaces, as they send traffic directly to the other endpoint (the OpenVPN server's internal IP) rather than a more typical broadcast network interface. Point-to-point interfaces use a different ifco...

Hi LSH246, Well ultimately it's likely to be one of three things: 1. A DNS issue. It could be that for some reason you're able to resolve some DNS names,, but not others. Run though the troubleshooting steps in the following article and test a variety of domains you have trouble accessing: https://w...

Rest assured the route is supposed to be there, and helps enable things like PMTUD and service discovery. I understand that if you're not familiar with routing flags and interface scoping you might think it's an unwanted normal "default" route, but this isn't the case.

Cheers,
James

Hi JounQin, The "default 10.80.0.169 UGScIg utun10" route is normal and expected. Please observe the “I” flag listed for the route. This indicates it is an "interface scoped" route, and does not apply globally to the system. It will not cause traffic outside of your VPN routes to...