Letsencrypt in docker Container and ddns.net instead duckdns

Hello community

I hope you can help me with my problem. I try to install nextcloud on my Raspberry pi4 and have docker and docker composer on it. I have taken the docker compose file from your site. There under SWAG only duckdns is mentioned and the token. But I don‘t know how to use my NoIP domain *.ddns.net??

When I install the containers nextcloud MariaDB and letsencrypt are running but letsencrypt has the following error:


-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \ 
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
-------------------------------------

To support the app dev(s) visit:
Certbot: https://supporters.eff.org/donate/support-work-on-certbot

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1000
User gid:    1000
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing... 
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing... 
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 50-config: executing... 
Variables set:

0

0
TZ=Europe/Berlin
URL=neno.ddns.net
SUBDOMAINS=wildcard
EXTRA_DOMAINS=
ONLY_SUBDOMAINS=false
VALIDATION=noip
DNSPLUGIN=
EMAIL=
STAGING=

SUBDOMAINS entered, processing
Wildcard cert for neno.ddns.net will be requested
No e-mail address entered or address invalid
http validation is selected
Generating new certificate
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Requesting a certificate for *.neno.ddns.net and neno.ddns.net
Performing the following challenges:
Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. You may need to use an authenticator plugin that can do challenges over DNS.
Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. You may need to use an authenticator plugin that can do challenges over DNS.
ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container

The config is this:


---
version: "2"
services:
  nextcloud:
    image: linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Berlin
    volumes:
      - /media/NVMe_1TB/appdata/nextcloud/config:/config
      - /media/NVMe_1TB/appdata/nextcloud/data:/data
    depends_on:
      - mariadb
    restart: unless-stopped
  mariadb:
    image: linuxserver/mariadb
    container_name: mariadb
    environment:
      - PUID=1000
      - PGID=1000
      - MYSQL_ROOT_PASSWORD=nc29979
      - TZ=Europe/Berlin
    volumes:
      - /media/NVMe_1TB/appdata/mariadb:/config
    restart: unless-stopped
  letsencrypt:
    image: linuxserver/letsencrypt
    container_name: letsencrypt
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Berlin
      - URL=neno.ddns.net
      - SUBDOMAINS=wildcard
      - VALIDATION=noip
    volumes:
      - /media/NVMe_1TB/appdata/letsencrypt:/config
    ports:
      - 443:443
      - 82:80
    restart: unless-stopped

You can’t just just make up a random value for the VALIDATION var like noip.

All the available options are listed in the readme.

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.