this post was submitted on 11 Mar 2025
45 points (86.9% liked)

Selfhosted

60177 readers
590 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

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

Questions? DM the mods!

founded 3 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
[–] SuperUserDO@sh.itjust.works 1 points 1 year ago (1 children)

Let us know the following

If ping works for: localhost, your gateway, 1.1.1.1, google.com.

The contents of your /etc/resolve.conf

If you have a tun0 interface (ifconfig or ip a)

You said you uninstalled tailscale. Are there any running process or active systemd units laying around?

[–] ludicolo@lemmy.ml 1 points 1 year ago* (last edited 1 year ago) (1 children)

So I was able to get it working again by doing this solution that badlotus suggested. I did not delete the file because it was already gone after the first timw I attempted this. If I reboot my device however the issue comes back. If I run the command again my internet is back.

Badlotus' solution:

"Have you tried deleting /etc/systemd/resolved.conf and restarting the service with systemctl restart systemd-resolved?"

[–] SuperUserDO@sh.itjust.works 1 points 1 year ago* (last edited 1 year ago)

Good that it's working (kinda).

So it sounds like your DNS resolver is botched. Id dig into the doc on how systemd-resolverd should look and see if you can't rectify what went wrong (the arch wiki should have examples of what a default config looks like).

I don't remember if arch uses cloud init configs but it being reset at boot feels like a cloud init config problem.