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 upgrade issues 6.8.0 --> 7.0.1 --> 7.1.4

Featured Replies

Hello guys,

I have had Unraid version 6.8.0 hosted on Supermicro X9DR3-F Version 0123456789 running very stable without any issues since 2019.

Couple of days back, I've noticed I couldn't pull up binhex-delugevpn docker container in UI.

So, I thought of upgrading to latest stable version. So, as part of upgrade process, I've upgraded all the plugins and docker container whatever they could upgrade. Since not all of them were backwards compatible with 6.8.0 version.

The default version presented by Unraid to upgrade to was 7.0.1 -which I did.

After the upgrade, I've noticed the following issues:

1) The fans are running super high with lot of noise. It's really loud.

2) binhex-sabnzbdvpn is the only container that did not start. It's logs also doesn't show anything. Currently it's stopped.

3) None of the containers give the option to show 'open ui' when I click on them. All of them show that they are running.
I can't even click on the containers where it shows all the configurations of each container like port mapping, shares etc....

In the process of debugging/triaging, I've read that it's better to upgrade to the latest stable version of Unraid, which I did.

Now I'm on 7.1.4. But the above three issues still persist.

Please see the attached pictures.

All the container are working when I directly go to the web urls -

Plex: http://192.168.1.245:32400/web/index.html#!/

Krusader: http://192.168.1.245:6080/vnc.html

Radar: http://192.168.1.245:7878/

4) except Deluge: http://192.168.1.245:8112/ and ofcourse sabnzbdvpn is down.

I'm attaching some screen shots and logs of the containers. (sabnzbdvpn doesn't even show anything in it's log).

Can you please advise me on what could be wrong and how to fix these four issues?

Thanks in advance!

dashboard-1.JPG

dockerContainers.JPG

fans_running_veryLoud.JPG

FixCommonProblems.JPG

FixCommonProblems-2.JPG

Edited by KevinImf

  • Author

Hi guys,

I want to provide an update. I have searched few forums and decided to backup and reinstall the docker image and reinstall all the containers.

Looks like OpenVPN is deprecated and I have installed WireGuard-Docker in it's place.

I've re-installed deluge first and later sabnzbdvpn containers., sabnzbdvpn failed and the log states
"Bind for 0.0.0.0:9118 failed: port is already allocated."

When I checked deluge configuration, it's using this for microsocks.

Container Port: 9118
This is the port for microsocks application - Socks5 proxy server.

How do I resolve this conflict / sharing of 9118 port between deluge and sabnzbdvpn.
I've attached the log and the docker allocation of ports

Thank you!

sabnzbdvpn_failure_log.txt

dockerAllocations_ports.JPG

Edited by KevinImf

  • Author

Guys, I want to provide an update:

After I reinstalled all the containers, everything is working fine except the deluge (with wireguard vpn) and sabnzbdvpn(it doesn't even install because of port binding issue)
I'm focusing on fixing deluge first -
The UI comes up fine, but when I add torrents, it doesn't download even a bit.
I suspect it might be incorrect configuration with ports or keys of wireguard vpn.

I followed all the steps as is in this video (https://www.youtube.com/watch?v=uAt_M_aCvLs&t=189s) to install wireguard and configure deluge, but the downloads still wont' work.

Can you let what I might be missing?

I've attached screenshots of Router Port fowarding, deluge and wireguard configs.

deluge_config_1.JPG

deluge_config_2.JPG

Router_port_Forwarding.jpeg

wireguard_config.JPG

deluge_log_071425.txt

Edited by KevinImf

  • Author

All - the issues are resolved now.

When I upgraded unraid, looks like the change the share/mount name of my Unassigned drives.
Per binhex's suggestion, I've reversering the mount /share name back to the previous one, fixed the deluge issue.
Also, assigned a different port to sabnbzd and it's also working fine now.

Thank you all!

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.