40 minutes ago, flashback said:

I'm seeing this issue when I run the scan:

Looks like a bug. Thanks

15 minutes ago, Squid said:

Looks like a bug. Thanks

That makes more sense then! Thanks, I'll ignore for now.

On 10/24/2025 at 7:21 AM, dopeytree said:

there may an issue with using ghcr.io repos? I noticed even when you use them such as ghcr.io/chrisbenincasa/tunarr it still adds https://dockerhub infront sometimes but maybe thats a template authoring mode bug, but doesn't seem to affect function except it's saying this has been blacklisted because its not on docker hub when the url is GHCR.io (GitHub repos)

perhaps this ties into a wider community app issue? not really sure

If possible would like to see DATE & TIME of detection too.

I am also getting this message, along with a warning about ' The plugin dynamix.system.temp.plg is not known to Community Applications and is possibly incompatible with your server ' . Have reinstalled system temp, and it's working ok. reinstalled fcp and these 2 warnings still appear. So not so much a bug, as unexpected results.

Edited November 15, 2025Nov 15 by Wintermuteau

All dynamix plugins got an update now with this changelog

2025.11.14

Migrate repository to Unraid

after update, fcp check warns about all of them (not known).

Edited November 15, 2025Nov 15 by Niklas

It should be all good now. Migration of plugins from one repo to another is time intensive.

4 hours ago, Niklas said:

All dynamix plugins got an update now with this changelog

2025.11.14

Migrate repository to Unraid

after update, fcp check warns about all of them (not known).

This is the exact issue I am currently having as well.

4 hours ago, LordShad0w said:

This is the exact issue I am currently having as well.

Shloud be fixed.

Warnings gone for me.

Try scanning again.

Edited November 15, 2025Nov 15 by Niklas

Suddenly seeing 'Unable to communicate with GitHub.com' even tho I can install community apps and ping github. The only thing I notice is most icons for CA apps are not loading. Maybe a backend github url is down? How does it verify it's connection to github? I had made zero config changes to my server or network when this appeared so I think it's not on my side but need a way to verify.

I've rebooted, restarted docker service, disabled VPN, and turned off host access to custom networks but no luck on resolving the error messages.

1 minute ago, alicecantsleep said:

Suddenly seeing 'Unable to communicate with GitHub.com' even tho I can install community apps and ping github. The only thing I notice is most icons for CA apps are not loading. Maybe a backend github url is down? How does it verify it's connection to github? I had made zero config changes to my server or network when this appeared so I think it's not on my side but need a way to verify.

I've rebooted, restarted docker service, disabled VPN, and turned off host access to custom networks but no luck on resolving the error messages.

It's down.
https://www.githubstatus.com/incidents/5q7nmlxz30sk

Edited November 18, 2025Nov 18 by Niklas

10 minutes ago, Niklas said:

https://www.githubstatus.com/

Thank you!

Hello Squid

I've just got /var/log full error from FCP plugin. Attached here as per your instructions the exact error message and the diagnostics.

Hope you'll find a moment to help a full unRAID novice like myself.

TIA

Nick

ugreen-diagnostics-20251129-0816.zip

1 hour ago, nubbie61 said:

've just got /var/log full error from FCP plugin.

Log is being spammed with vsftp messages:

Nov 28 06:38:43 UGreen vsftpd[2538255]: [nick] OK UPLOAD: Client "192.168.2.105", "/mnt/user/S..v", 888110 bytes, 59620.19Kbyte/sec

Nov 28 06:38:43 UGreen vsftpd[2538255]: [nick] OK UPLOAD: Client "192.168.2.105", "/mnt/user/S..v", 1404058 bytes, 97925.32Kbyte/sec

Nov 28 06:38:44 UGreen vsftpd[2538255]: [nick] OK UPLOAD: Client "192.168.2.105", "/mnt/user/S..v", 1287618 bytes, 126604.86Kbyte/sec

See if they can be quieted.

1 hour ago, JorgeB said:

Log is being spammed with vsftp messages:

Nov 28 06:38:43 UGreen vsftpd[2538255]: [nick] OK UPLOAD: Client "192.168.2.105", "/mnt/user/S..v", 888110 bytes, 59620.19Kbyte/sec

Nov 28 06:38:43 UGreen vsftpd[2538255]: [nick] OK UPLOAD: Client "192.168.2.105", "/mnt/user/S..v", 1404058 bytes, 97925.32Kbyte/sec

Nov 28 06:38:44 UGreen vsftpd[2538255]: [nick] OK UPLOAD: Client "192.168.2.105", "/mnt/user/S..v", 1287618 bytes, 126604.86Kbyte/sec

See if they can be quieted.

Thanks a lot, JorgeB - that explains the situation to me. Will take this into account when next time using WinSCP for transfer.

There's currently a bad link. If you get this error:

And click on the THIS link after the error message, you're taken to https://forums.unraid.net/topic/39097-video-demo-managing-game-libraries-with-unraid-user-shares/#comment-381697 but that 404s.

