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.

docker containers with tailscale after upgrading to Unraid to 7.1.2

Featured Replies

I am having a few issues with some of my docker containers after upgrading unraid from 7.0.1 to 7.1.2. and am looking for help.

 

Things that were broken but are now fixed:

I have both sabnzbd and qbittorrentvpn installed. both want to use port 8080 so I moved sabnzbd to port 8081, that worked fine before the upgrade but would not load the web interface after the upgrade. I found I had to change the WebUI to http://[IP]:[PORT:8081] in the advanced setting not just in the docker container port type variable. It did work before, but not after until the change in the advance setting.

 

This was 1/2 of the problem with the qbittorrentvpn problem. that container would still not load the web interface if the VPN was turned on. the only way I could fix that was to delete the VPN configuration and reconfigure it. After thatthe webUI would load fine with the VPN enabled.  

 

Now to the 2 containers I have not fully fixed yet:

both audiobookshelf and komga have tailscale installed so they can be accessed outside my network but only by devices on my tail net. This all works fine. I can still access them both inside my network and out via the taiscale url. But I can no longer access those 2 containers via the internal webUI link that is the {unraidserverIP}:{container port}.

 

All docker containers that do not have tailscale install still work from the internalIP:port but the 2 ones using tailscale will not. 

 

I can access the containers so it is not a critical issue but something changed as I was able to access it that way before the update. I always get concerned when there is a change to the server that I do not understand so I would like to restore the internal connection or at least understand why it stopped working.

 

thanks for any help,

Andrew

 

  • Author

I have installed another container that I use tailscales with, calibre-web. It is behaving the same way. I can access it via the tailscaleIP:Port or thr tailscale url,  but not the unraid provided webui links which is serverIP:port. 

All the docker containers that do not use tailscale work with the webui link.

This started after I upgrades unraid to 7.1.2. So not sure if it a tailscale support issue or upgrade support but it would be great to figure out what changed so I am not surprised down the road when/if some other function is disrupted. 

 

Thanks for any help

Andrew

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.