Fehler Meldung - Erstellen Zertifikat für DDNS

Guten tag,
Entschuldigt, aber Google übersetzt falsch und ich schreibe in Deutsch.

My sub.domain is: DNNS-Dienst ist erreichbar über Port 80 (möchte ich nicht öffentlich zeigen, aus Sicherheitsgründen, bis SSL funktioniert. Danke)

I ran this command: NGINX-Proxy-Manager -> SSL Zertifikat erstellen

It produced this output: CommandError: Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.

at /app/lib/utils.js:16:13
at ChildProcess.exithandler (node:child_process:430:5)
at ChildProcess.emit (node:events:524:28)
at maybeClose (node:internal/child_process:1104:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)

My web server is (include version): NGINX

The operating system my web server runs on is (include version): Raspberry IO Reales 6.0 10.2025

My hosting provider, if applicable, is: All.inkl.com

I can login to a root shell on my machine (yes or no, or I don't know): ja

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): Desktop Version mit Terminal

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): kann ich nicht sagen.

Ich bin nur ein Anwender, kein IT-Mensch und möchte das Zertifikat erstellen über NGINX-Manager-Proxy.
Log Datei ist nicht auf dem Raspberry in diesem Verzeichnis vorhanden?

Danke

OT: Fehler Ausgabe, stimmt der Inhalt Links nicht, man kommt auf ein Webhosting für Webseiten!

you need to log into that docker container itself and get log file /tmp/letsencrypt-log/letsencrypt.log itself
and inkl.com is new site:

2 Likes

Good morning,

The directory /tmp/letsencrypt-log/letsencrypt.log is empty, so I wrote here to ask whether something is missing or has not been created, as the error message refers to an extension, but I would say that it is included with NGINX (has been installed)?!

All.inkl.com is the host where DDNS is created to have forwarding to the IP address in the LAN.

The following is installed:

Docker

Docker Compose

NGINX Manager Proxy

Everything is running, but only port 80; therefore, I need port 443.

How do I get a log if none is stored in the directory? Thank you.

Regards, Hans

OT. Google Translate

Translated with DeepL.com (free version)

all.inkl.com is not resolve to anywhere and inkl.com is english news website: so where you get that?
and that dir won't in host system but in NPM docker, in ram as it's under /tmp . so you need to open shell into running npm and get file from inside, stopping container will delete log I guess

2 Likes

all-inkl.com is a popular hoster in germany, so i guess he is using this.

they offer something similar to dyndns

2 Likes

Das ist das Verzeichnis, in welchen die Logdatei liegen soll -
/tmp/letsencrypt-log/letsencrypt.log

oxxxx1@raspberrypi:/tmp $ ls
ssh-wiGjKgeJHYCv
systemd-private-ed58a7ecad2o482cada618242119bfc6-bluetooth.service-3ZAbGF
systemd-private-ed58a7ecad2o482cada618242119bfc6-ModemManager.service-KGRK5t
systemd-private-ed58a7ecad2o482cada618242119bfc6-polkit.service-DsFdMa
systemd-private-ed58a7ecad2o482cada618242119bfc6-systemd-logind.service-iCxDBt
systemd-private-ed58a7ecad2o482cada618242119bfc6-upower.service-GgCcvt

es gibt keinen Eintrag, wie weiter?

Grüße Hans

OT: über SSH eingeloggt als Root

that'd likely host's tmp: we want to look inside npm's own filesystem.

docker exec -it <container-id-or-name> /bin/bash
2 Likes

| \ | | __ ()_ __ __ | _ \ _ __ _____ ___ | / | __ _ _ __ __ _ __ _ ___ _ __
| | |/ | | '_ \\ \/ / |_) | '__/ _ \ \/ / | | | |\/| |/ _ | ' \ / |/ _ |/ _ \ '__|
| |\ | (
| | | | | |> <| __/| | | (
) > <| |
| | | | | (| | | | | (| | (| | __/ |
|
| _|_, ||| |//__| || _/_/_\, || ||_,|| ||_,|_, |___||
|/ |/ |___/
Version 2.12.6 (356eaa0) 2025-07-09 21:34:09 UTC, OpenResty 1.27.1.2, debian 12 (bookworm), Certbot certbot 4.1.1
Base: debian:bookworm-slim, linux/arm64
Certbot: nginxproxymanager/nginx-full:latest, linux/arm64
Node: nginxproxymanager/nginx-full:certbot, linux/arm64

Ich hoffe das es die richtige Information ist.
Grüße Hans

I think it'd in nginx-full:certbot node, I guess, npm really hides log

1 Like

Und wie bekomme ich nun eine Information, was im System hängt und den Fehler Ausgibt?

Grüße Hans

how knows, I'd persnally just use caddy if you are fine with running new thing

2 Likes