December 8, 20223 yr Could I request an option to bypass this feature completely please. This would be a real quality of life improvement for compose users.
December 9, 20223 yr Just updated run FIx and it shows this warning!! But mine is already set to what it suggests ? So not sure why its telling me to do something already set ?
December 9, 20223 yr 1 hour ago, OsoPolar said: Just updated run FIx and it shows this warning!! But mine is already set to what it suggests ? So not sure why its telling me to do something already set ? Sorry about that, I see the bug. p.s. this was my bug, not Squid's
December 9, 20223 yr Author 1 hour ago, OsoPolar said: Just updated run FIx and it shows this warning!! But mine is already set to what it suggests ? So not sure why its telling me to do something already set ? Can you update to 2022.12.09b and see if it's now fixed
December 10, 20223 yr Author Extended Tests are now removed from FCP Extended tests had their use a number of years ago, but nowadays No matter what you do it's a given that it will always return issues Those issues are not "real" per se They're primarily tests for SMB compatibility, (and any errors are once again not "real" issues) It takes forever to run
December 12, 20223 yr FCP recently started warning me that Quote Your mnemos_unraid_bundle.pem certificate is not valid for your system's hostname 'mnemos.rendezvous.agffa.net'. Either adjust the system name and local TLD to match the certificate, or get a certificate that matches your settings. But my subject CN appears to be set correct for a wildcard root@mnemos:/boot/config/ssl/certs# openssl x509 -noout -text -in mnemos_unraid_bundle.pem | grep "Subject: CN" Subject: CN = *.rendezvous.agffa.net root@mnemos:/boot/config/ssl/certs# and my local TLD also appears to be correct I am still on unRAID 6.9.2 if that matters.
December 12, 20223 yr 13 hours ago, rjorgenson said: FCP recently started warning me that But my subject CN appears to be set correct for a wildcard root@mnemos:/boot/config/ssl/certs# openssl x509 -noout -text -in mnemos_unraid_bundle.pem | grep "Subject: CN" Subject: CN = *.rendezvous.agffa.net root@mnemos:/boot/config/ssl/certs# and my local TLD also appears to be correct I am still on unRAID 6.9.2 if that matters. Would you run these two commands please? openssl x509 -noout -subject -nameopt multiline -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | sed -n 's/ *commonName *= //p' openssl x509 -noout -ext subjectAltName -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | grep -Eo 'DNS:[a-zA-Z 0-9.*-]*' | sed 's/DNS://g' Is this is an official cert provided by a certificate provider or one you generated?
December 12, 20223 yr 14 minutes ago, ljm42 said: Would you run these two commands please? openssl x509 -noout -subject -nameopt multiline -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | sed -n 's/ *commonName *= //p' openssl x509 -noout -ext subjectAltName -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | grep -Eo 'DNS:[a-zA-Z 0-9.*-]*' | sed 's/DNS://g' Is this is an official cert provided by a certificate provider or one you generated? This is a wildacard cert provided by letsencrypt. Here is the output of those two commands. root@mnemos:~# openssl x509 -noout -subject -nameopt multiline -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | sed -n 's/ *commonName *= //p' *.rendezvous.agffa.net root@mnemos:~# openssl x509 -noout -ext subjectAltName -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | grep -Eo 'DNS:[a-zA-Z 0-9.*-]*' | sed 's/DNS://g' *.rendezvous.agffa.net agffa.net rendezvous.agffa.net root@mnemos:~#
December 12, 20223 yr 6 minutes ago, rjorgenson said: This is a wildacard cert provided by letsencrypt. Here is the output of those two commands. root@mnemos:~# openssl x509 -noout -subject -nameopt multiline -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | sed -n 's/ *commonName *= //p' *.rendezvous.agffa.net root@mnemos:~# openssl x509 -noout -ext subjectAltName -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | grep -Eo 'DNS:[a-zA-Z 0-9.*-]*' | sed 's/DNS://g' *.rendezvous.agffa.net agffa.net rendezvous.agffa.net root@mnemos:~# I don't have a wildcard cert to test with, but I'll use the output from those commands to mimic it on a 6.9.2 system. Would you mind uploading your diagnostics.zip file (from Tools -> Diagnostics) as well?
December 12, 20223 yr 3 hours ago, ljm42 said: I don't have a wildcard cert to test with, but I'll use the output from those commands to mimic it on a 6.9.2 system. Would you mind uploading your diagnostics.zip file (from Tools -> Diagnostics) as well? Sure thing, here you go. Thanks for the help! mnemos-diagnostics-20221212-1254.zip
December 12, 20223 yr 21 hours ago, rjorgenson said: But my subject CN appears to be set correct for a wildcard Thanks for reporting this, I see the issue. Also mine and not Squid's
December 13, 20223 yr 3 hours ago, ljm42 said: Thanks for reporting this, I see the issue. Also mine and not Squid's Glad the issue was found. Am I safe to dismiss this for now until a new version is released? Or will I need to change something about my cert eventually anyways?
December 13, 20223 yr 12 hours ago, rjorgenson said: Glad the issue was found. Am I safe to dismiss this for now until a new version is released? Or will I need to change something about my cert eventually anyways? Your cert should be good. Would you please update to today's release of Fix Common Problems and confirm it no longer warns about your setup?
December 13, 20223 yr 3 hours ago, ljm42 said: Your cert should be good. Would you please update to today's release of Fix Common Problems and confirm it no longer warns about your setup? yeah it's all good now, no longer complaining after upgrading.
December 13, 20223 yr Has anyone noticed that the exclusion list for "Docker Safe New Perms" has disappeared from the Settings/FixProblems page after the patch 2022.12.10 (or 2022.12.09)? I still have some shares on that list which I would like to be able to change.
December 13, 20223 yr Author 4 minutes ago, Waoji said: Has anyone noticed that the exclusion list for "Docker Safe New Perms" has disappeared from the Settings/FixProblems page after the patch 2022.12.10 (or 2022.12.09)? I still have some shares on that list which I would like to be able to change. That's an oops on my part... Removed as part of removing the extended tests. I'll add it back in tomorrow
December 13, 20223 yr Invalid folder cache contained within /mnt Think I have this due to renaming a cache drive how do I fix it Thanks tower-diagnostics-20221213-2335.zip
December 14, 20223 yr Author 37 minutes ago, gemeit said: Invalid folder cache contained within /mnt Think I have this due to renaming a cache drive how do I fix it Thanks tower-diagnostics-20221213-2335.zip 127.47 kB · 0 downloads Look for a docker container referencing /mnt/cache/... in one of it's host paths.
December 15, 20223 yr Hi all, I'm running the backup appdata plugin. The scan suggests to switch to the KluthR version, because the original has been deprecated. I've checked, and I am running the KluthR version. Any suggestions?
December 15, 20223 yr Author Are you sure about that? Have you done a rescan since you switched (or has another scan been run)
December 15, 20223 yr Hi, please could you advise on this. When I click on "The following shares will NOT be touched: Additional shares can be excluded HERE" in Docker Safe New Perms, it takes me to Fix Common Problems. However, there is no option to exclude shares. I have tried updating Fix Common Problems and clearing the browser cache. Edit: I went through and manuualy checked ownership for each share using find . ! -user nobody Then fixed as required using newperms /mnt/user/share It would still be cool to do this in a more automate way, though. Edited December 15, 20223 yr by Mushin
December 15, 20223 yr On 12/14/2022 at 12:14 AM, Squid said: Look for a docker container referencing /mnt/cache/... in one of it's host paths. Thank you
December 18, 20223 yr On 12/15/2022 at 10:50 PM, Mushin said: However, there is no option to exclude shares Same. Some thing has changed very recently and the "Docker Safe New Permissions" is now broken because you can't set the include/exclude shares any longer. I'm stuck because I have all of my shares barring one excluded
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.