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.
I ran this command:
acme.sh --log --force --staging --issue -d beacon.esva.net -d godsbeacon.com -d *.godsbeacon.com --dns myapi
It produced this output:
[Sun Oct 20 16:10:01 EDT 2019] Using stage ACME_DIRECTORY: https://acme-staging-v02.api.letsencrypt.org/directory
[Sun Oct 20 16:10:01 EDT 2019] Multi domain=‘DNS:beacon.esva.net,DNS:godsbeacon.com,DNS:.godsbeacon.com’
[Sun Oct 20 16:10:01 EDT 2019] Getting domain auth token for each domain
[Sun Oct 20 16:10:02 EDT 2019] Getting webroot for domain=‘beacon.esva.net’
[Sun Oct 20 16:10:02 EDT 2019] Getting webroot for domain=‘godsbeacon.com’
[Sun Oct 20 16:10:02 EDT 2019] Getting webroot for domain=’.godsbeacon.com’
[Sun Oct 20 16:10:02 EDT 2019] Error, can not get domain token entry *.godsbeacon.com
[Sun Oct 20 16:10:02 EDT 2019] The supported validation types are: dns-01 , but you specified: http-01
My web server is (include version):
apache 2.4
The operating system my web server runs on is (include version):
FreeBSD 11.3-RELEASE-p3 i386
My hosting provider, if applicable, is:
I manage my own servers
I can login to a root shell on my machine (yes or no, or I don’t know):
yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
No, doing it the hard way
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
I noticed that, about the dns-01 versus http-01 thing. I’m just now playing around with wildcards, so I’m pretty sure I haven’t gotten a wildcard cert with http-01. Also, deleting the records in .acme.sh doesn’t help. I tried it with a different domain, but that didn’t work either. So I tried it with a new domain I’ve never gotten any certificate for and that didn’t work either.
I’m sure I must be doing something wrong, but I can’t figure out what.
Check in ~/.acme.sh/beacon.esva.net/beacon.esva.net.conf . It may be loading pre-existing settings from there.
Edit: Oops, just saw you already tried that. Another idea: acme.sh can be a bit weird about parameter ordering. Could you move --dns myapi to the start of the command?