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.

Unraid / Docker / Networking issue: Unable to reach containers with custom IP configuration

Featured Replies

I have been running a home server for years on Windows and my friend finally got me on board with Unraid / Docker when I recently upgraded hardware, however I am having multiple networking issues after migrating my applications, and I'm confident I'm doing something wrong. I have been working for weeks on trying to figure out my problem and not sure what it is.

 

Because I need the ability to utilize Intel ARC GPU for Plex transcoding, I am running 7.0.0-rc1. 

 

My friend told me to create a proxynet (primarily for Swag) and just use an available port on the host IP for anything I want to run in Docker, then call it up by the Unraid host IP and whatever port I selected. That works great for containers that I want to access internally, but I have a couple of things that I want to set specific IP's for (like PiHole and an Apache) to make it easy to map things externally.

 

Example: My network is 10.0.1.XXX. Unraid is running 10.0.1.12. I have several things running successfully on 10.0.1.12 utilizing their specific ports for sonarr, radarr, etc. etc. I can hit them both locally via the WebUI (internal IP / port) as well as thru Swag externally. I have PiHole running on its own IP, 10.0.1.9. It's running, no errors in the log (attached). I am unable to ping the container locally, nor am I able to hit 10.0.1.9/admin internally.

 

Things I've tried:

1. Different IP

2. Different Port

3. Removing and redeploying the container

4. Confirmed I can hit it locally utilizing the host IP 

 

I also have an Apache server running as well with its own IP and having the same symptom. This has to be something missing that I don't fully understand. Because I'm using IP addresses instead of URL's, I'm ruling out DNS as an issue. I've tried disabling PiHole but there's no difference in symptoms utilizing my ISP's DNS servers.

 

I'd appreciate any advice anyone could offer. Once I get beyond this, other than other strange SMB share issues I still can't figure out, I should be good.

PiHole Log.rtf

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.