Some users reported a broken VPN on Stable 4.8 (non -op24) on Beryl AX
Beta 4.8.0-op24 (July/29th) seems to be OK
1 Like
@bruce One bug, that came to my attention: I'm running the latest OP24 with my MT6000 and AdGuardHome (Version: v0.107.64) values are not showing up.
@bruce Any updates as to what caused this crash from the Dev team?
I've been running 4.8.0-op24 on my Flint 2 with Wireguard Client - good results so far.
A few days ago, I added 3 websites to be excluded from the VPN.
This worked fine until this morning, when no VPN was on any device, despite the GUI saying it was.
I activated WG VPN via Luci - all clients got VPN - including IP's meant to be excluded.
After some testing, it looks like the culprit are those 3 excluded websites.
Once removed, I could control each devices VPN on/off.
All working again - but I can no longer exclude websites.
Is this a known fault?
Thanks for your feedback.
I tested the preinstalled ADG (v0.107.56) in v4.8.0-op24 firmware, and it works ok.
Not sure if the newer version ADG has modified the API, please use the preinstalled ADG version.
Hi,
The R&D checked the crash log part and found nothing with any exceptions related to the system processes. Seems strange.
Is this cyclical?
If possible, reset the system firmware and observe again.
1 Like
Given my previous post:
Beta 4.8.0 op24 issues - #85 by covenant
Is there a reliable way to exclude a website from the VPN?
I can include/exclude entire devices but not a website from a device with VPN active.
You need to exclude domain names, not web sites.
Unsure of difference.
eg how do I exclude:
forums.whirlpool.net.au or whirlpool.net.au
that's the same as I has done before - the input is modified to the correct format by the firmware.
Once I apply that exclusion, the entire network loses the vpn -as per my earlier post
Test with a simplified example: ipleak.net or ip.me. Note there's no sub-domain like in the forum.whirlpool.net.au. That may be enough of a difference. Then test just whirlpool.net.au.
It wouldn't surprise me if the GL firmware had a problem (read: a bug) with second level/regional TLDs or subdomains.
Same result.
Definitely a bug then.
1 Like
Good on 'ya for finding it. Post screencaps/logs, firmware ver, device model in a new thread & link back to here. That'd give a hell of a lot better chance of having it acknowledged by GL rather than just leaving it dumped & lost in the massive noise of a 'mega-thread'.
These kind of threads are idiotic. I really need to learn to stay out of them.
1 Like
This is a pretty specific thread and Bruce seems to respond here - although not to me!
Regardless it's of no help to anyone digging thru the forums with a similar problem when they have to sift thru 90+ posts to find the context just because a few key words hit in the search results.
Let's get real for a moment: have you seen how non-descript, if not outright useless, the majority of these threads are titled? Just look at this one. We know there's 'issues'. This is a support forum, FFS. That's why we're all here!
Rant over. I'm staying out of this one.
2 Likes
Great! Bye! 
Hi @bruce, the same problem exists for the MT-3000 but with AdGuardVersion 0.107.56)
So this workaround is not really a solution. Could you please look into this?
MT6000, Everything works, I did a clean installation.
The MT3000 is currently in another city, but when I arrive, I will check it out.
Which AdGuardHome version are you running?