manfat

Just got the 'fix common problems' plugin warnings again about this plugin not being known to Community Applications and is possibly incompatible. Any ideas on how to get this useful plugin added to Community Applications so these warnings stop?

How are plugins added to CA so that they become known/recognised as compatible with unRAID? RE: https://forums.unraid.net/topic/189395-plugin-secure-unraid-webgui-with-acmesh/ The 'fix common problems' plugin just generated the following warning message: "The plugin ACME.plg is not known to Community Applications and is possibly incompatible with your server" with a suggested fix comment: "As a general rule, if the plugin is not known to Community Applications, then it is not compatible with your server. It is recommended to uninstall this plugin" so I'm just wondering how to get this useful plugin added so that it can be recognised by CA as compatible? Otherwise I'm quite happy to just ignore the warning for now.

The 'fix common problems' plugin just generated the following warning message: "The plugin ACME.plg is not known to Community Applications and is possibly incompatible with your server" with a suggested fix comment: "As a general rule, if the plugin is not known to Community Applications, then it is not compatible with your server. It is recommended to uninstall this plugin" so I'm just wondering how to get this useful plugin added so that it can be recognised by CA as compatible? Otherwise I'm quite happy to just ignore the warning for now.

Hey @ich777 first thanks for the years of effort that you've put into maintaining these images, much appreciated. As others mentioned it seems that your changes last month stopped the default image viewer function working with JPEG files in the Krusader image. This is a minor issue for me but guessing one option for a quick fix may be to just include a KDE image viewer like Gwenview on line 9 of the Dockerfile? (unless there is another default one already installed somewhere in the base image we can point to maybe?) https://github.com/ich777/docker-krusader/blob/master/Dockerfile Just out of interest I tried the @binhex version of Krusader from community apps and that seems to have the same issue but unsure if that was always that way or not...

I just tested this plugin and it worked perfectly with my personal domains on Cloudflare, many thanks for this excellent automation it is very much appreciated 😁 Some notes for anyone else interested in testing this: You can test everything works manually first ( which is how I had SSL set up previously ) if you prefer to have an emergency fallback option - I'm happy to share details of the manual approach that I took beforehand so if anyone is interested, just ask The install method I used was to copy and paste the raw plugin URL from Github (above) directly into the install plugin option in unRAID I already had my personal domain email registered beforehand with ZeroSSL so unsure how well it works registering a fresh one The last few lines output after plugin installation were as follows Running reload cmd: /usr/share/ACME/scripts/reloadcmd /boot/config/ssl/certs/unraid_unraid_bundle.pem Installing certificate... Reloading nginx... Stopping nchan processes... ^ you can click the [Done] button at this point, there was also a successful popup notification saying 'Certificate renewed' - nice! Overall this automation should save me about fifteen minutes every few months - very nice so thanks again @morgendagen excellent work 👍

@ChannelD thanks for sharing. Just one comment: ==> add AllowGroups schusses ^ I think that line has a typo - should it not look like this? - ==> add AllowGroups sshusers I'm attempting to put together an automated script to enable passwordless normal user SCP with public key authentication for use with WinSCP. I've not fully tested it yet but I have had it working manually and is based on the scripts above but enabled using the user scripts plugin rather than main /boot/config/go one One thing I learned was that you must ensure that the directory and file ownership and permissions are correct i.e. on the user home and subdirectories and key files using chown and chmod commands ( as I think the SSH daemon needs that when reading the users ~/.ssh/authorized_keys file containing the public keys based on its logs ) For SFTP (rather than just scp) transfers via Tailscale I'm already using the excellent TailVault container from @SpaceInvaderOne but I prefer to have a manual backup option for that with pubkey based auth and have disabled SSH for root. Here is my draft script: #!/bin/bash # EDIT NEXT TWO LINES and change CHANGEME to your SSH username and paste in your SSH public key _username=CHANGEME _sshpublickey='ssh-ed25519 PASTE-YOUR-RANDOM-LONG-SSH-PUBLIC-KEY-STRING-OVER-THIS' # Rereate user home directory - I tested and this is deleted on a reboot mkdir /$_username # Set home directory and assign shell cat /etc/passwd | sed -e s/$_username.*false/"$_username:x:1000:100:User description:\/$_username:\/bin\/bash"/ > /etc/passwd.1 mv /etc/passwd.1 /etc/passwd # Ensure user profile doesn't try to send you to the root homedir upon login cat /etc/profile | sed -e s/"export HOME=\/root"/"export HOME=\/\`whoami\`"/ > /etc/profile.1 mv /etc/profile.1 /etc/profile # Comment out AllowUsers line in the SSH daemon config file to allow all users to SSH in cat /etc/ssh/sshd_config | sed -e s/"AllowUsers root"/"# AllowUsers root"/ > /etc/ssh/sshd_config.1 mv /etc/ssh/sshd_config.1 /etc/ssh/sshd_config # then restart the SSH daemon /etc/rc.d/rc.sshd reload # Setup public key based auth for user - note you may need to uncomment PubkeyAuthentication line in /etc/ssh/sshd_config mkdir /$_username/.ssh echo $_sshpublickey > /$_username/.ssh/authorized_keys chmod 600 /$_username/.ssh/authorized_keys chmod 700 /$_username/.ssh chmod 750 /$_username chown -R $_username:users /$_username/You can generate a new key pair using the free PuTTYgen tool on Windows and also test logging in using WinSCP but must use SCP mode not SFTP unless you've otherwise enabled that already. PLEASE NOTE: This is only meant to be used as an emergency backup if root SSH is disabled and not intended for any other purpose but I thought I would share in case anyone else finds it useful.

