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.

Biff Bojangles

Members
  • Joined

  • Last visited

  1. That is super helpful. That was the one thing that always bothered me with FolderView and FolderView2, there was a disconnect with container order in unraid for autostart and the look and feel of folderview. Awesome work with keeping this alive.
  2. If I understand everything correctly now, in FolderView3 the default container order Autostart is replaced by what you see in FolderView3. For Example: Pre-Folder View - Container 1 - Container 2 - Container 3 Would start 1, 2, 3 In FolderView3 - Folder A -- Container 1 -- Container 3 - Folder B -- Container 2 Would start 1, 3, 2 Is that correct or is the Unraid Container order still setting the autostart settings? I asked because some containers need to start before others since they are dependent upon each other.. mainly databases.
  3. As a follow-up to this discussion. I have a similar issue when enabling Tailscale within the SWAG docker container and using Docker MODS. When enabling the Tailscale integration directly in the container, the container can no longer access the DNS records for lscr.io. The use case for this would be to allow subdomain access via tailscale only as the A Record resolves to a 100.x.x.x tailscale ip and also have externally facing reverse proxy. This is similiar to SpaceInvaderOnes Uncast Ultimate SWAG on Unraid walkthrough (https://www.youtube.com/watch?v=3uW97tXYWVI) It seems like it is an issue with the port that tailscale inside the docker container uses is 443. Is there a way to solve this?
  4. In either the user accounts under show more info Or in the box at the bottom of the picture you shared. In the routing box with yes, using NAT
  5. I added the following in the NAT table from your last picture: 192.168.1.0/24 and I also added some other internal 172.XX. subnets based on other dockers
  6. @jfrancais Can you access the unRAID gui by going to 172.27.224.1?
  7. I ended up doing the same thing. Kept it off the proxynet and put in the mydomain. By any chance do you also run OMBI? Having trouble utilizing .htpasswd to access it.
  8. Have you been able to figure this out. I am having the same issue with the 502 Bad Gateway. For the tutorial, I set up the proxynet network, but if I select that, I get an error for plex.

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.