Suggestion - can we somehow disable any alerts related to Nextcloud-aio-* for updates?

 

Because the AIO master container is the one handling the updates, unraid thinks there's always an update avaialble for these 10 containers on my system (others may have more) but they for sure all start with nextcloud-aio-* -- the only one that IS managed by unraid is nextcloud-aio-mastercontainer

 

It would be nice if we had a way to not have to manually ignore each of the 10, and either have these auto-ignored by fix common problems, or a checkbox to ignore items matching a text string, so we could put in "nextcloud-aio-" as the string or something? 

 

Just thinking out loud here  

 

Edited December 5, 20241 yr by CorneliousJD

4 hours ago, CorneliousJD said:

or a checkbox to ignore items matching a text string, so we could put in "nextcloud-aio-" as the string or something? 

The problem then would be that you want "nextcloud-aio-mastercontainer" which also would give you a match to your ignore string.

 

The real problem is that UNRAID says "ready for update" on these containers but if you ask to update it says "no configuration found, cannot update".

 

So this plugin better should check for the docker config.

 

Strange issue I'm seeing here on two on my Unraid boxes, post-upgrade to 7.0.0-rc1.  In fix common problems, this error pops constantly.  Occasionally (very, very rarely) it will disappear upon rescan only to come back a short while later.  Has never happened before on either Unraid system, and happened on both of them immediately post-upgrade.

 

 

Nothing network-wise has changed (on my LAN or within either Unraid box), and NIC settings are set identically to everything else on my LAN that works as expected:

 

 

Furthermore, I can ping github.com just fine from the shell on both boxes...

 

I've tried playing around with some advance options under Settings > Docker but nothing I've changed has made any difference.  Diagnostics are attached.  Thoughts on what I could be missing here and/or is anyone else seeing this issue?

unraid01-diagnostics-20241204-1508.zip

Did you try the suggestion it offered and set the DNS address in Settings - Network settings?

Doing that did make it go away on one of my servers, which would indicate a dns resolution failure/block using 192.168.1.1...but it has gone away temporarily before after messing with stopping and restarting the docker service so time will tell if it's actually permenant.  It also causes a name resolution error to pop due to not being able to resolve my internal fqdn that I have set in settings....so that doesn't really work unfortunately.

 

In any case, the bigger questions I'd have would be how that explains it suddenly happening with both servers immediately after upgrade, and more importantly why I can resolve github.com just fine from the shell?  What am I misunderstanding about what/how that step is performing it's check?  Thoughts?

 

EDIT: For what it's worth, using the normal 192.168.1.1 firewall address (like everything else in my network does) I can see github DNS entries hitting and being allowed just as expected:

Is there somewhere I can view the raw log of exactly what is being attempted when this check is performed so I can try to figure out why this is failing?  I've tried poking around the github source but I'm clearly looking in the wrong spot...and scoping my DNS logs specifically to blocked I'm finding nothing failing.

Edited December 5, 20241 yr by d.ohlin

I don't have all of the answers unfortunately.   FCP (and CA, along with installation and checks for updates for plugins) use standard cURL requests, and for some reason on people's networks using the router to resolve the DNS simply sucks.  Especially if you've never adjusted the router to use "real" DNS servers eg openDNS (208.67.222.222 / 208.67.220.220) and not the ISP's default values.

 

16 hours ago, MAM59 said:

So this plugin better should check for the docker config.

 

FCP reports what docker tell it.  Not having the config file (the template) is not the issue, as nothing says you have to have a config file.

7 hours ago, Squid said:

Not having the config file (the template) is not the issue, as nothing says you have to have a config file.

I cannot really agree. The config file contains the "wanted" release (mostly "latest").

Without a config UNRAID does not know which version you are requesting.

Thats why it gives up if you try to update manually.

So the lack of a config surely shows that no update is possible (from within UNRAID. Nextcloud AIO has its own docker for backups and doing updates).

 

Hi all,

 

I just ran this plugin and got an error of a "possible hack attempt":

 

___

On Dec 15 there were 866 invalid login attempts. This could either be yourself attempting to login to your server (SSH / Telnet) with the wrong user or password, or you could be actively be the victim of hack attacks. A common cause of this would be placing your server within your routers DMZ, or improperly forwarding ports.

 

This is a major issue and needs to be addressed IMMEDIATELY

 

NOTE: Because this check is done against the logged entries in the syslog, the only way to clear it is to either increase the number of allowed invalid logins per day (if determined that it is not a hack attempt) or to reset your server. It is not recommended under any circumstance to ignore this error  More Information

___

 

The "More Information" link told me to post this error and my Diagnostics file (attached) here.  

 

Does anyone know what this could be about?

 

