@stu1234 

stu1234 wrote

  @Sunshine 

 

Is there no fix for the Archer VR 2800 coming? I see it's still listed as a current product on TP-Link's website and remains for sale. Enabling insecure protocols is not a suitable long term workaround for a VPN, TLS 1.0 has been deprecated for 3+ years now due to vulnerabilities and the current version TLS 1.3 has been in available for 5 years. Do TP-Link have plans to provide firmware that supports TLS 1.3?

Agreed, I'm also looking at Archer VR600 v2 (Australian version) and worried about the vulnerabilities now.

  @stu1234 Archer VR2800 V1. Have Updated the routher firmware but I'm also having the exact same issue. Openvpn Android Client Version 3.4.0 allows to enforce to TLS version 1.3. Is there an update to the firmaware Coming?? I really need this working

  @Sunshine 

I have an Archer VR2800 and still can't use VPN on my Android phone unless I switch the OpenVPN client to 'Insecure'.

It really is about time this problem was solved! Telling us to use an insecure link simply isn't acceptable.

Because I have OpenVPN enabled on my VR2800 it leaves me vunerable to hacking attacks via the VPN server built into the router.

Come on Tp-Link, GET THIS SORTED OUT IMMEDIATELY!

  Hi @Sunshine ,
any plan to release a firmware update also for VR1210 v1 to address the issue?
I really don't like the "Insecure" solution.

Thank you

  @Gremnet  Lowering the security level on the device as you suggested worked for me (Motorola G9 phone Android 11) 

Sunshine wrote

This Article Applies to:

Archer VR2100 V1, VR2100v V1, VR600 V3, VR400 V3, VR2800 V1

 

Issue Description:

After updating the OpenVPN client version, some users might be unable to connect to the OpenVPN server of DSL modem router, and OpenVPN client prompts "Authentication failed, and Server TLS version is too low".

 

Solutions:

1. For Archer VR2100 V1 and VR400 V3, please try installing the following beta firmware:

For VR2100 V1: Archer_VR2100_V1_1.8.0_Build_231114

For VR400 V3: Archer_VR400_V3_1.6.0_Build_231024

 

Note: Please be sure you have read the Terms and Conditions for TP-Link Beta Firmware before proceeding.

 

2. For all models, please open the OpenVPN Connect client >> click the three-line symbol in the upper left corner >> Settings >> Slide to the bottom to find the Advanced Settings >> Set Minimum TLS Version to TLS1.0, then test if it will be able to connect the OpenVPN Server properly.

 

If there is any further issue, please leave us your comment and provide the following information:

1) Model no., hardware and firmware version of your TP-Link DSL modem router

2) The version of your OpenVPN Client software

3) Screenshot of the error message and also the Minimum TLS Version

 

  @Sunshine 

  @Sunshine  It seems like there might be a compatibility issue with the TLS version. Have you tried updating the firmware of your DSL modem or adjusting the OpenVPN settings? That could potentially resolve the authentication error. I had same issue before but i fixed it immediately because I play coc a lot a lot. And i need seamless internet at any cost. You can also download the game here: clashofclansproapk

TLS 1.0 and TLS 1.1 are now considered insecure (take a look at the OpenVPN website).

Telling users of TP-Link hardware that they must leave an insecure piece of software open to attack if they want to use VPN to connect to their routers is simply unacceptable.

On the 19th February 2024 @Sunshine posted that this issue would be addressed in an update for the VR2800. It is now May and this update still hasn't been delivered.

Needless to say, in the future I would not even consider buying TP-Link hardware!

  @Sunshine I would also be interested in TLS 1.3 solution being rolled out for VR600 v2. Suggesting using an insecure connection misses the point of VPN in the first place. As i require my personal VPN for work, this is has become quite urgent, since there's been no update since Feb 2024!