Hi, i get the following error-message:
Failed authorization procedure. exmaple.com (dvsni): unauthorized :: The client lacks sufficient authorization :: Correct zName not found for TLS SNI challenge
- The following 'unauthorized' errors were reported by the server:
Error: The client lacks sufficient authorization
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address.
Any idea, what i should change?
This is the way how Let’s Encrypt verifies that you are the owner of the server. In other words the IP address you are requesting the certificate from must match DNS (A type) record for the used domain in the request. I guess the 188.8.131.52 (example.com) address is not yours server address.
Hope it helps,
maybe webrrot/manual mode helps, with that you have to put some text at a certain url of your webserver and press enter after you did that.
I’m not positive but it seems that it’s not the way the LE developers see the world. I noticed that they tend to keep 90 days renewal period BUT with possibility of automated procedure. That’s why I think is a must to generate the certs at the server.
well they want automation that is stuff i know but IT’S NOT POSIBLE for all the types of systems and servers there are to make a completely flawless automation without any errors. also m stuff isnt supported yet so I have to do manual…
also manual mode isnt the way LE devs want it but it works, I did that yesterday so I know.
So does it mean that you were able to generate the cert on remote/other server? Can you share how?
didn´t know whats wrong
that is the DNS Record lookup: http://viewdns.info/dnsrecord/?domain=user-agents.me
any ideas, what i should add?
could you try the manual mode as per my last post?
Mmh, ok tried it and the certification was created.
But is this the right way to do it?
So in the default situation your request should reach to LE servers from 184.108.40.206 IP address. Can you confirm if you reach https://www.whatismyip.com/ from the server you can see 220.127.116.11?
The manual mode that ‘mentor’ mentioned might be a good workaround for you.
Mhh anyway nginx is blocking my check. Workaround has helped.
But the next problem is still here. Integration in Plesk.