technology

23115 readers

228 users here now

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.

founded 4 years ago

MODERATORS

[email protected]

Changed my server's IP and now I can't access my website over VPN (hexbear.net)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

16 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 2 months ago (1 children)

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

[–] [email protected] 6 points 2 months ago* (last edited 2 months ago) (1 children)

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

[–] [email protected] 3 points 2 months ago (1 children)

traceroute is hard to use on a lot of modern networks

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

[–] [email protected] 4 points 2 months ago

yeah

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