Openvpn on tplink C60 router cannot connect after router reboot

Openvpn on tplink C60 router cannot connect after router reboot

Openvpn on tplink C60 router cannot connect after router reboot
Openvpn on tplink C60 router cannot connect after router reboot
2024-08-12 01:46:26
Model: Archer C60  
Hardware Version: V2
Firmware Version: 2.0.1

 

Openvpn server setup with tplink ddns ! 

 

Everytime when the Archer C60 is rebooted , openvpn clients (both openvpn connect and openvpn for android clients) can no longer connect again ! A new certificate has to be generated again and exported to the clients again before the Archer C60 openvpn server can be connected by openvpn clients again.

 

Have searched the forum and saw a user suggested to change the time servers to "pool.ntp.org" ! I do change the time server to pool.ntp.org but still fail to connect to the Archer C60 openvpn server after reboot !

 

Suggestions to resolve this problem are most welcomed !

  0      
  0      
#1
Options
4 Reply
Re:Openvpn on tplink C60 router cannot connect after router reboot
2024-08-13 07:55:57

  @cm852 

 

Hi, thanks for posting question here.

After rebooting C60, you may check whether device time on the router is synchronized.

And you may share the log of your OpenVPN app, then we can take further analysis.

 

  0  
  0  
#2
Options
Re:Openvpn on tplink C60 router cannot connect after router reboot
2024-08-13 14:34:39

  @Marvin_S 

Dear Marvin

 

Thanks for your reply !

 

I have checked the Archer C60 router using the pool.ntp.org time server is synchronised with my local time !

 

I am using the "openvpn for android" app as my client for connection ! The openvpn connection log will be in the next post for your reference ! 

 

Looking forward to hearing from you soon !

 

Thanks

 

  0  
  0  
#3
Options
Re:Openvpn on tplink C60 router cannot connect after router reboot
2024-08-13 14:36:11
  0  
  0  
#4
Options
Re:Openvpn on tplink C60 router cannot connect after router reboot
2024-08-16 08:18:05

  @cm852 

 

Hi, thanks for your update~

You may try to add this at the beginning of the  certificate:

setenv opt verify-x509-name 0

 

  0  
  0  
#5
Options