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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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
it's a gl.inet brume2 running openwrt, I SSH into it and can ping outwards to anything and my speed test from the CLI tells me i have 900Mbit available
Ah, gotcha, cool. If it's OpenWrt and you have shell access, that should make it easier to diagnose. When you are checking that you don't have connectivity from your local LAN device, you tried pinging the same out-there-on-the-Internet host, and that failed?
Yes I use the same destination fro testing on my laptop and the router.
I think I've narrowed it down to a DNS issue, I just don't know exactly what. I can ping outwards from my laptop when using IPs but not names. But my laptop can reach my DNS.
For whatever reason ISPs tend (at least in here) to be pretty bad at keeping their DNS services up and running and that could cause issues you're having. Easy test is to switch your laptop DNS servers to cloudflare (1.1.1.1, 1.0.0.1) or opendns (208.67.222.222, 208.67.220.220) and see if the problem goes away. Or even faster by doing single queries from terminal, like 'dig a google.com @1.1.1.1'.
If that helps you can change your router WAN DNS server to something than what operator offers you via DHCP. I personally use opendns servers, but cloudflare or google (8.8.8.8, 8.8.4.4) are common pretty decent choices too.
Try
nslookup testdomain.comfrom your laptop (this uses your router DNS by default)Then try
nslookup testdomain.com <your-router-ip>from your laptop (this forces using your router DNS)Then try
nslookup testdomain.com 1.1.1.1from your laptopThen repeat all 3, but on your router. Just to see where the problem is exactly