VPNMON VPNMON-R3 v1.8.2 -Nov 23, 2025- Monitor OpenVPN/Wireguard WAN/Dual-WAN Health & Random Reset Multiple Connections (Available in AMTM!)

[JTnola]

I think everything’s working, but do yall know what this is about? (Running 1.8.1, but it also showed apparently on 1.8.0)

#BadNumber

RT-AC86U

 

[Viktor Jaep]

I think everything’s working, but do yall know what this is about? (Running 1.8.1, but it also showed apparently on 1.8.0)

#BadNumber

RT-AC86U

Weird. Could you please send me a screenshot of your settings? Or a copy of your vpnmon-r3.cfg?

 

[Viktor Jaep]

I think everything’s working, but do yall know what this is about? (Running 1.8.1, but it also showed apparently on 1.8.0)

#BadNumber

RT-AC86U

Friendly follow-up, @JTnola?

 

[Viktor Jaep]

I think everything’s working, but do yall know what this is about? (Running 1.8.1, but it also showed apparently on 1.8.0)

#BadNumber

RT-AC86U

@JTnola ... I've tried everything I could to duplicate this, but have not been able to.

Would you mind turning debug mode on in my script, and capture this error, save the output to a txt file, and send to me please? Here's some instructions:

In the vpnmon-r3.sh script, uncomment the following lines (only the left-most #):

6961 #DEBUG=; set -x # uncomment/comment to enable/disable debug mode
6962 #{              # uncomment/comment to enable/disable debug mode

8055 #} #2>&1 | tee $LOG | logger -t $(basename $0)[$$]  # uncomment/comment to enable/disable debug mode

Run the script until you see those errors... then kill (CTRL-C) the program and save the output (everything before and after where the error occurs), paste into a text file, and please share with me?

Immensely appreciated... and sorry to make you go through these steps.

Also, seeing a copy of your vpnmon-r3.cfg would also help along with this while you're at it! LOL. Thank you!

 

[Viktor Jaep]

Nevermind, @JTnola ... I *finally* found it. Working on a fix as we speak.

 

[Viktor Jaep]

Small bugfix patch coming your way! Enjoy! Thanks to @JTnola for reporting this... and glad I was finally able to find this!

What's new!?
v1.8.2 - (November 23, 2025)
- PATCH: Thanks to @JTnola for sharing a "[: bad number" bug he was experiencing. This hard-to-find bug only seemed to come up in certain scenarios when using the limited 2-OVPN slot configuration. Variables weren't being assigned that the script was expecting, causing these errors. Fixed!

Download link (Or update directly with AMTM/VPNMON-R3):

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/VPNMON-R3/main/vpnmon-r3.sh" -o "/jffs/scripts/vpnmon-r3.sh" && chmod 755 "/jffs/scripts/vpnmon-r3.sh"

Significant Screenshots:

This was what @JTnola was experiencing:

And showing the fix

 

[JTnola]

@JTnola ... I've tried everything I could to duplicate this, but have not been able to.

View attachment 69142

Would you mind turning debug mode on in my script, and capture this error, save the output to a txt file, and send to me please? Here's some instructions:

In the vpnmon-r3.sh script, uncomment the following lines (only the left-most #):

6961 #DEBUG=; set -x # uncomment/comment to enable/disable debug mode
6962 #{              # uncomment/comment to enable/disable debug mode

8055 #} #2>&1 | tee $LOG | logger -t $(basename $0)[$$]  # uncomment/comment to enable/disable debug mode

Run the script until you see those errors... then kill (CTRL-C) the program and save the output (everything before and after where the error occurs), paste into a text file, and please share with me?

Immensely appreciated... and sorry to make you go through these steps.

Also, seeing a copy of your vpnmon-r3.cfg would also help along with this while you're at it! LOL. Thank you!

Sorry just seeing these now
Glad you figured it out
Sorry I left you high and dry, so it was more difficult than need be
You’re the best — no matter what anybody says!! lol

 

[Viktor Jaep]

Sorry just seeing these now
Glad you figured it out
Sorry I left you high and dry, so it was more difficult than need be
You’re the best — no matter what anybody says!! lol

Glad to help... continuous improvements!

 

[CaptainSTX]

Have you tried using the Recovery Timeout Opportunities? I've set mine to 3 and that has really helped stability of the connection, instead of having it reset after 1 failed response.

I'm only getting emails nightly now after it goes through it's scheduled reset. Email rate limiting is also an option now if you find it too spammy.

One feature of VPMON I am finding very useful is restarting my WG clients in the middle of the night. My experience with StrongVPN WG clients is after a few days the download speeds would drop from 600+Mbps to as low as 150 Mbps. This was consistent for three clients connecting to servers at distances between 200 miles - 4,500 miles. Stopping and then restarting the clients restores the download speeds.

Thanks again Viktor.