Selfhosted

44058 readers

556 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:

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!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Tailscale has messed up my internet connection (lemmy.ml)

submitted 13 hours ago* (last edited 8 hours ago) by ludicolo@lemmy.ml to c/selfhosted@lemmy.world

37 comments fedilink hide all child comments

I have no idea why this is happening on my arch linux machine. I was trying to set it up as a client device, and now i have no internet connection on my wired network. This is bare metal not docker. I just wanted to add the device to my tailnet.

Any help is appreciated

Thank you for your time.

EDIT: I have completely uninstalled tailscale yet I still do not have internet access. I am connected to the network fine. If i cinnect through wifi it is the same result.

EDIT 2: the error I am recieving is limited connectivity.

EDIT 3: It has been fixed! scrion@lemmy.world solution fixed it!

you are viewing a single comment's thread
view the rest of the comments

[–] scrion@lemmy.world 17 points 9 hours ago* (last edited 9 hours ago) (2 children)

I don't know what your previous setup was, but given that running resolved fixes your DNS issues, run:

ln -sf ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

This will point programs that use /etc/resolved.conf during DNS resolution to the local DNS server provided by systemd-resolved.

Then, enable resolved so that it is started when you reboot:

systemctl enable systemd-resolved.service

Finally, start the service so that it is available immediately:

systemctl start systemd-resolved.service

You will want it run those with the required permissions, e. g. via sudo.

[–] Engywuck@lemm.ee 10 points 7 hours ago

"It's always DNS"

load more comments (1 replies)