Some type of error with my container as example
docker restart letsencrypt
WARNING: Error loading config file: /root/.docker/config.json: read /root/.docker/config.json: is a directory
but after few second the reply is
letsencrypt
so it is working?
Weird error: config.json: is a directory
-
- OMV 5.x
- Nefertiti
-
-
You probably have a typo in your config and thus created a folder instead of a file . Maybe you can post your run command, or docker-compose.yml. From that we can further investigate.
Greetings
David
-
Here some pics actually letsencrypt is running good.
You are right but witch config file is it?
-
From the screenshots it doesn't make any sense. However, delete your config.json folder, and run the command touch /root/.docker/config.json via the command execution or ssh. That will create is as a file. Test again then.
Greetings
David
-
I deleted the folder and SSH touch /root/.docker/config.json but after that same result. kind of, end of file.
-
What are you executing precisely in your cron?
Greetings
David
-
docker restart letsencrypt
since sometime only for omv and jellyfin got a blank login page
and
docker images -q --filter "dangling=true" | xargs -n1 -r docker rmi
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export SHELL=/bin/sh; sudo --shell --non-interactive --user=root -- docker
-
Can you show the config and logs of your letsencrypt container?
Greetings
David
-
Sorry for the delay was really busy lately
Code
Alles anzeigenletsencrypt.log <-------------------------------------------------> cronjob running on Sun Jul 26 02:08:00 PDT 2020 Running certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/XXXXXX.duckdns.org.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert not yet due for renewal - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The following certs are not due for renewal yet: /etc/letsencrypt/live/XXXXXXXXXX.duckdns.org/fullchain.pem expires on 2020-09-05 (skipped) No renewals were attempted. No hooks were run. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
That looks completely fine.
Does running it via the Webinterface still give an error?
Greetings
David
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!