nraygun

I'm avoiding that one because of this warning in the template Info: And further down in the Info it says: None of the other 40 containers I have display this warning so I'm a little leery of it. I don't know, maybe I'll give running a container straight from Docker Hub a try. I've not done this before - I've only used templates. But I might do this after a break - I was at it all day yesterday trying to make that OnlyOffice container work properly.

I've had my instance of Nextcloud(and other apps) running fine for years behind a reverse proxy. I see that many people have had problems with integrating Collabora and OnlyOffice into Nextcloud. I gave OnlyOffice a try, got pretty far, but then wound up in the same boat as many others. At least there was a an official container out there unlike Collabora. I think I'll leave well enough alone and consider going to the AIO in the future. Or maybe SpaceInvaderOne will put out an updated video some day.

I must be doing something wrong. When I do this, I see a huge number of options and I see this at the bottom of the search results: "Displaying 1 - 25 (of 10000)" LOL!

Why is there no Linuxserver Collabora container? What container should I use? The only one I see out there is Collabora-CODE by L4stIdi0t. Is there another option? I've not used any containers from L4stIdi0t before.

Oh wait, I found this info for the container I’m using(linuxserver). I just don’t want another container exposed to the internet but I guess I have no choice. Collaborative EditingNextcloud's built-in collaborative editing packages (Collabora/CODE and OnlyOffice) only work on x86_64 systems with glibc, and therefore they are not compatible with our images. You should create separate containers for them and set them up in Nextcloud with their respective connector addons. If (auto) installed, those built-in packages may cause instability and should be removed.

Quick question: Is a separate Collabora instance still needed for office dox support in Nextcloud?

There was a checkbox somewhere that seemed to imply the ability to manage the server via the connect interface was a toggle. Of course, I can't find it now. I think I'm all set. Thanks!

Assuming Flash Backup is available when the two conditions above are met. Closing issue.

I think I found the answer. It appears the "latest" tag includes beta releases for Plex Pass users. I don't want beta release - this last one borked my system. I changed the tag to "public" to get the latest publicly released versions but not betas.

Having some major problems with Plex on my Unraid 7.1.4 i5-12600K box. It stopped playing .mpg files. It was also unable to play some movies that I was able to play on Sunday. And for a bit there, it didn't see the iGPU. I was able to play at least one .mpg last week when I calibrated the 5.1 setup in the basement last week. I had added 3 magnetic fan filters to the bottom of the case. I removed these and was able to play a few movies I couldn't before but still not .mpg files. Not sure if that is related or a coincidence. I saw that Plex updated on Sunday, so I tried reverting back to 1.41.6 by changing the repository to "linuxserver/plex:1.41.6". I also tried deleting the Codecs directory in appdata. Even though I reverted back to 1.41.6, it is using Version 1.43.0.10162 . I don't even see a 1.43.0 in the linuxserver hub. And I see this in the logs: linuxserver.io version: 1.41.6.9685-d301f511a-ls264 Build-date: 2025-04-28T10:53:22+00:00 ─────────────────────────────────────── Setting permissions on /tmp **** Server already claimed **** **** creating video group video42bv with id 18 **** **** adding /dev/dri/renderD128 to video group video42bv with id 18 **** **** permissions for /dev/dri/card0 are good **** Attempting to upgrade to: 1.43.0.10162-b67a664b6 (Reading database ... 9538 files and directories currently installed.) Preparing to unpack .../plexmediaserver_1.43.0.10162-b67a664b6_amd64.deb ... PlexMediaServer install: Pre-installation Validation. PlexMediaServer install: Custom environment detected. Skipping preinstallation validation. Unpacking plexmediaserver (1.43.0.10162-b67a664b6) over (1.41.6.9685-d301f511a) ... Setting up plexmediaserver (1.43.0.10162-b67a664b6) ... PlexMediaServer install: Custom environment detected. Skipping postinstallation tasks. Continuing. [custom-init] No custom files found, skipping... Starting Plex Media Server. . . (you can ignore the libusb_init error) [ls.io-init] done. Critical: libusb_init failed UPDATE: I was able to go back to 1.42.2 by also changing the VERSION variable from "latest" to "1.42.2" and now I can play .mpg files again! But I still want to know why it went to 1.43.0. Where is it getting 1.43.0? The latest I see is 1.42.2. What is "video42bv"?

I think we're good here. Last error was on 9/4/2025. Marking as solution.

I opened a ticket and got a quick response. I turned off NetBIOS and kept WSD on. Now I'm monitoring to see if I still get the DFS errors.

I went to 7.1.4 recently, and I still see these errors. Most recent one was yesterday. I'll submit a bug report if I can find where to do that.