If it helps, I use my unRaid mainly to host Plex, and a day or so ago my Plex docker stopped working.  I am still trying to figure out why (current guess is that my Plex db got corrupted during a docker update), but that issue is why I ran the "fix common problems" app in the first place.   

 

Any help is much appreciated!

freemanbox-diagnostics-20241215-1056.zip

Is your server sitting in your router's DMZ?  You do have 800+ login attempts from around the world.  Pretty much every script kiddie out there.

1 hour ago, Squid said:

Is your server sitting in your router's DMZ?  You do have 800+ login attempts from around the world.  Pretty much every script kiddie out there.

 

Sorry for the noob question, but how do I check this?  

Depends upon your router.  Log into it and check for DMZ akin to

 

Placing your server within a DMZ effectively puts the server directly on the internet, and is not recommended.  Forward ports instead.  Another possibility is that you've forwarded the SSH / SSL ports in which case you should use a reverse proxy (or ideally once 7.x is released TailScale)

After investigating a recent issue I had with SMART read errors on a Parity drive (caused by a power outage) I cleared the error in the UnRaid UI but cannot get the warning to disappear from FCP.  Other than 'IGNORE ERROR' how can I clear this in FCP?  The FCP warning is 'parity2 (ST12000NM0008-2H3101_ZL0033AV) has read errors'

 

Thanks in advance!

 

Edited December 18, 20241 yr by Green Dragon

Anyone seeing FCP's scan get stuck after the update to 6.12.14? I'm on the plugin page, looking at the 'Scanning. Now Scanning your system for common problems. This may take a minute' popup and it's been doing nothing for a long while now. Never took this long before.

 

TIA

 

EDIT: disregard, fixed with a reboot. I shall watch The IT Crowd in shame tonight.

Edited December 19, 20241 yr by thatsthefrickenlightning

I keep getting a notification for “wrong DNS entry” which is a false positive but I don’t see anywhere in Settings/FCP to ignore this error. The warning isn’t shown there at all.

On 12/22/2024 at 6:56 AM, wgstarks said:

I keep getting a notification for “wrong DNS entry” which is a false positive but I don’t see anywhere in Settings/FCP to ignore this error. The warning isn’t shown there at all.

 

  Can you show me a screenshot of the notification.  And include your diagnostics

51 minutes ago, Squid said:

 

  Can you show me a screenshot of the notification.  And include your diagnostics

 

 

brunnhilde-diagnostics-20241223-0957.zip

 

I was wrong that the warning didn’t appear in settings (2nd screenshot). Not sure how I missed it.😳

It is false though. All the machines on my local network use my pfsense router for primary DNS. If I browse to Brunnhilde.dahoney.me from any machine on my local network I get the Unraid login screen rather than the IPMI login which is at 10.0.1.22. I’ll just ignore the warning for now.

 

I did tweek the DHCP reservations in pfsense. Maybe it takes a while for FCP to see the changes?

13 minutes ago, wgstarks said:

Maybe it takes a while for FCP to see the changes?

This appears to be the case. After a short wait and re-enabling the warning it doesn’t show on a rescan.

@ljm42  ^^^ Thoughts on the posts from @wgstarks?

system says there is an update to "Fix Common Problems"

Installed Version2024.12.04

Upgrade Version2024.12.19a

 

but when I run the update i get this message:

 

plugin: updating: fix.common.problems.plg
Executing hook script: pre_plugin_checks

+==============================================================================
| Skipping package fix.common.problems-2024.12.04-x86_64-1 (already installed)
+==============================================================================


----------------------------------------------------
fix.common.problems has been installed.
Copyright 2016-2024, Andrew Zawadzki
Version: 2024.12.04
----------------------------------------------------

plugin: fix.common.problems.plg updated
Executing hook script: gui_search_post_hook.sh
Executing hook script: post_plugin_checks

 

 

Just wanted to make you aware as I am sure a line of code was missed.

Try it again in about 5 minutes

I would like to get some help with this alert from "Fix Common Problems"

 

I have removed an old Pool by the name qbittorrent, after that this alert appeared. I have tried too reboot, to see if that would remove it from /mnt, but its still there.

 

What can I do too fix this alert?

nollemania-diagnostics-20241228-0046.zip

20 hours ago, Nolle said:

What can I do too fix this alert?

 

Look for a docker container which is referencing /mnt/qbittorent.  It will wind up recreating it and causing the error

Thanks for the solution. That fixed my problem. Very much appreciated.

When I tried to upgrade from 2024.12.19 to 2024.12.19a, I saw this message:

Update Plugin

plugin: updating: fix.common.problems.plg
Executing hook script: pre_plugin_checks
plugin: XML file doesn't exist or xml parse error
Executing hook script: post_plugin_checks

 

And now it is stuck as pending.

Edited December 31, 20241 yr by mhorn