This Article Applied to:

Archer BE230_V1/V1.20_1.2.1 Build 20250804

Archer BE230_V2_1.1.0 Build 20250718

Archer BE220_V1_1.1.0 Build 20250718

Archer BE900_V2_1.2.0 Build 20250722

Archer BE700_V1_1.2.1 Build 20250709

Phenomenon:

We have received feedback from some users that after their routers updated the latest firmware, OpenVPN clients stopped working or were unable to connect normally.

Our development team has identified the reason: when an Ovpn file contains two consecutive hash symbols (##) and uses a newline character between them, the reported unexpected behavior occurs.

The following are some feasible solutions.

Available Solution:

Solution 1:
Manually edit the . ovpn configuration file as below:

• Open the . ovpn file with a text editor (e.g., Notepad).
• Locate any lines that contain two consecutive hash symbols (##) with a line break between them. 
• Delete these lines entirely. 
• Save the file and re-import it into the router's OpenVPN settings.

Solution 2:
For some of the affected models, we also have corresponding beta firmware versions. This beta version enables the router to read configuration files correctly without manual editing.

Note: 

• Please be sure you have read the Beta Test Agreement before upgrading the pre-release firmware!
• For the sake of insurance, it's always recommended to save a copy of the router's Backup Config file before upgrading or downgrading.
• You may follow the guide to upgrade the firmware of your router. How to Upgrade the Firmware on the TP-Link Wi-Fi Routers.

If there are beta firmwares of other models, I will synchronize them here on time.
Gradually, we will also release new firmwares to fix this abnormal behavior for affected models.

In addition, if you have other models that encounter similar situations after updating the firmware, please try the solutions above to see if they are helpful.
We welcome you to provide additional details, including the affected models or your experience with the solutions.

Thanks for your feedback and cooperation.