Maybe one of you hogs knows what's up.

I got a new IP address for my VPS and updated the DNS A record accordingly. That was two days ago and I still get an "unable to connect" error when trying to access TankieTube through protonVPN.

However, if I drop the VPN everything works. This is the case with both Firefox and Chrome.

Does this have to do with DNS propagation?

  • Chronicon [they/them]
    ·
    3 months ago

    2 days says to me not DNS propagation

    https://protonvpn.com/features/adblocker could be this or another one of Proton's "protection" features (okay scare quotes is a little harsh but I kinda start to roll my eyes with that type of stuff)

    • TankieTanuki [he/him]
      ·
      3 months ago

      I connect by OpenVPN instead of the app, so I don't think I'm using that feature.

      • Chronicon [they/them]
        ·
        3 months ago

        well you can rule out DNS issues by making sure it resolves properly using command line tools like dig. traceroute is hard to use on a lot of modern networks but a simple ping is still usable, or something like netcat or curl to rule out browser shenanigans

        I have actually had some weird issues like this too, where I seemingly couldn't reach hexbear from my former VPN provider at one point, but it eventually recovered, so maybe bad peering/blocking due to abuse going on from either the VPS provider or the VPN provider? But it was very annoying to troubleshoot and not that big of a deal so I don't think I ever found a smoking gun

        • TankieTanuki [he/him]
          ·
          3 months ago

          traceroute is hard to use on a lot of modern networks

          Is that why most of the hops come back as * * *?

          • Chronicon [they/them]
            ·
            3 months ago

            yeah

            the internet was not designed for NAT, and it was not designed for ICMP to be disabled lol