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
I've had similar problems in the past - apparently no internet connection, and both times I narrowed it down to the machine being unable to resolve domain names.
Turns out Tailscale had changed the IP address for the machines' DNS resolution in resolv.conf to 100.100.100.100
That's fine when the machine is connected to Tailscale but not when it isn't!
Reverting the DNS IP back to whatever it was previously, or to something like 1.1.1.1 solved the problem for me, at least to the extent that it could resolve URLs again.
Worth a look, if only to rule it out...?
I try to nano into my resolv.conf but it appears to only be a symbolic link file. I apologize for my ignorance but is there any other way to revert my dns back?
EDIT: the symbolic link leads to a directory that does not exist:
/run/systemd/resolve/stub-resolv.conf
Does
ping 1.1.1.1
work?Yes it does