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.

Mattaton

Members
  • Joined

  • Last visited

Everything posted by Mattaton

  1. I can't figure out why, but this isn't working for me. Still looks the same. When I inspect the elements, the styles are there, but the float is having no effect. Weird.
  2. You rock! Great additions!
  3. I have an Intel NUC running unRAID with only one drive currently (no, this is definitely not my main server). To add parity, I want to replace the current 250GB with two 500GB drives. The NUC only has two M.2 slots, so I can't have all three drives installed together. What is the best way to do this? If I add in one drive as parity, let it build, then replace the original drive with the second new drive, will parity rebuild the data to the new drive? I have backups of all data on the drive, so I'm not worried about losing anything. Just looking for the most painless, best-practice way of swapping the drives. Thanks! Matt
  4. That's how I found out about Folder View, when moving from 6.11 to 6.12 I got a message that Docker Folders is no longer under development and it suggested Folder View. Luckily, we have @scolcipitato to help us out with our need for organization. 🙂 Depending on how complex your folder setup is, it's not bad redoing it for Folder View.
  5. No worries! Bigger fish to fry! 🙂
  6. Outer wrapper wouldn't be a block element. So it wouldn't clear the elements beside it. It'd just be something used to group the folder element with its container children. The wrapper around the children would be display:none and then display:block when expanded. Which would allow it to look more like @Linguafoeda showed.
  7. I added this to the custom CSS and it hid the "Started" "Stopped" for the dockers. #docker_view .folder-element-docker .state { display: none; }
  8. I must not be understanding how the editing of the CSS works. I am in the FolderView settings, I created a CSS file and imported it with the Import Dashboard button, but it wasn't having any affect on the dashboard. So I exported dashboard, and it's blank. Which leads me to think the CSS I imported wasn't actually imported. What am I doing wrong? 😄 NEVERMIND...I just did it via the file manager and directly edited the dashboard-custom.css.
  9. You could just hide the .state class.
  10. Can a wrapper element be added around the children container elements? Knowing nothing about how this plugin was assembled, how much control do you have over the elements that are generated here? If you can put a wrapper around each folder and its container children, and then a wrapper around just the children, we'd have a lot more to play with using CSS. The display: block you're adding to the .folder-docker element is pushing the children down to the next row but not really grouping them. If all the folders weren't all expanded, the next folder element would be right inline with the previous container element. This wouldn't be too difficult if you have any control over the html elements spit out in this area.
  11. Check this comment and the next 6 after it. Talked about this exact thing. 🙂 In short, yes, it's the order of the containers without the folders as long as you moved at least one thing after the last folder was created.
  12. Drag and drop, like @scolcipitatosaid, but you do have to unlock the ordering first in unRAID v6.12. Red lock in the upper right corner. Then relock (green lock) after dragging to set it.
  13. I just checked the userprefs.cfg file and it does look to reflect the order on the Docker screen. It includes lines for the folders themselves, so it's all stored there.
  14. Got it. Yeah, after any creation of folder or change in container order within a folder, you have to change the order of something on the main Docker screen in order to trigger unRAID to reset the start order. So, even if you move a folder and then put it back where it was, that will trigger the unRAID reorder to match the order of the folders/container you see on the screen. Good to know! Thanks!
  15. Yeah, it is a little confusing. I think an example may be best to illustrate: Three folders: A, B, and C. Folder A holds containers: 1 2 3 B holds 4 5 6 C holds 7 8 9 If the order of the folders in the container list is C, A, B, do the containers start in this order: 7 8 9 1 2 3 4 5 6? And, if I reorder the containers inside of B to 6 4 5, does that change the start order for those containers, or is it just visual and we eventually/potentially have no way to know the actual start order?
  16. Hmmm...so you're saying the order we set under the folder options has no bearing on the start order? I always thought that the order in the Docker screen was still the start order, you just had to make sure you ordered the folders in a way that put dependency containers ahead of other containers. But still, if all folders are toggled "open" then the order you see there is the start order. Is that wrong? Is the only way to affect start order is with all containers OUT of the folders? We must sort them for start order, then add them to folders? And we can't affect start order at all once they're in folders? If that's the case, could you add a quick on/off button for folders? Turn them off, the default view is back, we can then affect start order, then turn the folder view back on and we get our visual sort, unaffected by start order. Or maybe an alternate settings screen that just shows all the containers in their start order where we can rearrange them without all the other clutter? Similar to the list of containers inside the folder settings screen, but just for start order. I may be oversimplifying, but I'm hoping this is a relatively simple thing to do. Thanks!
  17. Maybe same issue others were having that an update seemed to fix for them. I just installed Folder View, so I'm on the latest version. I finally finished up all my folder organizing, saved my changes to a folder and went back to main Docker window to find three of the folders I made permanently expanded with no heading. The containers just appear in a list as usual (without folder view), but when I go to create a new folder or edit an existing one, those containers aren't in the list since they are already assigned to a folder I just can't see. Thanks! ---EDIT-- I stopped one of the containers and that refreshed the page and the folders were back. Although I had refreshed the page, gone to other pages, and even closed the browser and reopened and none of that brought the folders back. Go figure.
  18. I guess that's what I did, in effect. Though your way would have been simpler. I did a new config and just assigned all the disks back to the same positions. Seems to have worked, though the parity had to be re-synced with this method. Thanks!
  19. I replaced my cache drives a month ago. Everything was fine. Today we had a power outage, so I had to shut the server down. It's on battery backup, so no big deal. Bringing it back up this evening, the array didn't autostart and the cache drives are saying they're wrong and being emulated (when the array is started). It's showing the serials for the OLD cache drives as missing and showing the new cache drives as the selected, but wrong drives. Starting the array, as mentioned, says it's being emulated. But these drives have been in use for a month without this issue. What do I do? Thanks!
  20. Yes, it's a reverse proxy setup. Everything seems to work fine, I just noticed the error with My Servers. Thanks!
  21. Where do I go to update ALLOWED_ORIGINS? I'm getting a CORS error saying the url I'm using to access my server is violating policy since it isn't in the ALLOWED_ORIGINS list. Thanks!
  22. I need some help with getting my unifi-controller container accessible via swag. I think because the unifi-controller webui uses https without a cert, then nginx can't resolve it and I get a 502 error from Cloudflare. From my nginx unifi conf file: include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app 192.168.75.13; set $upstream_port 8443; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; I've tried changing the $upstream_port to just 443. The container has port 8443 set as the webui port. This is definitely the url for accessing the webui locally: https://192.168.75.13:8443/ Swag is on my proxy network, and the unifi-controller container is on br0 with a specified IP. The nginx error logs say: 2023/01/02 15:49:42 [error] 1943#1943: *15046 connect() failed (113: Host is unreachable) while connecting to upstream, client: -publicIP-, server: unifi.*, request: "GET / HTTP/1.1", upstream: "http://192.168.75.13:8443/", host: "unifi.domain.com" 2023/01/02 15:49:45 [error] 1943#1943: *15046 connect() failed (113: Host is unreachable) while connecting to upstream, client: -publicIP-, server: unifi.*, request: "GET /favicon.ico HTTP/1.1", upstream: "http://192.168.75.13:8443/favicon.ico", host: "unifi.domain.com", referrer: "https://unifi.domain.com/" I have a FreeIPA server being accessed the same way, specifying an IP address as opposed to the name of a container, and it works fine. The big difference is the FreeIPA server does not use https. Any suggestions are appreciated! Thanks!
  23. I wrote down what NerdPack had installed prior to uninstalling and then installing NerdTools. Everything that NerdPack had installed is not listed on NerdTools. Should I assume all of these things are built into unRAID now? I didn't write down the entire name of the package, but here is what I had: sysstat perl mcelog kbd iperf (I see from the pinned comment that this is included with unRAID) Thanks! UPDATE: Okay, I see from the 6.11 release notes that all but the kbd package is included. Maybe I wrote that one down wrong?
  24. So, did you use swag? I have reverse proxy set up for several dockers already. For instance, it works fine for NextCloud, but I used the included NextCloud conf file in nginx (plus I had SpaceInvaderOne's video guide). There isn't an included conf file for SearXNG, so I've tried to build one based on NextCloud, but no matter what, the docker list always says the external port for SearXNG is 8080, whereas it's 443 for NextCloud. I'm most definitely a novice when it comes to this stuff, so extrapolating from other things doesn't always go well. 😄 If you used Swag, can I see what your nginx conf file looks like? Thanks!

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.