NextCloudPi - Problems with Letsencrypt

I’m trying to install NextCloudPi on my RaspberryPi 3B. Everything worked until i had to set the DDNS up. I’ve created a NOIP account and added it to my Router (Speedport Smart 3).
But when i press the Finish Button i get an error:

[ no-ip ]

Auto configuration for Linux client of

Only one host [pfaff. sytes. net] is registered to this account.
It will be used.

New configuration file ‘/usr/local/etc/no-ip2.conf’ created.

Failed to enable unit: Unit /run/systemd/generator.late/noip2.service is transient or generated.
System config value trusted_domains => 3 set to string pfaff. sytes. net
System config value overwrite.cli.url set to string https ://pfaff. sytes. net/
noip DDNS enabled

[ nc-autoupdate-ncp ]
automatic NextCloudPi updates enabled

[ dnsmasq ]
System config value trusted_domains => 2 set to string pfaff. sytes. net
System config value overwrite.cli.url set to string https ://pfaff. sytes. net/
dnsmasq enabled

[ letsencrypt ]
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for pfaff. sytes. net
Using the webroot path /var/www/nextcloud for all unmatched domains.
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. pfaff. sytes. net (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://pfaff. sytes. net/. well-known/acme-challenge/KW4bYiMkzzMdOtzc9XBJqwBplC5Q8EAs7DrMQmYa7xc: Timeout during connect (likely firewall problem)

  • The following errors were reported by the server:

    Domain: pfaff. sytes. net
    Type: connection
    Detail: Fetching
    https ://pfaff. sytes. net/. well-known/acme- challenge/KW4bYiMkzzMdOtzc9XBJqwBplC5Q8EAs7DrMQmYa7xc:
    Timeout during connect (likely firewall problem)

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.

I had to change the Domain because there where to much links in my post. The spaces are not the problem.

Can somebody help me?

Please post link via pastebin or similar of output of

sudo ncp-report

Looks like firewall issue, is port 80 forwarded?

If your router is handling the dynamic dns, you just need to forward port 80 and 443, and not have ncp try handle the ddns also. One or the other, but not both.

1 Like

Here’s the ncp-report:

The ports should be correct:

Try 443 instead of 433 :wink:

1 Like

Thank you, thats it -_-

searched the problem everywhere but not there…