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...?
resolv.conf is usually set by systemd network manager. You should change the setting in /etc/systemd/... (Idk I forgot the full path)
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
What's the output of
systemctl status systemd-resolved○ systemd-resolved.service - Network Name Resolution Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; preset: enabled) Active: inactive (dead) Docs: man:systemd-resolved.service(8) man:org.freedesktop.resolve1(5) https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS https://systemd.io/WRITING_RESOLVER_CLIENTS
Have you tried deleting
/etc/systemd/resolved.confand restarting the service withsystemctl restart systemd-resolved?Ok wtf. I retried this solution and it worked for some reason. I have no idea what happened differently. I didn't delete the file because it was already gone.
However if I restart it breaks again.
I found an informative post about a related issue that might be of some use to you. Sounds like DHCP or Network Manager may be rewriting your systems-resolved.conf.
https://joshrnoll.com/my-tailscale-dns-woes/
That did not work, I deleted the file and then I restarted the service. I then restarted the pc just to make sure. Still no internet access and still same limited connectivity error.
What's the config file look like?
https://wiki.archlinux.org/title/Systemd-resolved
None of those config files exist in that folder location.
Does
ping 1.1.1.1work?Yes it does