Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
While we wait for your answer... I see that HTTP+S connections are being refused:
curl -Ii http://edadamvpn.duckdns.org/
curl: (7) Failed to connect to edadamvpn.duckdns.org port 80 after 14715 ms: Connection refused
curl -Ii https://edadamvpn.duckdns.org/
curl: (7) Failed to connect to edadamvpn.duckdns.org port 443 after 120 ms: Connection refused
Ok, we can help you get a cert for that.
The simplest way is to use HTTP authentication to validate the FQDN and obtain a cert.
For that, you will need to open HTTP [TCP port 80] through the firewall(s).
Then run the ACME client in standalone mode.
ANotWorking
Error
edadamvpn.duckdns.org has an A (IPv4) record (193.160.96.194) but a request to this address over port 80 did not succeed. Your web server must have at least one working IPv4 or IPv6 address.
Get "http://edadamvpn.duckdns.org/.well-known/acme-challenge/letsdebug-test": dial tcp 193.160.96.194:80: connect: connection refused
Trace:
@0ms: Making a request to http://edadamvpn.duckdns.org/.well-known/acme-challenge/letsdebug-test (using initial IP 193.160.96.194)
@0ms: Dialing 193.160.96.194
@28ms: Experienced error: dial tcp 193.160.96.194:80: connect: connection refused
IssueFromLetsEncrypt
Error
A test authorization for edadamvpn.duckdns.org to the Let's Encrypt staging service has revealed issues that may prevent any certificate for this domain being issued.
193.160.96.194: Fetching http://edadamvpn.duckdns.org/.well-known/acme-challenge/-mcBQArQi9yY6Ke9m6K2EMy6gDfg5wbtjnVA7xoti1M: Connection refused
The DNSSEC configuration is invalid. This will prevent users who are relying on validating DNS servers (e.g., Google DNS) to get any DNS responses for this domain name."