GL.iNet Router Connects to WireGuard VPN but Has No Internet Access (Debian Server with Pi-hole DNS)

I’ve set up a WireGuard VPN server on a rented virtual server running Debian. The configuration is as follows: - List item - Server OS: Debian (12) - VPN: WireGuard - DNS: Pi-hole running on the same server, configured as the DNS for VPN clients - Domain: I’ve registered vpn.myname.com and pointed it to my server’s IP Clients: -iPhone phone -Windows PC -GL.iNet travel router (e.g., Slate, Mango, etc.) When I connect from my phone or Windows PC using the WireGuard configuration, everything works as expected: VPN connection is successful -All traffic is routed through the VPN -whatismyip.com shows the server’s IP DNS resolution works (via Pi-hole) However, when I import the same .conf into my GL.iNet router (which uses the WireGuard client), the VPN tunnel shows as connected, but there’s no internet access on devices connected to the router. The router itself doesn’t appear to be routing traffic through the VPN correctly. Things I’ve checked: - The same config works perfectly on other devices - The router shows "Connected" in the WireGuard status - DNS seems to be set correctly to Pi-hole (same as other clients) - AllowedIPs is set to 0.0.0.0/0, ::/0 - IP forwarding and masquerading are enabled on the server What I’m looking for: Any ideas why the GL.iNet router establishes a WireGuard connection but cannot access the internet, even though other devices work fine with the same config? Are there special considerations for WireGuard on GL.iNet routers? Any help is appreciated!