this post was submitted on 09 Dec 2023
115 points (98.3% liked)

Selfhosted

40329 readers
404 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
[–] socphoenix@midwest.social 10 points 11 months ago (1 children)

T-mobile was doing this in the US but only blocking certain ports when talking to my home server, might try putting it on a non-standard port as well and see if you can access the service then.

[–] jabjoe 7 points 11 months ago (2 children)

Oh I know some ports are ok. My SSH and WireGuard get through. Port 80 is redirected to a block page place holder and 443 is interfered with so SSL fails.

[–] SheeEttin@lemm.ee 2 points 11 months ago (1 children)

Okay, so just run it on a different port.

[–] jabjoe 1 points 11 months ago (1 children)

Tried it. Makes no odds.

Interestingly it's fine if I use the static IP directly.

They are doing some packet inspection by the looks of it. Some rule like:

On IP address found from duckdns, mess with SSL and rewrite HTTP to go to this block page.

[–] SheeEttin@lemm.ee 1 points 11 months ago (1 children)

That is weird then. I'd change dynamic DNS providers.

[–] jabjoe 1 points 11 months ago

I don't know which other ones they have done this to. Also it's a faff to move domain now. If I'd move domain, I'd just buy one as the IP is static.

[–] droolio 2 points 11 months ago (1 children)

Wouldn't you be on CGNAT though? How are they blocking it - at the DNS level? Have you tried a CNAME record that points your own domain to the actual duckdns domain? Just curious how/why they might be doing this.

[–] jabjoe 3 points 11 months ago* (last edited 11 months ago)

I've been doing some investigating. It's not just DNS. Termux doesn't use the system DNS, it uses Google. But there is still a interference with SSL on 443 and a different page on port 80.

Edit: oh and the IP address is current with ping.