OpenVPN initializing forever

[a-seus-am-i]

I just upgraded my RT-AC86u from stock to Merlin 384.13 and the OpenVPN server isn't working. When I go to the server page, it says "Initialinzing the settings of OpenVPN server now, please wait a few minutes to let the server to setup completed before VPN clients establish the connection." and it's spinning forever. Any ideas on how to address this?

I even set it back to defaults and tried again but same hang.

Note that

 

[RMerlin]

Check your System Log.

 

[Zonkd]

I just upgraded my RT-AC86u from stock to Merlin 384.13 and the OpenVPN server isn't working. When I go to the server page, it says "Initialinzing the settings of OpenVPN server now, please wait a few minutes to let the server to setup completed before VPN clients establish the connection." and it's spinning forever. Any ideas on how to address this?

I even set it back to defaults and tried again but same hang.

Note that

I’ve seen that before. How long are you waiting? Before VPN server starts for the very first time the router has to perform slow task of generating encrypted pki stuff. If it keeps getting stuck generating pki and you really want to get technical you could generate the pki manually on your PC at command line with easyrsa OpenSSL and openvpn2 then copy-paste pki keys and certs and dh to the server advanced settings. Personally I’d once more try clear nvram reset and cleanly flash firmware then reset one more time.

 

[martinr]

I just upgraded my RT-AC86u from stock to Merlin 384.13 and the OpenVPN server isn't working. When I go to the server page, it says "Initialinzing the settings of OpenVPN server now, please wait a few minutes to let the server to setup completed before VPN clients establish the connection." and it's spinning forever. Any ideas on how to address this?

I even set it back to defaults and tried again but same hang.

Note that

Like Zonkd, I have also seen this when setting up OpenVPN Server. You didn’t say if the rest of the router was working or if you have connected to the Internet.

You will get this behaviour if you try to set up OpenVPN without first connecting to the Internet.

 

[jsbeddow]

I just upgraded my RT-AC86u from stock to Merlin 384.13 and the OpenVPN server isn't working. When I go to the server page, it says "Initialinzing the settings of OpenVPN server now, please wait a few minutes to let the server to setup completed before VPN clients establish the connection." and it's spinning forever. Any ideas on how to address this?

I even set it back to defaults and tried again but same hang.

Note that

I have also seen this, and my issue was resolved after clearing (formatting) the jffs partition. In my case I did not need to do the full nvram erase, but of course you will need to reconfigure your OpenVPN server and/or reimport the certs/config for that (not the full jffs backup of course).

 

[CaptainSTX]

Have you set up DDNS and is it correctly reflected on the network map page?

Is the IP shown a public IP? If it isn't a public IP and/or you are double NATed then getting the server to work is going to take some extra steps.

If DDNS isn't functioning the server won't come up.

Have you tried to also run a VPN client on your router? If you can't get either to work you may have a dysfunctional router.

 

[Grisu]

Have you set up DDNS and is it correctly reflected on the network map page?

Is the IP shown a public IP? If it isn't a public IP and/or you are double NATed then getting the server to work is going to take some extra steps.

If DDNS isn't functioning the server won't come up.

Have you tried to also run a VPN client on your router? If you can't get either to work you may have a dysfunctional router.

Merlin added DDNS support in Double NAT some releases ago, so it should work either with public or private IP.

 

[CaptainSTX]

Merlin added DDNS support in Double NAT some releases ago, so it should work either with public or private IP.

I know it can be made to work but in my experience it may take an extra step or two.

When I have been fooling around with my AC86s in a bench setup double NATed behind another router it doesn't automatically function or at least it didn't for me. One issue I saw was the ovpn file it generates, to send to potential clients used the private LAN address issued by router 1 to router 2 as its WAN IP.

I didn't spend any time tweaking settings on both routers as I was just interested in seeing if the repaired AC86 worked and since its 2.4 Ghz radio didn't I sent it back.

 

[a-seus-am-i]

Thanks for all the replies! So the router is working fine and the internet is working. I have a gigabit fiber connection if that makes any difference. It was working on the stock firmware, just stopped working when I updated to merlin. DDNS says it's working ok on both the network map page and DDNS settings, although I see what looks like a new option labeled "Method to retrieve WAN IP". That's set to internal.

I tried to clear the system log, set it to debug level, and try to start the VPN server but nothing seems to be getting logged now. Really confused as to why that is.

I've waited up to 10 min and nothing.

 

[jsbeddow]

Thanks for all the replies! So the router is working fine and the internet is working. I have a gigabit fiber connection if that makes any difference. It was working on the stock firmware, just stopped working when I updated to merlin. DDNS says it's working ok on both the network map page and DDNS settings, although I see what looks like a new option labeled "Method to retrieve WAN IP". That's set to internal.

I tried to clear the system log, set it to debug level, and try to start the VPN server but nothing seems to be getting logged now. Really confused as to why that is.

I've waited up to 10 min and nothing.

I strongly suggest using the "format jffs partition on next reboot"option (on the administration page), followed by a reboot of course: this resolved my identical problem of the forever spinning circle on the OpenVPN server page, and it is now functioning correctly. Of course I did have to reconfigure the OpenVPN server and reimport my certs.

 