Well, it looks like the frequent flash_backup entries were reduced to 1 entry after 8/12/2025. I rebooted my server on 8/25/2025 this week I think. I see that the Unraid Connect plugin had an update, so I updated it. The flash backup function was disabled. Not sure if the reboot did this or if it turned off some time after 8/12. It appears that I can't upload flash backups without turning on Manage Server. I could swear I was able to do flash backups to Connect without turning on the Manage Server feature. I don't like the idea of being able to manage my server across the internet. I'd like for it to be local only. I looking at what URL it uses, I see that it uses a myunraid.net domain. If i hit that manage URL from my phone on my wifi, I can get to it. If I disable wifi, and use cellular, it doesn't connect. That's good. So, can you confirm that the Flash Backup feature of Unraid Connect is only available when a) logged into the service, and b) when Manage Server is enabled. I don't see a way to disable the Manage Server function without logging out of Connect which would also disable flash backup.

Thanks again. I'll take a look. It was not doing this before. Maybe I have a new/updated plugin fiddling with the flash drive.

Thanks @ljm42 I see that the increase in adding tasks started happening around 3/21/2025 - that's the day I went to 7.0.1. Prior to that date, I don't see 6,7, and 19 back-to-back entries like in the examples above. Did 7.0.1 change how this "flash_backup: checking for changes every 1800 seconds" works in Unraid 7?

Recently upgraded to 7.1.4 and looking through the syslog I see multiple entries like this every once in a while: Aug 12 13:30:46 flores flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 12 14:00:46 flores flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 12 14:30:46 flores flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 12 15:00:46 flores flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 12 15:30:46 flores flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 12 16:00:46 flores flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Aug 12 16:30:46 flores flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Looks like it added a backup task every 30 minutes. Here it did it 7 times in a row. Earlier it did it 6 times, then before that, 19 times. There are few other things with the upgrade, but I'll tackle them one at a time. Why is it doing this? server-diagnostics-20250812-1804.zip

OK, thanks! I'm in a holding pattern for 7.1.4. Probably next month.

Was poking around in my syslogs and see that I started getting these types of errors right around when I went to 7.0.1 in March 2025: Mar 19 19:19:19 server smbd[941291]: [2025/03/19 19:19:19.657930, 0] ../../source3/smbd/msdfs.c:120(parse_dfs_path_strict) Mar 19 19:19:19 server smbd[941291]: parse_dfs_path_strict: Hostname #007SERVER is not ours.I checked the identity area and see that my server is named "server" (lowercase). Googling around says it's a smb.conf issue, but I see no mention of SERVER in the config and testparm -s looks OK. I think everything seems to work. What gives?

And what is the command? shutdown?

That's what I did but it shutdown pretty fast. Just worried the rug got pulled out from under it. Does "shutdown" perform a graceful shutdown? Stop containers, stop parity check if running, and such.

I'm having all kinds of fun these days with Unraid. Locked myself out of the GUI due to a bad wireless keyboard. I found the info on how to reset the root password but it says to shutdown the server to edit the shadows file. Since I couldn't get to the GUI to initiate the shutdown, I SSH'd into the server. Kinda surprised that worked. When I entered powerdown, it said the command has been deprecated. So I did a shutdown and it shut down pretty quickly. I was running a parity check at the time. Did the shutdown command shut the server down gracefully? If the powerdown command is deprecated, what do I use instead? As long as I'm asking, how do I also stop a parity check via CLI? I see there's a pause and resume, but no stop with the "/usr/local/emhttp/webGui/scripts/parity_control" command.

Wound up using the manual method with the backup from the Unraid Connect site. I added the passwords back for the users. I think I'm all set. @JorgeB and @trurl - Thanks for the help! PS - My backup drive died too! It was unreadable on two systems. Bought a pair of new WD Red Plus drives from Amazon and backing up now.

I tried to proceed with the backup from the Unraid Connect service and the Windows tools seemed to think this was a new install. It asked for the server name, IP, netmask, etc. When it was done, there was no config folder on the drive. Trying the manual method with the back from Appdata...

@JorgeB In preparation for the new USB drive, I see this in the dox: "Important: Backups from the flash device do not include the config/shadow or config/smbpasswd files. User accounts are preserved, but their passwords are not." And also, "This service is intended to store configuration files that will allow you to get back up and running quickly, it is not a 1:1 backup of the contents of your flash drive." I was expecting to restore from a backup and be back up and running like it was before. Not sure I can use the back up from Unraid Connect to get there. Luckily, I was running AppData Backup and I have a backup in the array from a week ago that I can get to from a Linux distro on my Ventoy drive. I see it has the config/shadow or config/smbpasswd files. Will the Windows Flash Creator tool work with the backup from Appdata Backup?