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. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
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
My web server is (include version): Unraid 6.6.6
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know): I think so
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
Visiting cdkauffmannnextcloud.duckdns.org appears to be routed to your modem/router's web administration, rather than the web server on your computer/server.
You may need to make some changes to your port forwarding or your modem/router's web admin port in order to achieve the effect you want.
The / sends 401, but the important file in /.well-known/acme-challenge sends a 404.
Your header:
Server: micro_httpd
How did you create your certificate request? This is a small http server. But your ACME-client must be able to create a file under /.well-known/acme-challenge.
I had this issue resolved it by updating the directory of the website within the file /etc/letsencrypt/renewal/yourwebname.conf - specifically under the section [[webroot_map]] - make sure this directory is the the same for your .conf file within /etc/apache2/sites-available for the website you are renewing for.
The reason this wasn’t correct for me initially on the renewal was because I moved my websites directory and forgot about it. When it came up for renewal it didn’t go through. I then realised the problem, updated the [[webroot map]] and hey bingo the renewal went through. After updating the conf files remember to restart apache.
This is what you see on this file - and at the bottom is what I needed to change. It was different from the websites directory that I was using in my .conf file for the websites directory. They needed to be mapped correctly in order for the renewal to go through. (restart after changing and try renewing again)
Domain: server.cdkauffmann.com
Type: None
Detail: DNS problem: NXDOMAIN looking up A for server.cdkauffmann.com **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**
Do you control that domain? It’s registered, but are you the registrant, or do you otherwise control it?
To use HTTP validation, you need to add DNS records for those hostnames at the domain’s DNS provider, GoDaddy. (A and/or AAAA records, or CNAME records pointing at something else, like your DuckDNS hostname.)
Oh! They exist, but names aren’t quite right. I’m sorry I didn’t check for that.
GoDaddy implicitly adds “.cdkauffmann.com” to the end, so creating a record called e.g. “nextcloud.cdkauffmann.com” results in “nextcloud.cdkauffmann.com.cdkauffmann.com”.
(Different DNS services expect people to enter information in different ways, and often they don’t explain it.)
So you need to rename them from e.g. “nextcloud.cdkauffmann.com” to just “nextcloud”.
You already have a “www” record, pointing indirectly at GoDaddy’s domain parking service, so you have to delete that “www” record before renaming “www.cdkauffmann.com” to “www”.
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.
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
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.
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
All of your domains have their DNS pointed to GoDaddy’s domain parking page … get rid of the very first record that’s shown in the screenshot you posted earlier.
right now, only the WWW returns any IP.
The rest are “empty”/“null”.
You might want to lower those 14400s to something much smaller - until you get this figured out.
o 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.
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
Cleaning up challenges
Failed authorization procedure. sonarr.cdkauffmann.com (http-01): urn:ietf:params:acme:error:unknownHost :: The server could not resolve a domain name :: No valid IP addresses found for sonarr.cdkauffmann.com, nextcloud.cdkauffmann.com (http-01): urn:ietf:params:acme:error:unknownHost :: The server could not resolve a domain name :: No valid IP addresses found for nextcloud.cdkauffmann.com, server.cdkauffmann.com (http-01): urn:ietf:params:acme:error:unknownHost :: The server could not resolve a domain name :: No valid IP addresses found for server.cdkauffmann.com
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.
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