ANIMATEK

Yeah that's true, I do get irritated when I see update available though. But in that case I could run it with AppData Backup and call it a day. I will see, thanks for the input.

Hello there, My server stopped working yesterday and I had to manually reboot it. Today it happened again, but after around 15m not responding, it came back to life. The symptoms were: - WebUI and SSH time out - Dockers not available - Ping works fine I activated the syslog after this last incidence (so for next time), but as the server wasn't rebooted, I took the the diagnostics right after I could log-in again. unraid-diagnostics-20240227-0818.zip The issue happened almost exactly at 8AM, when the Auto Update Apps tries with Docker. I don't know if it's related, but I have deactivated it now, see if it happens tomorrow. Unfortunately I cannot make much sense of the logs, so any help here will be greatly appreciated. Thanks in advance.

Thank you, the cron expression was completely wrong. I want it more like 0 8-15 * * *

I think the theme is putting you off. Those are indeed the settings for Docker (check "Time to wait for graceful stop before killing", which is only in Docker)

I am having trouble figuring out why my containers are not updating. Unfortunately, it is quite hard to search in this huge thread (or I don't know how). I looked around but I don't even know where the logs for the plug-in are. I am clueless. I attached my config but it is so simple I don't know what can be wrong. I also already reinstalled the plug-in. If I go to the Docker page I might see 1 or 2 that say "apply update". If I click search, almost always something comes up (I have a container that gets a new push everyday at around 8AM). The plug-in seems to not be working at all. Can someone give me hand?

So Wachtower is not good for Unraid at all, I am using now the Auto Update plugin (not a Container) and it works way better. As a bonus feature, it can also update other plugins and notify you when a OS update is available. It is dumb considering that Watchtower is the most downloaded Container.

@Squid Hey sir would you mind acknowledging this? I opened the post exactly as you requested in the other thread. It is a consistent issue that it's there all the time, so I would be cool to know if somebody is looking at it. Thank you.

For those coming here, I just re-opened the issue.

This is kinda re-opening the following thread: I have this problem in 6.12.3 too. It happens with many containers and not just from LSIO. I do have Watchtower installed, I don't know if it matters. Edit: Diagnostics added. unraid-diagnostics-20230717-1053.zip

Found it /boot/config/plugins/dockerMan/templates-user

Did you find what you were looking for?

The issue has been fixed in the update from yesterday. Happy nerding.

Exactly. I felt comfy in Linux but unRAID is another story. @fabricionaweb could you please elaborate on downgrading python? Thank you!

Well it's me again with a new problem... It seems that Python3.9 does not support the OpenSSL 1.1.1? This is what is installed between Unraid and NerdTools and unfortunately I cannot change it. This message is basically what I get when running the script that I want: Script location: /tmp/user.scripts/tmpScripts/install_qbt_api/script Note that closing this window will abort the execution of this script WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available. WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/qbittorrent-api/ WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/qbittorrent-api/ WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/qbittorrent-api/ WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/qbittorrent-api/ WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/qbittorrent-api/ Could not fetch URL https://pypi.org/simple/qbittorrent-api/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/qbittorrent-api/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping ERROR: Could not find a version that satisfies the requirement qbittorrent-api (from versions: none) ERROR: No matching distribution found for qbittorrent-api WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available. Could not fetch URL https://pypi.org/simple/pip/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/pip/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping WARNING: There was an error checking the latest version of pip. Googling the error tells me to update OpenSSL and try again, which I cannot do? Any new idea? It seems that I am stuck. Thanks in advance.

(thank you that fixed it)