Hide.me VPN - no automatic reconnect

Hello,

I have set up hide.me VPN via Wireguard using the instructions from the GL.iNet Support site on my AX-1800 Flint.

Everything works flawlessly, also the speed is phenomenal.

The only problem I have is that the VPN provider disconnects every 24 hours due to abuse prevention. Normally the wireguard connection should reconnect. However, this does not work.

Now I have already written to hide.me support, this suspects a change in the last firmware updates, because with the older firmwares the automatic reconnection worked.
The support clarifies it nevertheless also again with the developers of the Router configuration.

At the moment, I’m trying to reboot the router automatically every 24 hours. This solution works, but should not be the permanent solution.

I use the firmware version 4.2.1

Are the firmware developers aware of any change in this regard that could explain this problem?

Thank you very much for the answer.

Can you show full system log? you can export it in SYSTEM->LOG->Export

Hi,

i attached the system log below.

Thank you!

system2.zip (4.2 KB)

(post deleted by author)

I have written with Hide.me.

"our developer already submitted this issue to GL-iNet, and we are waiting for the new firmware release.

At the moment all 4.7 versions are affected."

Please run the following commands:

cd /lib/netifd/proto/cp wgclient.sh wgclient_bak.sh

if this commands reports error, stop here, and let me know what the error is.
edit file wgclient.sh

nano wgclient.sh

change line 31 from

${script} ${config} &

to

${script} ${config}

after that, run the following command:

uci show

and verify that the network.wgclient.pre_setup_script looks like this:

network.wgclient.pre_setup_script='/etc/wireguard/scripts/hideme.sh connect'

if it's not, run the following commands

uci add_list network.wgclient.pre_setup_script='/etc/wireguard/scripts/hideme.sh connect' uci commit network

after that, run the uci show command again and check if it's properly set.

This should fix the issue.

Unfortunately, this did not provide the solution. The error persists. Does anyone have any ideas?