I can confirm this fixed same issue for me when attempting to reinstall some plugins after upgrade from 6.x to 7.0.1

Idea/suggestion to add a plugin check please - the old version of the mover tuning plugin seems incompatible with unRAID v7.0.0 and stops working, causing cache pool to fill up. Simple fix is the remove the incompatible plugin then either run the stock built-in mover to empty the cache pool or install and configure the latest version of the plugin. Unfortunately when searching for the mover tuning plugin on the community apps there are two results returned and it isn't clear which version is which but I think the one with Reynald mentioned is the latest one with fixes for unRAID v7.0.0.

Should we get the older incompatible mover tuning plugin version formally added to the 'known issues' for v7.0.0 release? Also could we possibly work with the 'fix common problems' code to highlight the issue for those who were unaware and have upgraded already i.e. before filling up other old plugin users cache pools? Maybe even consider the new automated unRAID patch mechanism to upgrade from old to new plugin versions although I saw a post above that might be conflicting? Just wondering how many other folks out there might've upgraded to v7.0.0 and not yet noticed their cache pools filling up and also have no idea why Is it worth asking @Squid to temporarily add a warning to the top page for this thread? In the meantime for anyone else just wanting an emergency quick fix on unRAID 7.0.0 - removing the old incompatible mover tuning plugin and running the stock mover should work before adding the newer fixed plugin version back and configuring it again.

+1 for solution - removing the old (incompatible) mover tuning plugin also helped get mover working again for me since upgrade to v7.0.0 NOTE: Later version of the mover tuning plugin is available ( last updated July 19th 2024 by user @Reynald ) which explicitly mentions v7.0.0 compatibility but I haven't yet tested that version. I was clearly running the old v7.0.0 incompatible version.

Hi @binhex just checking if you're aware of the recent backdoor added to xz/libzma? I checked using console and looks like some of your containers may be running an affected version of xz? I doubt this actually introduces any risk unless folks are somehow using SSH in same container (extremely unlikely!) but maybe worth reverting to a clean version if Plex uses xz at all?

This happened to me on latest release, I can confirm that a reboot resolved the issue, thanks.

+1 for an official API but it does NOT need to be a web based interface, the underlying individual software functions can easily use any suitable programming language. I'd love to see unRAID move to a completely open source support model, similar to how CentOS compares to RHEL, then I'd willingly contribute more time to the product and pay for a reasonable yearly support subscription. Perhaps there are other professional developers and testers out there that feel the same way? If so, maybe a crowdfunding effort to kick-start an official open unRAID fork is a viable option, as long as Limetech formally approve of course, as owners of the brand.

Sorry for not responding sooner. Yes, normally their servers act as gatekeepers between the public internet and your Plex server. When their auth servers fail, you therefore cannot log in and get to your own media. Apparently there is a method (which I've not yet tested and needs configuring in advance!) for serving media directly via DLNA (without any internet dependency) here: https://www.howtogeek.com/303282/how-to-use-plex-media-server-without-internet-access/

Very minor annoyance but my instance of Plex recently started 'refreshing' the main screen every few seconds, regardless of client. I just wondered if anyone else had this or just me? Considering rebuilding my library or trying another version.