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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: yourfuturetosuccess.com
I ran this command: I ran these commands in Step 4 and chose Option 3. DNS Record Step 4: Verify Ownership
PRIV_KEY=./account.key; echo -n "eyJ1cmwiOiJodHRwczovL2FjbWUtdjAyLmFwaS5sZXRzZW5jcnlwdC5vcmcvYWNtZS9hdXRoei8zMTExMDQzMTkyLzY2ODI1MjMwMDcwMiIsImFsZyI6IlJTMjU2Iiwibm9uY2UiOiIxTHhJYW9KUlJ0ZV94VFFHbmtWTUNxajdKc0I5WkVBdkl3czBZdGpOeU5fSUFUY2NrVDAiLCJraWQiOiJodHRwczovL2FjbWUtdjAyLmFwaS5sZXRzZW5jcnlwdC5vcmcvYWNtZS9hY2N0LzMxMTEwNDMxOTIifQ." | openssl dgst -sha256 -hex -sign $PRIV_KEY
(stdin)= 899d69ed9eadd3339d42dddca55c345ff4d5bf644cdee0bf395c8366517fc379554783d55c8ec5e27db29f24694cb9c29920ce996a10cb38714ceb5af951cef47ee55b915e8865a766f25afd25044ba663ea5f868c8aa71cbba010a54745fb160e61eff52fe31a44914cfc54d7a056cdc15b3904f428470f95c36c2c1b16eed502d81ba879337ba0a9954f8a3c099f86ea3ee33e480afcddc3ae31d84a0749140209e892c8de7f0f12eb8b2b1a9012cc30e3fe4daed7edc267119c5b45b1b0ab8482fe7ea9d69fc70aee7e68cc11fa54a7c178acef7482c797d293fcceffb9fa3a88c9cd559bc179ec0cf7ac9e986d0a75d2893e6be506297b26492ae33dbcef
Challenges loaded! Choose a challenge option below.
Challenges for: ilo5-server.yourfuturetosuccess.com
Option 1 - python server Option 2 - file-based Option 3 - DNS record
How to set this DNS record:
- Log into your domain name provider.
- Create a new DNS record on ilo5-server.yourfuturetosuccess.com:
Type:
TXT
Name/Host/Alias:
_acme-challenge
Value/Answer/Destination:
o-9hqV6hs61pW_3K60EDN1Y_VJbOyaNjsKDlZrMz5yE
Time to Live (TTL):
900
- Wait until the TXT record is being served (this can take a while).
dig +short @ns.yournameserver.com _acme-challenge.ilo5-server.yourfuturetosuccess.com TXT
- Click "I can see the TXT record..." button when you can see that new TXT record has propagated.
I waited more than an hour and didn't see the TXT Record so I forced it in Godaddy by inputing the Value and the TXT appeared in in my DNS Record in Godaddy.
Easily verify domain ownership
Need to verify ownership of your domain to connect to an external service? We've made it easier than ever.
Verify Domain Ownership
(how do I do this?)Check challenge status command:
I ran the 2 Sign challenge commands: No errors
Then when I clicked on Check the challenge status I recieved the error below.
Error: Domain challenge failed. Please start back at Step 1. {"identifier":{"type":"dns","value":"ilo5-server.yourfuturetosuccess.com"},"status":"invalid","expires":"2026-03-11T19:16:54Z","challenges":[{"type":"dns-01","url":"https://acme-v02.api.letsencrypt.org/acme/chall/3111043192/668091815852/Isx3Ag","status":"invalid","validated":"2026-03-04T22:44:05Z","error":{"type":"urn:ietf:params:acme:error:dns","detail":"DNS problem: NXDOMAIN looking up TXT for _acme-challenge.ilo5-server.yourfuturetosuccess.com - check that a DNS record exists for this domain","status":400}
My web server is (include version): HPE ILO5
The operating system my web server runs on is (include version): Windows Server 2016 though I'm running the GetHTTPSforfree in Windows 11.
My hosting provider, if applicable, is: Not sure.
I can login to a root shell on my machine (yes or no, or I don't know): Don't know
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): I'm using Godaddy DNS Management.
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): Not using certbot. I'm using Git Bash
Hopefully all this makes sense and any help is always appreciated.
Eddie