VPN connection creation fails with 'Configuration failed' error
VPN connection creation fails with 'Configuration failed' error
I updated this morning my T6-423 running TOS 5.1.145 (which up until the update, had a working OpenVPN connection configured and working) to TOS 6.0.530 manually and once completed, updated to TOS 6.0.610. Once completed and because the system settings were reset, I tried to setup a VPN connection using the 'Importing OpenVPN file' method and the system always returns a 'Configuration failed' error message.
Re: VPN connection creation fails with 'Configuration failed' error
Hello, there are posts on the same topic in the forum. You can refer to them and try to solve the problem.
viewtopic.php?t=2821
viewtopic.php?t=6974
In addition, you can try to set the user authentication and data encryption methods when enabling OpenVPN. I hope this will be helpful to you!
Re: VPN connection creation fails with 'Configuration failed' error
The first link refers to VPN Server application. It's not my case. I'm trying to create a vpn connection from my provider on my NAS via Control Panel - Network- VPN Connection. The second link, those steps are unclear for me.
This clearly is a problem with TOS6 because even the same VPN connection with the same provider was working under TOS 5.1.145. Only when my NAS was updated to TOS 6, the Configuration failed error started to show up.
I tried to submit the system log via email to [email protected] as instructed by the Support and Help app, but my email was undelivered as it was classified as Spam.
- sianderson
- Silver Member
- Posts: 417
- Joined: 02 Aug 2020, 03:42

Re: VPN connection creation fails with 'Configuration failed' error
this might be a TOS6 thing but i gave up with the built in VPN server, i was trying to set up a L2TP connection but i just struggled to establish a connection to it, no error messages but when i viewed the users in the app it just wouldnt show any ticks by the L2TP and couldnt see a way to set it,
i ended up giving up on the built in APP, i was setting up a WIndows Server VM using virtual box so i just configured routing and remote access in the windows server and its now working perfectly, so that is another option is to use a VM
i ended up giving up on the built in APP, i was setting up a WIndows Server VM using virtual box so i just configured routing and remote access in the windows server and its now working perfectly, so that is another option is to use a VM
F2-424 TOS 7.0.0765
F2-423 TOS 7.0.0765
F2-210 TOS 4.2.44
D4-320
C/O
F4-424 TOS 6.0.794
F2-423 TOS 7.0.0765
F2-210 TOS 4.2.44
D4-320
C/O
F4-424 TOS 6.0.794
