Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
If it's just a DNS block, you could use a different DNS server. You should do this anyway in my opinion.
It's not the DNS server. I'm sure of this because Termux uses a different DNS server but does the same. I also tried setting my phone to use OpenDNS directly. I'm pretty sure they are inspecting the DNS traffic. Exactly so changing DNS server doesn't help.
I don't see a problem when using IP directly. I mean the IP is static, so I could must buy a domain, but I'd also have to piss about with my setup.
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.
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.