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.

Issue with Loopback definition

Featured Replies

A few of us are trying to install Minimierter on unRAID: http://minimserver.com. This is the best UPnP AV music server IMHO.

 

The initial guide to start a Docker on unRAID:

Quote

1) Create a folder to be used for building the Docker image
2) Download the file MinimServer-0.8.4.7-linux-intel.tar.gz and save it in this folder
3) Download the file Dockerfile.bin save it in this folder and rename it to Dockerfile
4) In a terminal window, change directory to this folder and run the following commands:

 

docker build -t minimserver:0.8.4.7 .
docker run -p:1900:1900/udp -p:9790:9790 -p:9791:9791 --net=host minimserver:0.8.4.7

 

 

However Minimserver was not starting and came up with this message in the log file: 

MinimServer: ohNet port 9791 is already in use

 

The root cause is the following as identified by Simon who is the Minimserver developer: "unRAID is defining the loopback adapter with two different netmask values. Here is an extract from the output of 'ip addr': 

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/32 scope host lo
       valid_lft forever preferred_lft forever
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever

The ohNet UPnP stack (used by MinimServer) can't handle this because it treats 127.0.0.1/32 and 127.0.0.1/8 as if they were separate adapters and tries to bind both of these "adapters" to different sockets listening on address 127.0.0.1 port 9791. The second of these bind attempts fails. The 127.0.0.1/8 combination is a superset of 127.0.0.1/32 and I can't see any reason why both would be needed. As a workaround, I have used the command ip addr del 127.0.0.1/32 dev lo"

 

 

My question now is if this could be fixed by the Limetech team or if there is any reason of how Limetech was defining the loopback adapter.

 

Than you very much. 

 

Latest unRAID version 6.4 defines a single subnet for ipv4 and ipv6 assignments.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever

 

  • Author

Thanks a lot @bonienl

Let‘s hope that v.6.4. is out soon. 

Archived

This topic is now archived and is closed to further replies.

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.