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.

hopsonhops

Members
  • Joined

  1. definitely still a bug in 6.8.3. All of my containers have an update option. even fresh installs or ones I just updated.
  2. Success! solution ended up being upgrade from OS 6.8.1 to 6.8.3. Theres a bug in 6.8.3 that causes all containers to constantly think they need to be updated, so I had rolled back to the previous version. Apparently 6.8.1 has this issue with routing container networks. Looks like I'm stuck with one issue or the other so I guess I'll just live with the false update notification issue.
  3. this doesn't address what I'm trying to do here. as I noted above I'm following the process in spaceinvader's video to route container traffic through a container with vpn. Jackett is just one container I would like to have set up this way. This was working previously, but now I've gone to re-do my setup and it's no longer working. One problem might be that the container thinks it has two networks, but I can't find a way to truly delete the default network, just set the drop-down to "none".
  4. EDIT: solved by updating os to 6.8.3 (which has separate issues). see below. This is probably not an issue wiht delugevpn as that container on it's own seems to work, but I's connected... I had this set up a few weeks ago and it was working, but I needed to change up a few things so I opted to tear it all down and start from scratch. (learning experience, right?) I'm following spaceinvaderone's excellent video on routing container networks through another container running VPN: https://www.youtube.com/watch?v=znSu_FuKFW0 Using binhex-delugevpn as my vpn container. that seems to be set up and working properly. I can check it's external IP and it looks like it's in Switzerland. WebUI is accessible from internal network and seems to be working. able to download a linux iso without problems. Trying to create a binhex-jackett container (have tried some others and get the same result). I can get the container to run without changing network settings, but if I change the normal network to "none" and add an extra parameters "--net=container:binhex-delugevpn" I get this: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-jackett' --net='none' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-jackett':'/config':'rw' --net=container:binhex-delugevpn 'binhex/arch-jackett' /usr/bin/docker: Error response from daemon: Container cannot be connected to network endpoints: container:binhex-delugevpn, none. See '/usr/bin/docker run --help'. The command failed. help pls

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.