I've set up Wireguard server on Opal.
Tried to connect to it via Mango router as a Wireguard client and also via Wireguard mobile app on a phone on a different wifi network / mobile internet. Both result in no connection ("DNS_PROBE_POSSIBLE" error). Trying to solve it for >10h in total. Pls help
I have no ISP router, ethernet cabel is connected directly to Opal.
Logs (I googled them, still don’t know what to do):
Sun Oct 19 17:23:21 2025 daemon.notice netifd: Network device 'wgserver' link is down
Sun Oct 19 17:23:22 2025 daemon.notice netifd: Interface 'wgserver' is now down
Sun Oct 19 17:23:23 2025 user.notice mwan3[301]: Execute ifdown event on interface wgserver (unknown)
Sun Oct 19 17:23:24 2025 user.notice firewall: Reloading firewall due to ifdown of wgserver ()
Sun Oct 19 17:23:25 2025 user.notice relay: Reloading relay due to ifdown of wgserver ()
Sun Oct 19 17:24:43 2025 daemon.notice netifd: Interface 'wgserver' is setting up now
Sun Oct 19 17:24:44 2025 daemon.notice netifd: Interface 'wgserver' is now up
Sun Oct 19 17:24:44 2025 daemon.notice netifd: Network device 'wgserver' link is up
Sun Oct 19 17:24:45 2025 user.notice mwan3[4170]: Execute ifup event on interface wgserver (wgserver)
Sun Oct 19 17:24:45 2025 user.notice mwan3[4170]: Starting tracker on interface wgserver (wgserver)
Sun Oct 19 17:24:49 2025 user.notice firewall: Reloading firewall due to ifup of wgserver (wgserver)
Sun Oct 19 17:24:50 2025 user.notice relay: Reloading relay due to ifup of wgserver (wgserver)
Sun Oct 19 18:14:32 2025 daemon.notice netifd: wgclient (18225): [!] Section lan2wgserver option 'dest' specifies invalid value 'wgserver'
Sun Oct 19 18:14:32 2025 daemon.notice netifd: wgclient (18225): [!] Section lan2wgserver skipped due to invalid options
Sun Oct 19 18:14:32 2025 daemon.notice netifd: wgclient (18225): [!] Section @redirect[0] (GL-Opal) internal rewrite IP cannot be determined, disabling reflection
Sun Oct 19 18:14:32 2025 daemon.notice netifd: wgclient (18225): [!] Section nat6 option 'reload' is not supported by fw4
Sun Oct 19 18:14:32 2025 daemon.notice netifd: wgclient (18225): [!] Section gls2s option 'reload' is not supported by fw4
Sun Oct 19 18:14:32 2025 daemon.notice netifd: wgclient (18225): [!] Section gls2s specifies unreachable path '/var/etc/gls2s.include', ignoring section
Sun Oct 19 18:14:32 2025 daemon.notice netifd: wgclient (18225): [!] Section glblock option 'reload' is not supported by fw4
Sun Oct 19 18:14:32 2025 daemon.notice netifd: wgclient (18225): [!] Section vpn_server_policy option 'reload' is not supported by fw4
Sun Oct 19 18:14:32 2025 daemon.notice netifd: wgclient (18225): [!] Automatically including '/usr/share/nftables.d/chain-pre/mangle_output/01-process_mark.nft'
Sun Oct 19 18:14:32 2025 daemon.notice netifd: wgclient (18225): [!] Automatically including '/usr/share/nftables.d/chain-post/mangle_output/out_conn_mark_restore.nft'
Sun Oct 19 18:14:33 2025 daemon.notice netifd: wgclient (18225): DROP all opt -- in * out * 0.0.0.0/0 -> 0.0.0.0/0 match-set GL_MAC_BLOCK src
Sun Oct 19 18:14:33 2025 daemon.notice netifd: wgclient (18225): Failed to parse json data: unexpected character
Sun Oct 19 18:14:33 2025 daemon.notice netifd: wgclient (18225): uci: Entry not found
Sun Oct 19 18:14:33 2025 daemon.notice netifd: wgclient (18225): cat: can't open '/tmp/run/wg_resolved_ip': No such file or directory
Sun Oct 19 18:14:33 2025 daemon.notice netifd: Interface 'wgclient' is now down
Sun Oct 19 18:14:33 2025 daemon.notice netifd: Interface 'wgclient' is setting up now
Sun Oct 19 18:14:36 2025 user.notice mwan3[18409]: Execute ifdown event on interface wgclient (unknown)
Sun Oct 19 18:14:40 2025 daemon.notice netifd: Interface 'wgclient' is now down
Sun Oct 19 18:14:41 2025 user.notice firewall: Reloading firewall due to ifdown of wgclient ()
Sun Oct 19 18:15:00 2025 daemon.notice netifd: Interface 'wgclient' is setting up now
If both the Mango and the WireGuard mobile app on your phone show “Connected,” the issue is likely not with the VPN connection itself.
Based on the DNS_PROBE_POSSIBLE error, this may be DNS-related.
Please open CMD or Terminal on a LAN device connected to the Mango with VPN connected and run the following commands for further troubleshooting:
nslookup google.com
# For Windows CMD
tracert 64.6.64.6
# For macOS/Linux
traceroute 64.6.64.6
Maybe it is the ddns, you said you have no NAT, that makes little no sense to me.
You have a ethernet cable connected on wan, where does that come from?, a media converter to a ipon connection/isra or coax?
If you try a tracert without the vpn, do you see a upstream local ip? (Use table Private network - Wikipedia under private ipv4 addresses to identify those).
If there is one, you are still behind a nat, because incomming traffic doesn't know about the route back to your wgserver, portforwarding still needs to be required.
Then does the domain not work, it might only opened registered access to the web ui of this other router (if it was set in bridge mode).
If you see a 100.x.x.x ip you might be on a cgnat (multiple isp users behind a single public ip), you will see this also reflect on the luci wan interface, then you need to use alternatives like tailscale.
Based on these results, it appears Mango is not connected to the VPN server.
First, please check whether your home network ISP provides a public IP address.
If possible, please share some screenshots (may blur the latter part of the public IP address).
If confirm a public IP address is available and Opal has correctly obtained it or the main router has properly configured port forwarding, please connect both Opal and Mango to GoodCloud and share them with us as follow guide.
So that we can have a remote check. Technical Support via GoodCloud - GL.iNet Router Docs 4