Thanks. It’s a server running inside an Orbi router. I don’t know if I can disable anything. I have set the rest of my AppleTVs to not update the app but 2 already have 😭

https://community.netgear.com/discussions/Orbi/openvpn-server-config-problems---compression-and-authorization-on-rbr40/1972000

I'm searching the web, and it seems that Netgear enforces compression at the firmware level, which is really a shame. Unfortunately, there are several reasons why I couldn't keep compression support in the app. :/

Contact me on https://t.me/keeshux, and I'll see what I can do.

Thank you.! New to Telegram and got limited to send you a message apparently. Working on getting spam flag lifted.

[email protected] in that case

Then the problem is on the server side. Not much I can do about it. :-/ Once again I think of discontinuing providers…

Ok, thanks for trying it

If I provided a newly generated config profile from my provider would that be helpful in fixing your provider template for TorGuard and possibly others? Just perusing the repo I noticed under torguard.js it has entries for both compression framing and compression algorithm, but I don’t have the knowledge or understanding of your code to know if both existing in the template means the options are passed to the client profile you are using to initiate the connection, or if simply existing is triggering the “unsupported” enum in the code.

I don’t see any compress or allow-compression asym in my new configs from TorGuard which indicates to me that the server config no longer uses it, however I am following up with their support to find out for sure.

Send me an updated TorGuard .ovpn config to [email protected]

Done