What's new

Wireguard VPN client does not autostart after reboot

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

inandoutofRange

New Around Here
Setup:
RT-AX86U with 3004.388.8_2
syslog attached
I am able to setup wireguard from Proton VPN and everything is fine until the router reboots. After the router boots up I am able to restart the client by clicking the apply button.
I suspect the boot sequence needs to be updated to start the wireguard clients after boot is completed. Anyone else have this issue?

Would someone provide me a way to restart the wireguard client automatically after boot is completed as a workaround?

Before I manually restart the client, There is a client log error along the lines of it cannot find the interface/protocol


1728606895155.png
1728607006320.png
 
Last edited:
I am able to setup wireguard from Proton VPN and everything is fine until the router reboots. After the router boots up I am able to restart the client by clicking the apply button.
I suspect the boot sequence needs to be updated to start the wireguard clients after boot is completed. Anyone else have this issue?
dont have this issue. but only way Wireguard would "fail" to start is if the endpoint cannot be resolved to an ip at the time of start. do you have any special setup for router DNS?

Would someone provide me a way to restart the wireguard client automatically after boot is completed as a workaround?
if you SSH into the router and execute:
Code:
service "start_wgc 2"
or possibly
Code:
service "restart_wgc 2"

if that works you could probably put it in the appropriate User script: https://github.com/RMerl/asuswrt-merlin.ng/wiki/User-scripts to have it executed at a time when your router is capable of resolving the endpoint.
 
I ended up creating a services-start but needed to know whats wrong :p
Performed hard factory reset and reconfigured from scratch.. That seems to have fixed it.

Thank you for taking the time to review and respond!! :)
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top