Home Network Community > Wi-Fi Routers > VPN Config importing failed
< Wi-Fi Routers

VPN Config importing failed

VPN Config importing failed

VPN Config importing failed
VPN Config importing failed
Tuesday
Tags: #VPN
Model: Archer AX12  
Hardware Version: V1
Firmware Version: 1.2.1 Build 20250729 Rel. 73566(4555)

Hi TP-Link Support Team,

​I am writing to report a persistent and critical firmware bug regarding the VPN Client on my Archer AX12 V1. I am unable to import any .ovpn configuration file, even those generated by the router itself.

​Below is the detailed information:

​1. Model, Hardware, and Firmware Version:

  • ​Model: Archer AX12
  • ​Hardware Version: V1
  • ​Firmware Version: 1.2.1 Build 20250729 Rel. 73566(4555)

​2. VPN Server Type:

  • ​Standard OpenVPN servers (Testing with both TCP and UDP protocols).

​3. VPN Type on TP-Link Router:

  • ​OpenVPN Client.

​4. VPN Client Software for Testing:

  • ​Software: Official OpenVPN Connect app (Windows & Android).
  • ​Test Result: I can successfully connect to the VPN servers using these apps on the same network. The .ovpn files are verified and fully functional on other devices.

​5. Detailed Error Description & Screenshots:

  • ​Step: The failure happens during the "Import" step.
  • ​Definitive Evidence: I even exported the configuration file from this router's own VPN Server and attempted to import that exact file into the VPN Client section. Even the router's own generated file fails with "Config importing failed"!
  • ​System Log Errors: * ERROR [1808] Config importing failed
    • ​DEBUG [1808] Failed to read LAN_OFF
    • ​The errors are consistently triggered by the "Led Controller" process.

​6. Troubleshooting Done:

  • ​Time/NTP: System time has been manually set and is correct according to the logs.
  • ​File Structure: Files are in Unified/Inline Format.
  • ​Factory Reset: Performed multiple hardware factory resets with no success.
  • ​Interface: Tested via Ethernet using Chrome and Edge browsers.

​Conclusion:

 

There is a clear conflict between the Led Controller [1808] process and the VPN configuration handler in this firmware version. Could you please provide a Beta Firmware or a fix for this Archer AX12 V1 "LAN_OFF" bug?

 

System log:

2026-02-03 15:42:16 Led Controller INFO [1808] Start to run WAN1_ON 2026-02-03 15:42:16 Led Controller INFO [1808] Start to run WANO_OFF 2026-02-03 15:42:16 Led Controller ERROR [1808] Config importing failed 2026-02-03 15:42:16 Led Controller DEBUG [1808] Failed to read LAN_OFF 2026-02-03 15:42:01 Led Controller INFO [1808] Start to run WAN1_OFF 2026-02-03 15:42:01 Led Controller INFO [1808] Start to run WANO_ON

 

  0      
 
  0      
 
#1
Options
2 Reply
Re:VPN Config importing failed
Wednesday

Hello @X125012 ,

Welcome to our community.

 

Is the network stable after the firmware update? Please try the beta firmware and check if it helps.

Archer AX12(EU)_V1_1.2.2 Build 20250904(Beta Firmware) 

 

Manually updating firmware, you can refer to Case 1 of How to upgrade the firmware on the TP-Link Wi-Fi Routers

Welcome to Our Community！ Check Out the Latest Posts: △New Firmware for Archer BE800 V1 to Support VPN Merge, EasyMesh Guest/IoT Network Extend, and More △Enhanced EasyMesh Support with Extended Guest/IoT/MLO Networking and Advanced Features for BE550 V2 △New Firmware for Archer BE900 V2 to Support Multi-WAN, DoH/DoT, EasyMesh in AP Mode and More △New Firmware for Archer BE260/Archer BE400 to Support VPN Merge, New ECO Mode, and More If you found the post or response helpful, click Helpful. If an answer solves your problem, click Recommended Solution so that others can benefit from it.
  0  
  0  
#2
Options
Re:VPN Config importing failed
Yesterday - last edited Yesterday

  Hi @Joseph-TP,

​Thank you for providing the Beta firmware. I have manually updated the router to version 1.2.2 Build 20250904, but unfortunately, the issue persists.

​I am still getting the exact same error: "Config importing failed".

​Important observations with the Beta firmware:

  1. ​The error occurs even when the VPN Client is in the "Disconnected" state.
  2. ​The System Log still shows the same process conflict: Led Controller ERROR [1822] Config importing failed and DEBUG [1822] Failed to read LAN_OFF.
  3. ​I have performed a factory reset after the beta update, but it did not help.

 

​It seems the "Led Controller" process is still blocking the file import mechanism in this hardware version (V1). Is there any other fix or a different beta version that addresses this specific [1822] / LAN_OFF error?

 

System log:

2026-02-05 19:00:56 Led Controller INFO [1822] Start to run WAN1_ON

2026-02-05 19:00:56 Led Controller INFO [1822] Start to run WAN0_OFF

2026-02-05 19:00:56 Led Controller ERROR [1822] Config importing failed

2026-02-05 19:00:56 Led Controller DEBUG [1822] Failed to read LAN_OFF

2026-02-05 19:00:41 Led Controller INFO [1822] Start to run WAN1_OFF

2026-02-05 19:00:41 Led Controller INFO [1822] Start to run WAN0_ON

 

 

 

 

 

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 103

Replies: 2

Tags

VPN
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.