I ran this command: certbot certonly --manual --preferred-challenges dns -d xxx.ethz.ch
It produced this output: Please deploy a DNS TXT record under the name
My web server is (include version): none
The operating system is (include version): windows server 2022, no webserver, rdp connection should be covered by the ssl cert.
My hosting provider, if applicable, is: internal
I can login to a root shell on my machine (yes or no, or I don't know): yes
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 2.6.0
Is it possible with certbot on windows to generate a certbot certonly --manual --preferred-challenges dns with an internal acme-dns challenge, but how i specify that internal acme-dns challenge url?
So i know the details of the acme-dns like username, password and subdomaine
If cerbot is not the right way hows going true win-acme?
Certify The Web Nice, looks good, i'l give them a try.
So there i could select dns challenges from a list like, azure, ovh and so on.
So thats what we have internal but i don't know how to use that with certbot or another way to generate letsencrypt ssl certs, for linux we have a tutorial an use acme.sh
We refer to the letsencrypt as CA Server.
A lot but i don't know which one i should choose.
A may i can use (Use Custom Script)
So for authorization settings > DNS Update Method: (Use Custom Script)
Or may i ask our internal people to get on that list.
There shouldn't be "a lot". If I look at the Certify source code it defaults to a single value, but should be able to enter your own.
I have no idea where you're looking, so answers as "a lot" doesn't really help. Maybe you could make a screenshot of where you're looking if you can't use words?
When you have your own acme-dns server you just provide the URL to the server. That's the same for certbot or Certify The Web.
In Certify The Web, select acme-dns as your DNS provider, just enter the url. If that's not working for some reason please do let me know. If you have somehow pre-registered a domain with an acme-dns instance you can also provide the existing credentials in JSON format.
Certify DNS is a managed acme-dns style service, so you don't need that if you are hosting your own acme-dns instance.
For certificate validation to work your "internal" acme-dns service needs to be available on the public internet over TCP/UDP port 53, otherwise Let's Encrypt can't follow the CNAME to check it.
If your server is on the public internet you can just use the (very easy) http-01 validation option and open port 80, you don't need to have a web server installed as the app will answer the http challenge for you
So there you have to create an API toke from your account and then you reference to the API and Secret and customer key, so we have that in a similar way, we could create unique entries for every subdomaine like acme-username, password and subdomaine then that infromation will handle over your intern acme-dns servers as we have a lot of firewalls and so we don't wan't to add for every requested letsencrypt ssl cert an txt to teach subdomaine and open port 80. We could do but why if we have an easier way to use.
Any chance to have a private talk with you (webprofusion) ? I also send an email to support@certifytheweb.com
The OVH example you pointed to says "acme-dns" in the name, but it's nothing to do with the acme-dns standard, which is a type of DNS server built only to answer acme DNS challenges.