I seem to be going in circles trying to get this sorted out, does anyone have any tipschaoticserver-diagnostics-20260118-1213.zip

Changed this post after more info.

You have told docker to write directly to the root of your pool cache (/mnt/cache) without defining any share (like /mnt/cache/sharename)

You need to stop docker and remove all files and folders created by docker and change the path to the actual share you want.

Create a share named "docker". Set cache as primary, no secondary. Change Docker directory from /mnt/cache/ to /mnt/user/docker

These has to be removed.

Folders:
/mnt/cache/buildkit/

/mnt/cache/containerd/

/mnt/cache/containers/

/mnt/cache/image/

/mnt/cache/network/

/mnt/cache/overlay2/

/mnt/cache/plugins/

/mnt/cache/runtimes/

/mnt/cache/swarm/

/mnt/cache/tmp/

/mnt/cache/unraid/

/mnt/cache/volumes/

Files:

/mnt/cache/unraid-autostart

/mnt/cache/unraid-update-status.json

/mnt/cache/engine-id

Edited January 18Jan 18 by Niklas
Edited path to cache pool

i will try changeing it to what you suggested and see how it goes. thank you!

Just now, ChaoticDesigns said:

i will try changeing it to what you suggested and see how it goes. thank you!

Yes. You have it set to /mnt/cache and that's directly on your cache pool root, no share. You need at least /mnt/cache/sharename

Better to create a share named "docker" with cache as primary, no secondary and change the docker folder path from /mnt/cache to /mnt/user/docker (/mnt/cache/docker would also work, it will be the same share but could cause problem in the future if you want to move the docker share).

I edited my first answer, you need to clean up the docker files and folders, se my edited answer.

After deleting the folders (and the three files) you may need to delete the shares with the same names in the gui that Unraid created because it found all those folders not connected to any shares under /mnt/cache/*.

Btw, you will lose all your docker containers after this but you can easily add them back by using Apps - Previous Apps or click "ADD CONTAINER" on the Docker-tab and find your template in the list under "[ User templates ]", don't change anything and click APPLY. All settings remembered.

NEVER set any paths with no share. Like /mnt/cache or /mnt/user. There needs to be a corresponding share, like /mnt/cache/myshare or /mnt/user/myshare. Easiest way is to always use /mnt/user/myshare (name as you wish). Unraid will handle and keep track of where the data goes. Following your specific share settings ofc.

Edited January 18Jan 18 by Niklas

i don't even know what all those shares are from, i didn't manually create them.

I had a power spike and lost my 3 array drives and my cache drive.

I am starting fresh all new drives and no data.

I just got done resetting most things up, i guess it won't hurt to start again lol

1 minute ago, ChaoticDesigns said:

i don't even know what all those shares are from, i didn't manually create them.

I had a power spike and lost my 3 array drives and my cache drive.

I am starting fresh all new drives and no data.

I just got done resetting most things up, i guess it won't hurt to start again lol

Unraid will add every folder it finds in the root of your mounts as shares if you haven't set them up as shares. So docker has created all of them in /mnt/cache and Unraid finds them and adds them automatically with default share settings. Because you shouldn't have any stray folders (and no files) there without matching shares. :) That's good if you lost your usb-drive or config for the share. The folders will show up as shares for you to easily find them and set them back to your own settings.

Edited January 18Jan 18 by Niklas

Thanks for all the help!

i created the docker share and pointed it there, looks like the new files were created there. before i go installing things again.

I can't seem to delete the old shares through the shares section when i click on it, the option is there, i just can't select it.

I have tried with docker and vm stopped and also when it is started.

I assume i will have to go in with Krusader or something and delete them afterwards?

2 minutes ago, ChaoticDesigns said:

i created the docker share and pointed it there, looks like the new files were created there. before i go installing things again.

I can't seem to delete the old shares through the shares section when i click on it, the option is there, i just can't select it.

I have tried with docker and vm stopped and also when it is started.

I assume i will have to go in with Krusader or something and delete them afterwards?

Yes. You can only delete empty shares (folders). You can use the built in file manager in the ui.

Edit

This strange icon will open it (I would like to see something like a file cabinet). Don't forget the files placed directly in /mnt/cache. It should only have folders, no files.

Edited January 18Jan 18 by Niklas

I'm using my array solely for replaceable media and have no parity and share set to cache->array no problems or real question there.

I have a zfs pool of SSDs i use as a cache pool

I also have a zfs pool called "raid" of two HHDs in raid 1 that is for data that I want to protect from disk failure. That share is set to cache->raid

Fix common problems is telling meShare local set to use pool cache-ssd, but files / folders exist on the raid pool which is a correct statement.
I have it set up as I do to leverage the speed of the SSDs and reduce writes to the raid pool until mover tuning runs and moves them later.

Is my methodology flawed or is this just a growing pain from the addition of multiple pool and the like?

Edited January 20Jan 20 by shiftylilbastrd
formatting