Problem with certificate

  • Hi. I have a problem with letsencrypt certificate for my nexctloud. When i type in url: https://mydomain.duckdns.org I receive a message which says: "This server could not prove that it is mydomain.duckdns.org; its security certificate is from *.mydomain.duckdns.org. This may be caused by a misconfiguration or an attacker intercepting your connection." I don't know why there is "*.". It is probably bad configuration of some config file, but I don't know which one. Any ideas?

  • You probably use duckdns as verification method. See the documentation of the letsencrypt/swag container:


    Quote
    • For duckdns validation, either leave the SUBDOMAINS variable empty or set it to wildcard, and set the DUCKDNSTOKEN variable with your duckdns token. Due to a limitation of duckdns, the resulting cert will only cover either main subdomain (ie. yoursubdomain.duckdns.org), or sub-subdomains (ie. *.yoursubdomain.duckdns.org), but will not both at the same time. You can use our duckdns image to update your IP on duckdns.org.
  • Yes exactly. So is there any way to fix that? If I use http validation method, I am getting an error:

    "Waiting for verification...,

    Challenge failed for domain mydomain.duckdns.org,

    Challenge failed for domain duckdns.org,"

  • I think problem is beacause my router is using port 80 and port forwarding is working only from the internet but is not working from LAN.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!