this post was submitted on 09 Dec 2023
110 points (98.2% liked)

Selfhosted

40006 readers
979 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

It too me a while to work out why my Nextcloud stuff wasn't working on my phone. It wasn't until I went to http://duckdns.org on mobile data I saw the block. I had changed ISP from one with IPv6, which I had setup, to an ISP without it, and thought it might be that. But it was just coincidence.

I've written to O2 but I doubt they will change anything, so I'll be changing network.

So heads up UK O2 self hosting people!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 7 points 11 months ago (1 children)

Modern Android versions can use DoH (DNS over HTTPS) which can not be intercepted. If you don't have this option or are not sure how to configure it, you could use the Quad9 app to enable secure DNS. This way you can make sure it is not related to DNS. Frankly, I can't imagine they are blocking the IPs of the DuckDNS servers directly.

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago)

I've tried it with F-Droid's Rethink DNS already and everything is fine then.

Pretty sure they are doing DNS packet inspection. If the DNS is to duckdns (and no doubt other Dynamic DNS), then port 80 has their block page, and not sure what they are doing with 443, but it's not accepted.

Boringly, it's not being messed with right now. It's done this before. Coming and going. It's one of the things that stopped me working it out before.

Edit: I was wrong. It was just working again generally.Even with DoH DNS, I still see "Access denied" going to duckdns.org and my sites still don't work. Direct IP works. Not sure how this block is working yet.