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?
It could be propagation, and it could also be the VPN itself being blacklisted - I don’t think it’s uncommon for commercial hosting services to blacklist VPN subnet blocks depending on the reputation of the VPN.
Could maybe try a traceroute from the VPS to your VPN IP
Traceroute can’t reach my VPN endpoint but neither can it reach my bare home IP because I’m behind a CGNAT.
I didn’t change hosting providers with my IP; they moved me to an IP block with a “cleaner” reputation at my request. Would the provider block a VPN from some of its subnets but not others?
It’s possible, it’s also possible that you got IP blocked temporarily for suspicious behavior but that would entirely depend on how your provider works
I just opened a ticket. We’ll see what they say.
Would it be unusual for a VPN provider to block access to subnets? That’s not how things work, right?