[a-seus-am-i]

I strongly suggest using the "format jffs partition on next reboot"option (on the administration page), followed by a reboot of course: this resolved my identical problem of the forever spinning circle on the OpenVPN server page, and it is now functioning correctly. Of course I did have to reconfigure the OpenVPN server and reimport my certs.

Thanks. Does this reset the entire router so I'll have to reconfigure everything again?

 

[jsbeddow]

Thanks. Does this reset the entire router so I'll have to reconfigure everything again?

No, it is far less rework required. If you are running the scripts under the amtm "umbrella" (Diversion, Skynet, etc...), you will have to reinstall amtm and possibly the others. If you were running without any of the add-on scripts, it will require almost no reconfiguring, other than OpenVPN.

 

[a-seus-am-i]

No, it is far less rework required. If you are running the scripts under the amtm "umbrella" (Diversion, Skynet, etc...), you will have to reinstall amtm and possibly the others. If you were running without any of the add-on scripts, it will require almost no reconfiguring, other than OpenVPN.

So I tried that and it didn't seem to do anything. It still won't connect. Also, is it supposed to wipe out all your previous configuration settings? Because it didn't do that either. I still see all the VPN settings I had previously. I can't seem to remove them either. I tried hitting the default button on the VPN page to reset them but it didn't.

I tried hooking up my VPN client as well (PIA) and that didn't work either. I just imported the OVPN file provided by PIA and put in my user name and password but it won't connect.

My system log seems to be working again after the reboot but I don't see any entries related to VPN in there. On an unrelated note, I cleared the log before reboot and when it started up it put in entries from way in the past first then jumped to today's date which is weird.

 

[CaptainSTX]

Having both the VPN clients and VPN servers stop working was a frequent problem I have had with my AC86 and the replacements or repaired units ASUS sent me.

The only way I could get them working was the nuclear reset as outlined by LD&D followed by a factory reset, format JFFS partition and then manually entering all the settings again. Also tried reflashing both ASUS and Merlin firmware. Never could get both the Server and Clients to work for more than a day or two.

If the above doesn't work and can't get a stable router for you then consider returning the router or doing an RMA with ASUS.

 

[a-seus-am-i]

Having both the VPN clients and VPN servers stop working was a frequent problem I have had with my AC86 and the replacements or repaired units ASUS sent me.

The only way I could get them working was the nuclear reset as outlined by LD&D followed by a factory reset, format JFFS partition and then manually entering all the settings again. Also tried reflashing both ASUS and Merlin firmware. Never could get both the Server and Clients to work for more than a day or two.

If the above doesn't work and can't get a stable router for you then consider returning the router or doing an RMA with ASUS.

Thanks. It looks like I'll have to go the factory reset and reconfigure route (not sure what you meant by LD&D nuclear reset). Both the server and client was working pre Merlin firmware update on the latest stock, so hopefully it's just the update that needs to get reconfigured.

 

[CaptainSTX]

Look in member's L&LD's signature block. He outlines a very complete process for resetting and stabilizing a router.

Hopefully it will help you get your router into a stable condition and everything will be good and VPNs will work. Didn't work for me, but perhaps it will for you and you won't have to enter into the ASUS RMA purgatory.

Good luck.

 

[a-seus-am-i]

Look in member's L&LD's signature block. He outlines a very complete process for resetting and stabilizing a router.

Hopefully it will help you get your router into a stable condition and everything will be good and VPNs will work. Didn't work for me, but perhaps it will for you and you won't have to enter into the ASUS RMA purgatory.

Good luck.

Thanks. I got it reset (took a bunch of tries) and now it's working after reconfiguring everything. Thanks everyone for the help.

 

[jsbeddow]

Thanks. I got it reset (took a bunch of tries) and now it's working after reconfiguring everything. Thanks everyone for the help.

Did this OpenVPN server connection stay up and stable for you? My server connection just went south (again, after behaving normally for a month or two), and I haven't had time to do a full reset to see if that solves it this time. I hope I don't have one of the (many?) problematic 86U routers, but am beginning to think that I do (2018 production date....yes, I have seen the other threads on this topic). Ugh, I am not sure if I am up for the battle to get a good one from the Asus RMA procedure hell.

 

[CaptainSTX]

I am not sure if I am up for the battle to get a good one from the Asus RMA procedure hell.

The good news is that if your signature block has your correct geographic location the turn around time for receiving a "refurbished router??????" will be much quicker than mine. ASUS's RMA location is in Newark, CA. In my case shipping the router back by FedEX ground from Florida takes 6-7 days from Florida to CA., 2-3 days in Newark and then another 6-7 days back to Florida.

 

[a-seus-am-i]

Did this OpenVPN server connection stay up and stable for you? My server connection just went south (again, after behaving normally for a month or two), and I haven't had time to do a full reset to see if that solves it this time. I hope I don't have one of the (many?) problematic 86U routers, but am beginning to think that I do (2018 production date....yes, I have seen the other threads on this topic). Ugh, I am not sure if I am up for the battle to get a good one from the Asus RMA procedure hell.

It's been working ok for me. I don't connect to it a ton, only when I need to get to my home network, but so far I haven't had any issues.