Hi gabin8207, This is something that you'll need to handle on the OpenVPN server - it isn't something that you need to configure client side in Viscosity. On the server you have a few options: 1. A simple approach is to have multiple OpenVPN server instances (for example, running on different port ...

That's good to hear - thanks for letting us know.

Cheers,
James

However, for some reason there are two copies of the connection that show up. Both are identical, and both seem to work, so not a deal breaker, but still I'm unsure why. In the template you provided us via email your connection was stored in the "Connections-Append" directory, which means every ...

Just a heads up that we've released an updated beta version (1.11.4b2) that should improve performance on macOS 15.0.1+. Please give it a try and let us know if you still encounter any poor TAP performance or issues. https://www.sparklabs.com/support/kb/article/using-viscosity-beta-versions/ Cheers ...

Just a heads up that we've released an updated beta version (1.11.4b2) that should improve performance on macOS 15.0.1+. Please give it a try and let us know if you still encounter any poor TAP performance or issues. https://www.sparklabs.com/support/kb/article/using-viscosity-beta-versions/ Cheers ...

I do have one question for you on the script for the notarytool. Part of the code calls for myApplePassword. Is this our AppleID password, our Viscosity App Specific Password, or the password of the root/admin user on the machine we're running the script on? It should be the app specific password ...

Hi mlove, Thanks for the report. We're aware of this one, and actively working on it. It only affects TAP (bridged) connections on macOS 15.0.1 and 15.1, TUN (routed) connections are not affected, nor are earlier versions of macOS. It's related to Apple blocking access to the APIs necessary for ...

Never mind. If I distribute the package through my MDM the signed package works just fine and doesn't need to be notarized. Glad to hear you found a solution. Just in case anyone else comes across this forum post with the same issue, the most recent version of Xcode requires "notarytool" be used ...

Hi rouet, Thanks for the report. I can confirm we're seeing the same behaviour in macOS 15.0.1 (and 15.1 RC). Earlier versions of macOS are not affected (which are likely what your colleagues are using). Rather than a simple bug or framework change, it appears Apple have suddenly blocked access to ...

Either Login or System should be fine.

Cheers,
James