Mika Posted December 7, 2022 Share Posted December 7, 2022 Hey, the FCP plugin gives me a warning, that two NICs (eth 1 and eth 2) are having the same ip address, but there is only eth 1 visible in the network settings. Everything is working fine. Does anybody know how to fix this? Greetings Michael tower-diagnostics-20221207-1818.zip Quote Link to comment
NAS Posted December 8, 2022 Share Posted December 8, 2022 On 11/6/2022 at 4:49 PM, voidpointer said: The "Fix Common Problems" plugin warns about updating every individual docker container: > Docker Application prowlarr has an update available for it How can I disable this permanently for *all* docker containers? On 10/26/2022 at 12:50 AM, bdr9 said: This plugin is reporting many warnings on my Unraid server, but they are all Docker container updates. I can ignore them individually, but that only ignores the one specific Docker container, and warnings are still generated for other Docker containers. I would prefer not to receive any warnings for Docker container updates. Is there a way to disable this entire category of warning? This is a very long thread but I can only find issue reports and not a fix. How do I disable the image update warning entirely? I find myself starting to ignore Fix Common Problems because 99/100 it is docker noise and that cant be a good thing when that one time is important. Quote Link to comment
Squid Posted December 8, 2022 Author Share Posted December 8, 2022 You don't. Warnings have to be ignored on a case by case basis. After you ignore it once, it should never appear again. Quote Link to comment
NAS Posted December 8, 2022 Share Posted December 8, 2022 Could I request an option to bypass this feature completely please. This would be a real quality of life improvement for compose users. Quote Link to comment
OsoPolar Posted December 9, 2022 Share Posted December 9, 2022 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 ? Quote Link to comment
ljm42 Posted December 9, 2022 Share Posted December 9, 2022 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 Quote Link to comment
Squid Posted December 9, 2022 Author Share Posted December 9, 2022 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 Quote Link to comment
Squid Posted December 10, 2022 Author Share Posted December 10, 2022 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 3 Quote Link to comment
rjorgenson Posted December 12, 2022 Share Posted December 12, 2022 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 [email protected]:/boot/config/ssl/certs# openssl x509 -noout -text -in mnemos_unraid_bundle.pem | grep "Subject: CN" Subject: CN = *.rendezvous.agffa.net [email protected]:/boot/config/ssl/certs# and my local TLD also appears to be correct I am still on unRAID 6.9.2 if that matters. Quote Link to comment
ljm42 Posted December 12, 2022 Share Posted December 12, 2022 13 hours ago, rjorgenson said: FCP recently started warning me that But my subject CN appears to be set correct for a wildcard [email protected]:/boot/config/ssl/certs# openssl x509 -noout -text -in mnemos_unraid_bundle.pem | grep "Subject: CN" Subject: CN = *.rendezvous.agffa.net [email protected]:/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? Quote Link to comment
rjorgenson Posted December 12, 2022 Share Posted December 12, 2022 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. [email protected]:~# openssl x509 -noout -subject -nameopt multiline -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | sed -n 's/ *commonName *= //p' *.rendezvous.agffa.net [email protected]:~# 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 [email protected]:~# 1 Quote Link to comment
ljm42 Posted December 12, 2022 Share Posted December 12, 2022 6 minutes ago, rjorgenson said: This is a wildacard cert provided by letsencrypt. Here is the output of those two commands. [email protected]:~# openssl x509 -noout -subject -nameopt multiline -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | sed -n 's/ *commonName *= //p' *.rendezvous.agffa.net [email protected]:~# 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 [email protected]:~# 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? Quote Link to comment
rjorgenson Posted December 12, 2022 Share Posted December 12, 2022 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 Quote Link to comment
ljm42 Posted December 12, 2022 Share Posted December 12, 2022 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 Quote Link to comment
rjorgenson Posted December 13, 2022 Share Posted December 13, 2022 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? Quote Link to comment
ljm42 Posted December 13, 2022 Share Posted December 13, 2022 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? Quote Link to comment
rjorgenson Posted December 13, 2022 Share Posted December 13, 2022 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. 1 Quote Link to comment
Waoji Posted December 13, 2022 Share Posted December 13, 2022 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. Quote Link to comment
trurl Posted December 13, 2022 Share Posted December 13, 2022 Have you cleared browser cache? Quote Link to comment
Squid Posted December 13, 2022 Author Share Posted December 13, 2022 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 Quote Link to comment
gemeit Posted December 13, 2022 Share Posted December 13, 2022 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 Quote Link to comment
Squid Posted December 14, 2022 Author Share Posted December 14, 2022 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. 1 Quote Link to comment
Forty Two Posted December 15, 2022 Share Posted December 15, 2022 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? Quote Link to comment
Squid Posted December 15, 2022 Author Share Posted December 15, 2022 Are you sure about that? Have you done a rescan since you switched (or has another scan been run) Quote Link to comment
Recommended Posts
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.