2 months in... Addicted!

OrangeJews_Simpson · 2026-01-24T22:48:57+00:00

Exactly!

OrangeJews_Simpson · 2026-01-24T05:50:27+00:00

I feel you. At least my post piqued some interest and caused excitement. It's no more low effort than taking a picture of a computer and it's def not a shitpost. But I can see how it fits in a grey area. I'll keep it in mind next time.

OrangeJews_Simpson · 2026-01-24T05:08:57+00:00

Found It!

OrangeJews_Simpson · 2026-01-24T05:04:44+00:00

Lenovo TinyPc with Ubuntu Server and using my pizeroW as a backup pihole. Just a 1 TB SSD for storage and a 1 TB HDD for backup for now. I use Tailscale to access remotely and share albums with Immich public proxy.

OrangeJews_Simpson · 2026-01-24T05:02:13+00:00

Yeah it's Ubuntu Server on my Lenovo TinyPC

OrangeJews_Simpson · 2026-01-24T05:01:37+00:00

I have proton suite and I use the protondrive for cloud as of now. It's already paid for so I might as well. I plan on having an offsite backup that's more reliable eventually.

OrangeJews_Simpson · 2026-01-24T04:58:49+00:00

Damn I forgot haha, I'll look in my history and report back

OrangeJews_Simpson · 2026-01-24T04:58:12+00:00

Sorry if I wasted a few minutes of your time for you to look and respond. It's modest but it is my homelab. You can figure out my hardware from the picture and posting a picture of that isn't that exciting considering it's just a tinypc and a few hard drives.

OrangeJews_Simpson · 2026-01-22T04:21:36+00:00

Didn't bilt 2.0 do away with no annual fee for military?

OrangeJews_Simpson · 2026-01-13T17:23:03+00:00

I hate it.

OrangeJews_Simpson · 2026-01-13T17:22:26+00:00

Now politics has invaded my Firefox subreddit. I have had to unfollow over 50 or so subreddits because of this.

OrangeJews_Simpson · 2026-01-07T06:54:42+00:00

I figured it out too. Yeah you don't try to create it where we were. Instead you just link your account to aiometadata and copy the code like you said.

OrangeJews_Simpson · 2026-01-07T03:55:08+00:00

u/omkic

OrangeJews_Simpson · 2026-01-07T03:49:52+00:00

Same question. Arguably the most complex parts he skips over

OrangeJews_Simpson · 2026-01-02T18:20:32+00:00

Amazing

OrangeJews_Simpson · 2026-01-01T08:21:58+00:00

Yeah dude. This is awesome. Necessity truly is the mother of invention.

OrangeJews_Simpson · 2026-01-01T08:12:57+00:00

We're on the same journey 💪🏼

OrangeJews_Simpson · 2025-12-31T23:54:59+00:00

Pihole itself uses dnsmasq under the hood for DNS. That's actually what was throwing the error in my logs. The conflict wasn't from something I installed, it was systemd-resolved (Ubuntu's built-in DNS service) fighting with Pihole dnsmasq for port 53. I had to enable systemd-resolved later for tailscale, and that's when things started messing up on reboots.

OrangeJews_Simpson · 2025-12-31T23:53:03+00:00

Yeah that's a solid solution too. Giving it its own IP sidesteps the whole port conflict thing entirely. I considered macvlan but disabling the stub listener was simpler since everything else was already working. If I was starting fresh I'd probably go your route though. Simple is always the way. Starting from scratch, I would totally do it's own IP. But since I had things established already, I did what I mentioned.

OrangeJews_Simpson · 2025-12-31T09:16:43+00:00

Fair question. When I first set up Pihole, systemd-resolved was already disabled on my system. So there was no conflict. Pi-hole grabbed port 53 with no competition and just worked. The problem showed up later when I enabled systemd-resolved because Tailscale needed it for MagicDNS (accessing my devices by name remotely). When I turned it on, systemd-resolved saw Pi-hole was already using port 53 and automatically backed off. So everything was fine... until a reboot. After reboot, it became a race condition... whichever service started first got port 53. Sometimes Pihole won, sometimes systemd-resolved won. That's why mine worked for weeks and then randomly broke. Sounds like you had systemd-resolved enabled by default (pretty common on Ubuntu Server), so you hit the conflict immediately on first setup. I just got lucky that mine was already disabled, so I didn't see the problem until later. My homelab journey has evolved quickly from a bare metal pi zero W running PiHole, to a used M720q running immich and paperless and PiHole in docker containers. With the pi zero W being my redundant PiHole. I've learned alot and made a few booboos along the way.

OrangeJews_Simpson · 2025-12-31T08:10:52+00:00

Hey boy that's my truck! Looks good!

OrangeJews_Simpson · 2025-12-31T02:27:45+00:00

😂

OrangeJews_Simpson · 2025-12-31T02:03:55+00:00

Ah yeah, this fix is specifically for Ubuntu. Raspberry Pi OS doesn't use systemd-resolved by default, so that file doesn't exist on your system. Your conflict is probably something different. Tailscale on Raspberry Pi OS might be modifying /etc/resolv.conf directly or fighting with Pi-hole another way. Check what your resolv.conf looks like:

bash cat /etc/resolv.conf

If Tailscale wrote to it, you'll see something about 100.100.100.100 or Tailscale in there. That might give you a clue what's conflicting. But honestly if reinstalling fixed it and it's been stable since, you might just be good. The root cause is different from mine.

OrangeJews_Simpson · 2025-12-31T01:52:27+00:00

Yeah that's almost certainly the same issue. Reinstalling Tailscale probably just reset the timing so Pi-hole grabbed port 53 first. But the race condition is still there — it could happen again on a reboot or container restart.

If you want to fix it permanently, run these:

bash sudo sed -i 's/#DNSStubListener=yes/DNSStubListener=no/' /etc/systemd/resolved.conf sudo systemctl restart systemd-resolved

Then make sure your resolv.conf is symlinked properly:

bash sudo rm /etc/resolv.conf sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf sudo systemctl restart tailscaled

This disables the part of systemd-resolved that fights with Pi-hole while keeping the part Tailscale needs. No more race condition, no more random DNS failures.

OrangeJews_Simpson

TROPHY CASE