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.

dan91

Members
  • Joined

  • Last visited

  1. Hi, I think this is already enabled? The log is in the diagnostics as syslog-previous.txt. Thanks, Dan
  2. dan91 started following Occasional Lockups
  3. Hi, I'm having occasional Unraid lock ups. When it happened even pressing enter on the keyboard connected to the server does not seem to register. (Normally it keeps asking for username if you press enter) I have to hard power cycle the server to get it to come back. I've checked that docker is already using ipvlan (as i do use static ip's) i'm not sure where else to look? Sometimes it can go a month or more without happening. CPU is a i9 - 10900 so don't think any of the ryzen issues apply and it doesnt look like its affected by the intel degradation issues some CPU's are having. Thanks, Dan tower-diagnostics-20250612-0757.zip
  4. Hi, It seems that the anonamise doesnt work as expected. Its not removing LOCAL_TLD from ident.cfg so if people are using custom hostnames/dns they could be exposed. Its also not removing IPv6 addresses. So again if people are using routable IPv6 address they are potentialy being exposed. This is in network.cfg and in logs syslog ext. Thanks, Daniel
  5. Hi, Upgraded from 6.12.3 and having issues with my dockers using custom ipv6 addresses. I'm getting this error: docker: Error response from daemon: user specified IP address is supported only when connecting to networks with user configured subnets. These are the settings which worked fine on 16.12.3: docker run -d --name='binhex-sabnzbd' --net='br0' --ip='192.168.93.193' --ip6='2a02:restofip' -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="tower" -e HOST_CONTAINERNAME="binhex-sabnzbd" -e 'TCP_PORT_8080'='8080' -e 'TCP_PORT_8090'='9090' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/sabnzbd-icon.png' -v '/mnt/disks/WDC_1TB_BLACK/Sab':'/land':'rw,slave' -v '/mnt/cache/appdata/sab/':'/config':'rw' 'binhex/arch-sabnzbd:latest' 366a3580aae5540d218ef2281456d083994bf8f7998a1cb51b05e378cd705ad6 docker: Error response from daemon: user specified IP address is supported only when connecting to networks with user configured subnets. Am I missing something? Going to have to roll back for now. If i remove the specified IPv6 Address it works fine. Please let me know where to send diagnostics don't want to post them publicly. Thanks, Daniel
  6. Hi, Upgraded from 6.12.3 and having issues with my dockers using custom ipv6 addresses. I'm getting this error: docker: Error response from daemon: user specified IP address is supported only when connecting to networks with user configured subnets. These are the settings which worked fine on 16.12.3: docker run -d --name='binhex-sabnzbd' --net='br0' --ip='192.168.93.193' --ip6='2a02:restofip' -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="tower" -e HOST_CONTAINERNAME="binhex-sabnzbd" -e 'TCP_PORT_8080'='8080' -e 'TCP_PORT_8090'='9090' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/sabnzbd-icon.png' -v '/mnt/disks/WDC_1TB_BLACK/Sab':'/land':'rw,slave' -v '/mnt/cache/appdata/sab/':'/config':'rw' 'binhex/arch-sabnzbd:latest' 366a3580aae5540d218ef2281456d083994bf8f7998a1cb51b05e378cd705ad6 docker: Error response from daemon: user specified IP address is supported only when connecting to networks with user configured subnets. Am I missing something? Going to have to roll back for now. If i remove the specified IPv6 Address it works fine. Thanks, Daniel
  7. Hi Xploit with a single IP for blizzard i get about 1-3 MB/s on initial download with the amount of IP's from my initial post I mostly max out my download speed 8MB/s. If you remove all the extra IP's and just try 1 extra IP does your cache still work? (basically are the extra IP's functioning correctly) Can you see them in ip addr on the command prompt on unraid and are you using HOST mode for the docker container? Are you downloading to spinning disks or an SSD? If spinning are you able to swap to an SSD just for testing the blizzard download? You may be hitting a limitation on disk access times which may be why increasing your slice size helped. (How you get more througput from one large file than loads of small ones)
  8. I have managed to do this but you have to make a few changes to the setup. I use "Host" for the network setting for the docker container rather than giving it its own IP in Bridge mode. This ensures all IP's on your unraid box adapder pass through to it. Downside you cant have 80 443 or 53 listening on these. This mainly effects the unraid web ui which runs on 443 by default. To get round this move the web gui to another port (i used 444) this does mean to access the webui you will need to specify the port e.g. sdjklfhsdjfgh76786sdwe87r5sdf.unraid.net:444 Settings -> Identification -> Management Access to change port First step is to assign more IP address' to the unraid network adapter. You need to check on your router for its DHCP range and assign something outside of this range (which is not in use) or put a manual reservation in to a dummy mac address for the IP's your looking to use. (Sorry cant really help more with this so many different types of routers). For example my DHCP range runs 192.168.1.2 - 192.168.1.190 192.168.93.5 is assiged to my Unraid box as a manual reservation so its alway the same. I have decided to use 192.168.1.242 - 192.168.1.248 as the additional IP's as they are outside the DHCP range (so wont be given to something else and I know they are not in use) Now we have the list of IP's we are going to use we need to assign them to the interface. To ensure this percists through a reboot of the unraid box we need to install the User Scripts plugin made by Andrew Zawadzki (Search in the apps store) Once added go to Settings > User scripts (at the bottom under user utilities) New Script and give it a name i picked IPAddresses Click on the Cog next to the script you just made and go edit script Then in my example i entered the following into the script box; #!/bin/bash ip address add 192.168.1.243/24 dev br0 ip address add 192.168.1.244/24 dev br0 ip address add 192.168.1.245/24 dev br0 ip address add 192.168.1.246/24 dev br0 ip address add 192.168.1.247/24 dev br0 ip address add 192.168.1.248/24 dev br0 Note i left out the 192.168.1.5 as it will already be assigned automatically. Your br0 (network adapter) might be different run "ip addr" in the command prompt shell on the server and look for the network adapter that has IP address' that match your local network. Save the script Change the Schedule to First Array start (we only need to apply it once per reboot) and apply the changes. You can also manually run the script to add the ip addreses right now which you will need to do this first time (or reboot). running "ip addr" in the shell prompt should now show all these IP's also linked to that network adaper (this is important!) And you should be able to ping them from your pc! Now we need to tell the dns server in the docker container about these ip addresses. Edit LAN Cache bundle docker settings Ensure network type is Host (this will fail if you didnt move your Mangement port!) First lets just do a test and remove the IP currently in LANCACHE_IP to one of the new ones e.g. for me 192.168.1.243 Flush your dns on your PC to make sure Command prompt "ipconfig /flushdns" and then "nslookup update1.dota2.wmsj.cn" this is just an example address that should be overwritten by the steamcache dns we should get that IP address we changed too. Test your cache and make sure it sill working. If so lets put all the addresses in. Edit lancache bundle again For lancache IP put in all the IP addresses seperated by a space e.g; so i entered them all 192.168.1.5 192.168.1.243 192.168.1.244 192.168.1.245 192.168.1.246 192.168.1.247 192.168.1.248 You can leave DNS_BIND as the single IP Apply the changes. Command prompt "ipconfig /flushdns" and then On the PC in a command prompt run "nslookup update1.dota2.wmsj.cn" this is just an example address that should be overwritten by the steamcache dns. You should get a result including all your extra IP's. Make sure everything is working. Using this i get 100MB/s - 115MB/s which seems to be the limit of my Gigabit connection between unraid and my pc. When downloading ARMA 2 as an example. (I'm using spinning disks for the cache so they are likely the next limit)

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.