Solution Deco OpenVPN Client Always Connecting
Solution Deco OpenVPN Client Always Connecting

Over the past few weeks, there has been some feedback that the Deco VPN Client status consistently shows as "connecting."
After further troubleshooting with the engineers, we have identified several suggestions that have successfully resolved most cases.
1. The incorrect server username and password.
Although Deco APP VPN Client Wizards do not ask for mandatory VPN server credentials, it is suggested to fill in both. These credentials are usually not the same as the dedicated VPN APP login username and password, especially for NordVPN.
How to find the NordVPN server username and password:
2. Extra modification to the OpenVPN config file.
#1 If the Deco is set to connect to CyberGhost VPN, please test the following suggestions:
- Manually create the unified format-Manually create the unified format for OpenVPN profile
- Open the OpenVPN config file via Notepad and remove "ncp-disable".
#2 If the Deco is set to connect NordVPN, please test the following suggestions:
- If you are using a "NordVPN token" to create a VPN Client connection, please delete the current configuration and try the "Custom" profile to manually upload the OpenVPN config file.
- Open the OpenVPN config file via Notepad and remove "auth-user-pass".
#3 Deco APP doesn't allow adding an individual CA certificate, so you might need to add the CA to your OVPN File before uploading the VPN config file to Deco.
We will update more suggestions here to address the VPN Client connection issue. If you also figure out any other configurations that might potentially cause the VPN Client failure, please feel free to share your insights in the comments.
Thank you very much!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello, here's the firmware version (see attached screen capture).
I found a not-so-ideal solution: I ended up purchasing an external WIFI adapter for my Desktop, and now it is being used as an access point for my lab.
Meanwhile, Deco mesh is still "connecting" :(
Edited to add:
-Do you mean the outgoing IP address on the selected VPN clients only changed(encrypted) after a manual reboot of the devices themselves?
Yes, it used to work after a manual reboot, but now it fails soon as mesh ends booting.
It's sad to see a company like TP-Link not doing proper testing before releasing firmware updates.
- Copy Link
- Report Inappropriate Content
Hi, thanks for the update.
I do think the engineers have done many tests before releasing the firmware. Some issues probably can't occur in the lab environment.
Can I have the model number of the TP-Link wireless adapter?
I was a little curious about the mentioned workaround solution. How did you use this wireless adapter?
Or when you connect the desktop to the Deco network via this new adapter, the real IP can be protected, and only the VPN server IP is displayed?
Or do you enable a hotspot on the desktop to provide a separate wireless network for the lab devices?
Do you mean the VPN Client status is still "connecting"? I thought you mentioned before that the VPN Client status was "connected"?
Wait for your reply.
Best regards.
- Copy Link
- Report Inappropriate Content
@David-TP Yup, it used to say "connected", but in practice, my real IP was the same when visiting whatsmyip. Now it just says "connecting".
Anyway, I know you have good intentions, but nothing is going to change regarding this issue (since it's something that used to work fine), and TP-Link engineers haven't experienced it in their environment.
Good luck @David-TP, thanks for your time.
P.S.: I will stop recommending this product and will edit my review on Amazon.
- Copy Link
- Report Inappropriate Content

Information
Helpful: 1
Views: 2911
Replies: 13
Voters 0
No one has voted for it yet.