this post was submitted on 11 Mar 2025
6 points (100.0% liked)

Selfhosted

46452 readers
348 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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
[–] infinitejones@sh.itjust.works 1 points 1 month ago

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...?