nraygun

I notice that when I update a Docker container manually, I get a blank status while it's updating but then shows what it was doing when it completes the task. It just says "Update Container". I just wait for it to show the Done button, but it doesn't show progress like it did before. flores-diagnostics-20251207-1008.zip

Yep, BOINC was the problem. Relatively clean syslog now with no odd behaviors.

Yep, it was BOINC. I manually started it and the RAM usage jumped to 94% after a minute or two. There must have been an update that broke it. I'll leave it off for a day or two to see if I continue to get the OOM messages.

Still looking through the logs but I see that things seemed to start going haywire on Friday 11/28/2025 at 22:35:05. It went almost a month with no oom-killing. And before 11/28, the last one was on 10/4/2025, and then before that it was 12/27/2024. On 11/28 it started to call oom-killer for different processes every few minutes! I haven't had any today on 12/1/2025. Got a few theories: Maybe BOINC was causing all this. I see in the config the memory usage was set to use up to 90%. The client is not using the setting I have setup via web prefs. I manually set it to 50%. Bad memory? As soon as it's done with the parity check, I'll run a Memtest.

I was watching a movie last night with the family and all of a sudden Plex stopped playing the movie. A few moments later it looked like it was down. I tried to log into the web page of the server but it was not responding. I also could not ssh into it either. However, I could ping it. I went into the basement and connected a monitor and keyboard. I could log in and saw that BOINC was using lots of memory. The system was very slow at this point and it took a while for "top" to even come up. I paused the BOINC container and it started to behave normally and we finished the movie. This morning I see in the syslog a bunch of oom-killer processes for various apps on my server. These go all the way back to 10/4/2025 of this year. That day also happens to be the first time I got an out of memory error. It bombed on postgres but I was also running a VM with 8GB of RAM at the time so I think that's what did it. It's running a monthly parity check as I type this. Not sure what's going on this time and it seems to be happening often from what I can tell in the logs. Not sure why I was OK from 12/27/2024 to 10/4/2025. Maybe I just need more RAM? I'm on 32GB and my old server had 64GB. flores-diagnostics-20251201-1149.zip

I got it! I had to add the container range, the server range, and the IP of that my ISP gives me to the WOPI setting in the configuration for the Nextcloud Office app. I even tested taking entries out one at a time to confirm they are needed. So, the WOPI values for my instance are: 172.18.0.0/24,192.168.0.100/24,ipaddrisp where ipaddrisp is my IP from the ISP.

I had found the WOPI area of the app and had said I tried things there so you didn't need to provide the breadcrumbs to get there. The online dox for Collabora are pretty bare bones in my opinion. And to get to this point, yes, I've been Googling. Surely you recognized this or perhaps you're new to trying to help people. However, I'll keep Googlin'.

I got it! It was a little weird here and there, but I now have editing capabilities in my Nextcloud instance. Woohoo! Here's what I did: Installed Collabora using the template from L4stIdi0t. I changed the container name to collabora and turned off privileged mode. Tested that I was able to access the container by using the WebUI link for the container. Went into SWAG's appdata/ and removed .sample from the file swag/nginx/proxy-confs/collabora.subdomain.conf.sample At this point, SWAG revokes certs and has a problem connecting back to the standalone server on port 80 to confirm the CA cert. More on this in a bit. Added the CNAME to my domain's DNS. Used TTL=30 minutes so I waited at least this amount of time for it to propagate. Had to wait a little longer but confirmed CNAME was ready by going to https://toolbox.googleapps.com/apps/dig/ to confirm it. At this point going to collabora.mydomain.com gives an OK So now onto getting SWAG to refresh certs. I had to edit the config.php in Nextcloud to remove the "s" for 'overwrite.cli.url' and 'overwriteprotocol'. This made SWAG work again but I don't know why. I then put things back to the way they were originally. With new certs, I was then able to access Nextcloud again. I added the "Nextcloud Office" plugin. I entered the URL for my collabora instance(collabora.mydomain.com) in the "Use your own server". And it worked! I do get a warning about WOPI. I'm not sure what to add to that list. I tried the real IP of the nextcloud and collabora containers and still got an error. I have Collabora turned off for now until I can figure out this WOPI business. I think this ties it down so only Nextcloud can access the internet facing Collabora container. Can someone point me in the right direction on the plugin's WOPI setting?

I saw that setting. Will that Collabora container work with it turned off? I gave the L4stIdi0t template a try. Things went completely wonky when I added the CNAME for Collabora in my registrars DNS setting for my domain. Took me all morning to get SWAG and Nextcloud working again just from that one little change. Not even sure what fixed it other than perhaps a DNS propagation of changes. Nextcloud seems like a delicate house of cards. Again, I think I'll leave well enough alone.

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?