Hi - I followed this guide exactly: https://openwrt.org/docs/guide-user/services/vpn/openvpn/server
But when I tested the VPN, I can ping websites successfully but no web pages ever load. Traceroute works, the websites just never load:
PING google.com (142.250.176.14): 56 data bytes
64 bytes from 142.250.176.14: icmp_seq=0 ttl=118 time=322.881 ms
64 bytes from 142.250.176.14: icmp_seq=1 ttl=118 time=248.069 ms
64 bytes from 142.250.176.14: icmp_seq=2 ttl=118 time=369.009 ms
Some changes I did to troubleshoot:
push "dhcp-option DNS ${VPN_DNS}" from 192.168.9.0 to 192.168.0.1 (my router), which didn't fix it.
2023-11-26 13:08:10.949021 *Tunnelblick: DNS address 192.168.0.1 is being routed through the VPN
2023-11-26 13:08:53.315325 *Tunnelblick: After 30.0 seconds, gave up trying to fetch IP address information using the ipInfo host's name after connecting.
2023-11-26 13:09:32.021800 *Tunnelblick: An error occurred fetching IP address information using the ipInfo host's IP address after connecting
Warnings/Errors in client:
Warning: Tunnelblick is using 'openvpn-down-root.so', so the route-pre-down script will not be used. You can override this by providing a custom route-pre-down script (which may be a copy of Tunnelblick's standard route-pre-down script) in a Tunnelblick VPN Configuration. However, that script will not be executed as root unless the 'user' and 'group' options are removed from the OpenVPN configuration file. If the 'user' and 'group' options are removed, then you don't need to use a custom route-pre-down script.
AEAD Decrypt error: bad packet ID (may be a replay): [ #125 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Not sure if this issue is related: Openvpn route-up and route-pre-down broken in 23.05 - #20 by thekiefs