Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

pihole docker fails after 7.1.2 - 192.168.122.1:53 now bound

Featured Replies

After upgrading from 7.0.1 to 7.1.1, and then 7.1.2, I discovered my pihole docker no longer starts.

It no longer starts because something is listening on port 53.

netstat shows 192.168.122.1 listening on port 53. I'm double puzzled about this because:

a) I don't know why this subnet exists now. It didn't before. Looks like something related to virbr0, but I don't know what/where virbr0 is and why it now exists

b) pihole docker looks to be binding to my host IP of 192.168.0.201. I don't follow why something listening on port 53 on 122.1 would cause a problem with a docker listening on 0.201.

Searching shows that virbr0/192.168.122.1 relates to natting on unraid. I haven't intentionally enabled natting anywhere. To all appearances this started on its own when I upgraded to 7.1.2.

Thus far I haven't found where virbr0 is defined in unraid, but it runs and ties up port 53 anyhow.

I also have a wireless wlan0 appearing in my network config that I didn't have before. It's disabled, so I don't know why it would be enabling any natting or enabling something listening on dns port 53. But this wlan0 appeared about the same time I started having this problem.

I'd appreciate any advice on how to proceed.

Thanks!

nas-diagnostics-20250522-1652.zip

Edited by CGR21
attached diags

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.