Mattaton

Members
  • Posts

    300
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Mattaton

  1. Nice. I was able to find one on eBay. Looking forward to giving this a shot. ๐Ÿ™‚ P.S.: "Vacation Home"....I'm jelly ๐Ÿ˜„
  2. Awesome! Glad you got it working for you! And hey, we've all been there. Thanks for being cool about it. ๐Ÿ˜Š
  3. Ah man. That's awesome, but a shame they aren't available any longer. Any suggestions on alternatives?
  4. Such is the nature of a community-driven plugin ecosystem. Which isn't unique to unRAID. unRAID didn't create the old plugin or this one, so there would be no warning from them. The development for the old plugin died and I'm glad @scolcipitato created this one. He's very responsive and helpful in the development and improvement of it. Can you elaborate on what isn't working for you? We'll be glad to try to help you with it. I think most of us have FolderView working just as well or better than Docker Folders at this point.
  5. Slightly off-topic, but is there any truth or evidence to the claims where people have used SD cards in USB readers/adapters or SSDs connected with USB cables? Supposedly unRAID pulls the ID of the reader or SSD holder/connector and registers that which then allows the user to swap the SD card or SSD if it goes bad. So as long as the reader or holder/connector is good, then unRAID is "happy." If this indeed works, it sure takes a lot of the headache out of swapping flash drives. Just pop out the bad SD card, restore to a new one and you're good to go. I haven't tried it, but I do have an external enclosure for NVMe SSDs. When I connect it to my Windows machine, it sees the enclosure as the device and not the SSD. Maybe that's how unRAID would see it, too? If it has a GUID, you're golden? When I connect the enclosure, it gives Vendor, Product, and Serial Number. Although the serial number doesn't seem quite unique: 012345678930 So, yeah, probably not with this. I just plugged an SD card into a little USB reader/adapter. The reader comes up with a more unique serial, but still nowhere near the length of the serial on a flash drive. Vendor ID : 0x0BDA (Realtek Semiconductor Corp.) Product ID : 0x0120 Serial: 200604130921XXXXX
  6. I had read the first PSA post of that thread, but definitely not the entire thread. So, I knew to steer clear of Sandisk...although I still find a lot of rather current posts on Reddit and elsewhere that people are using SanDisk with no issues. So I assume this comes back to the counterfeit crud on Amazon. Maybe they got them at a Big Box Store or something instead of Amazon. I've never heard of Kanguru. I guess if they're tested. I know the flash drive doesn't matter THAT much as long as it works. When shopping, reputable brands just give better odds of working, I suppose.
  7. Are you guys having any luck finding decent USB drives on Amazon that are proven to work for unRAID? I have bought Samsung BAR Plus and FIT Plus in the past based on SpaceInvaderOne's video, but even those aren't available on Amazon anymore. They're 64GB and up. Which makes sense from a typical use-case for the drives, but not so much for unRAID. And those weren't even USB2.0. That's even harder to find. And with Sandisk no longer being recommended, that cuts out a big reputable brand...although not so reputable where unRAID is concerned, I suppose. Where are you guys landing drives these days? About to get a license for a new server and I need a drive! ๐Ÿ™‚ Thanks!
  8. I need some help with the db-backup container... Backups of MySQL server in separate container work fine. Instance for Postgres fails. Postgres logs say: 2023-11-21 03:00:00.852 EST [535] FATAL: password authentication failed for user "dbbackup" 2023-11-21 03:00:00.852 EST [535] DETAIL: Role "dbbackup" does not exist. Connection matched pg_hba.conf line 100: "host all all all scram-sha-256" 2023-11-21 03:00:00.872 EST [536] FATAL: database "admin" does not exist But DB_NAME and DB_USER are not set to be admin or dbbackup. So where is it getting that from? The login credentials the container has are correct and work fine to log in via Adminer. If I run backup-now in the container terminal, I get this: psql: error: connection to server at "192.168.75.10", port 5432 failed: FATAL: database "admin" does not exist Are the keys in the template wrong for postgreSQL? Manual run with debug mode on shows this as the command sent: psql -h 192.168.75.10 -U admin -p 5432 -d admin -c 'COPY (SELECT datname FROM pg_database WHERE datistemplate = false) TO STDOUT;' Looks like it's set the port number as the password (unless -p is for port?) and the username (admin) as the database name? Here are my settings. It looks correct, but it doesn't seem the variables are being parsed correctly for postgresql. Tried it all on a different unRAID server. Same error. It comes back saying database "-DB_USER-" does not exist. There is something broken in how the query is parsed from the container variables. They don't work the same from mysql to pgsql. Other than the above issues...I am also seeing a lot of deprecation warnings and the keys for the template don't match the keys spec'ed on the github page for db-backup. 2023-11-22.09:02:49 [WARN] ** [db-backup01-scheduler] Deprecated and unsupported variable 'DB_DUMP_BEGIN' detected - Please upgrade your variables as they will be removed in version 4.3.0 2023-11-22.09:02:49 [WARN] ** [db-backup01-scheduler] Deprecated and unsupported variable 'DB_DUMP_FREQ' detected - Please upgrade your variables as they will be removed in version 4.3.0 2023-11-22.09:02:49 [WARN] ** [db-backup01-scheduler] Legacy unsupported variable 'COMPRESSION' detected - Please upgrade your variables as they will be removed in version 4.3.0 2023-11-22.09:02:49 [WARN] ** [db-backup01-scheduler] Legacy unsupported variable 'SPLIT_DB' detected - Please upgrade your variables as they will be removed in version 4.3.0
  9. I changed the Tools->PHP Settings->Error reporting level to Errors Only (it was set to Default) and that got rid of the warning and brought the UPS details back.
  10. I just noticed an error (PHP Warning) on the UPS Settings page. Under the UPS Details portion where it used to show, well, the UPS details, it now just says this: Warning: Undefined variable $freq in /usr/local/emhttp/plugins/dynamix.apcupsd/include/UPSstatus.php on line 90 Any ideas how I can fix this?
  11. Ah man. Sorry. Maybe my new hardware/build fixed this issue, but I still had the issues in the other thread which ipvlan ultimately fixed. Thought the two problems were related, but maybe not. Good luck with it!
  12. My issue ended up being that I was using macvlan for custom docker networks instead of ipvlan. See this thread: Hopefully that helps you!
  13. You probably want to look into custom CSS for that. You can make it look however you want with the classes @scolcipitato has put on the elements.
  14. Is there a setting somewhere for how often Docker checks for updates? I have a server at work that seems to always find updates to containers long before my home server does. Just curious if this is a user-adjustable setting. Thanks!
  15. Depends on which unRAID theme you are using. For the Black and White themes, the lock icon is in the upper-right corner. For the Gray and Azure themes, it should be toward the bottom of the left column menu (I'm not exactly sure since I'm not using one of those themes). The sort order lock is an unRAID feature and is not added or edited by FolderView. It was added with unRAID 6.12+
  16. Sorting is done by drag and drop, both on the docker page (must unlock sort order first with lock icon in the upper right corner) and within each folder settings page. This question has been asked and answered several times recently. Scroll back and search the topic. ๐Ÿ˜Š
  17. This isn't the plugin, it's an unRAID version. 6.12 added the lock which you have to unlock before reordering the folders or containers. Then relock it. It's the same with or without the Folderview plugin.
  18. Not a bad idea and could be cool, but maybe try something like Uptime Kuma to track your containers and be notified if they go down. If @scolcipitato adds something, great, but Uptime Kuma is sweet.
  19. Also, if you want a dark mode theme, I have themes compatible with the built in black and gray themes. See my signature for a link.
  20. I'm not sure if @hernandito has updated the names of his custom files to work with the newest plugin version. Files have to be named like my.docker.css in order for the plugin to pick it up.
  21. It still works with earlier versions but is no longer under development. FolderView is the new hotness. ๐Ÿ™‚ Be advised, this is a completely separate plugin. I'm not sure if there is a clean way to move your folder order from Docker Folder to FolderView.
  22. You need to uninstall Docker Folder and install FolderView. I think as of 6.12.3 Docker Folders is a no-go. Thankfully @scolcipitato picked it up and ran with it. ๐Ÿ™‚
  23. You can see what dockerMan in unRAID has for the autostart order here: /flash/config/plugins/dockerMan/userprefs.cfg I would not edit that file, though. Not sure if that's kosher or not. Between dragging and dropping the folders (or containers that aren't in folders) on the docker page and then dragging and dropping the containers inside each folder on the folder's config page, you are setting the order you want for autostart. However, whenever you add a folder or make a change to the order inside a folder, you want to unlock the docker page and randomly move something, relock, and then unlock again and move things back the way you had it, and finally lock it again. This last random move and move-back is what updates that userprefs.cfg file to lock in the order you see on your screen. Once the order you see matches the order in userprefs.cfg, the autostart sync icon turns green letting you know what you see is what you'll actually get.
  24. The order for the folders themselves are handled on the docker page. You have to unlock them with the padlock icon, drag and drop to change order, then lock them again.
  25. When you first create a folder it will come up at the top of the container list, but that is NOT the same as the autostart order. That makes the icon red to let you know what you see is not the order they will actually start in. Once you change the order of folders or containers in the list, the auto load order is updated to match what you see, then the icon turns green.