Solution 'Authentication failed, Server TLS version is too low' appears when connecting OpenVPN of DSL Modem
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
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thanks for sharing this, the explanation clearly identifies the OpenVPN TLS mismatch issue after the client update. I’ll apply the suggested firmware or adjust the minimum TLS version as advised and will report back if the connection is restored successfully.
- Copy Link
- Report Inappropriate Content
Hello @Dmadma ,
Could I confirm the model of your modem? Is it Archer VR2800 or Archer VR2800v? If possible, please provide the modem's firmware and hardware versions. Please refer to How to find the hardware and firmware version of my TP-Link device
This post is about the Archer VR2800. I will also inquire about the firmware update progress for this model.
- Copy Link
- Report Inappropriate Content
Joseph-TP wrote
Updated on December 3:
Hi All,
Except for the Archer VR2800 V1, the latest firmware version for all other affected models has fixed this anomaly.
Please confirm that your modem's firmware is up to date:
- Archer VR400(EU)_V3_250905
- Archer VR600(EU)_V3_240929
- Archer VR2100(EU)_V1_240903
- Archer VR2100v(EU)_V1_241012
- Copy Link
- Report Inappropriate Content
Well, it's now been two years since I originally posted here about this problem on my VR2800 and no solution has yet been offered.
In fact, such a long time has passed that I had to reset my password!
Due to this disgraceful lack of customer service I have now thrown the VR800 in the bin and will never use TP-Link products again!
With so many other choices of hardware out there I can only recommend to people that they avoid TP-Link.
Thanks to your lack of support you have lost a customer and, potentially, many others.
Goodbye TP-Link!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 29073
Replies: 34
Voters 2
