@1reason said in Unable to get cert with Namesilo:
With the manual method I pushed "issue" to get the text and then uploaded it to namesilo,
Then pause.
Tale a windows cmd prompt, or better, the pfSense console prompt, and do a simple check first :
Check if you have a sub domain called .well-known and a TXT record "/acme-challenge" for each ( ! ) of your domain name servers :
You'll get a list like :
ns3. your-domain.tld.
ns1. your-domain.tld.
ns2. your-domain.tld.
For each nsx, do :
dig @nsx.your-domain.tld.
dig .well-known.acme-challenge.your-domain.tld TXT
This should return the unique token that Letenscrypt gave you, the token you stored manually into the TXT record .well-known.acme-challenge.your-domain.tld
When you use the automatic mode the first (couple of) times, you should introduce a delay using acme.sh the "--dnssleep 300 " parameter.
This give you 5 minutes to test if the master DNS server, which was updated by the acme.sh API script, and if the slave DNS name servers have synchronised, as this is never been done 'right away'.
If this https://www.varstack.com/2017/12/08/Automating-HTTPS-certs/ is still valid and actual, then at least 15 minutes or 900 seconds are needed : you find it out during the manual 'dig' spam testing : as soon as the TXT record ".well-known.acme-challenge.your-domain.tld" pops up, you have the (average) delay.
@1reason said in Unable to get cert with Namesilo:
am repeating things over and over
You are testing using the LE test stage server, right ?
If not, LE will blacklist you for an hour, day or more.
