letsencrypt.sh for hostname certificate gives email error

Zephyron

New member
Joined
Apr 11, 2017
Messages
1
I've updated DA and the letsencrypt binaries and certificates seem to work well using the gui in the users control panel, but when trying to letencrypt.sh script to create a certificate for the server, I get the following:

Code:
User let's encrypt key has been found, but not registered. Registering...
Account registration error. Response: HTTP/1.1 100 Continue
Expires: Tue, 11 Apr 2017 17:47:56 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache

HTTP/1.1 400 Bad Request
Server: nginx
Content-Type: application/problem+json
Content-Length: 107
Boulder-Request-Id: 1wFVdJoVLGzmN9oBEsazdjOUNzNnijc1BZrdV4eEjYc
Replay-Nonce: oCqlFrqYB0nT5y3Th3sE2jYsM_FPnl7ZE430eSzReJk
Expires: Tue, 11 Apr 2017 17:47:56 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 11 Apr 2017 17:47:56 GMT
Connection: close

{
  "type": "urn:acme:error:invalidEmail",
  "detail": "Error creating new registration",
  "status": 400
}.
I know that when requesting certificates on the user's control panel, an email address is required. Could this be what's causing the error here and if so, how do I set the address to be used by the script?
 

ger64

Verified User
Joined
Apr 18, 2017
Messages
5
Exactly the same Error Message at Request Let's Encrypt

i have exactly the same Error at request.


I've updated DA and the letsencrypt binaries and certificates seem to work well using the gui in the users control panel, but when trying to letencrypt.sh script to create a certificate for the server, I get the following:

Code:
User let's encrypt key has been found, but not registered. Registering...
Account registration error. Response: HTTP/1.1 100 Continue
Expires: Tue, 11 Apr 2017 17:47:56 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache

HTTP/1.1 400 Bad Request
Server: nginx
Content-Type: application/problem+json
Content-Length: 107
Boulder-Request-Id: 1wFVdJoVLGzmN9oBEsazdjOUNzNnijc1BZrdV4eEjYc
Replay-Nonce: oCqlFrqYB0nT5y3Th3sE2jYsM_FPnl7ZE430eSzReJk
Expires: Tue, 11 Apr 2017 17:47:56 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 11 Apr 2017 17:47:56 GMT
Connection: close

{
  "type": "urn:acme:error:invalidEmail",
  "detail": "Error creating new registration",
  "status": 400
}.
I know that when requesting certificates on the user's control panel, an email address is required. Could this be what's causing the error here and if so, how do I set the address to be used by the script?
 

ger64

Verified User
Joined
Apr 18, 2017
Messages
5
In fact - I got this ...

[root@xxx1 scripts]# ./letsencrypt.sh request serverx.xxx.xx 4096
Setting up certificate for a hostname: serverx.xxx.xx
Getting challenge for serverx.xxx.xx from acme-server...
User let's encrypt key has been found, but not registered. Registering...
Account registration error. Response: HTTP/1.1 100 Continue
Expires: Tue, 18 Apr 2017 07:11:35 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache

HTTP/1.1 400 Bad Request
Server: nginx
Content-Type: application/problem+json
Content-Length: 107
Boulder-Request-Id: YtEMqAHOUNGDyiNlU3VdoAT0CJw_HBT7f4GtL5tYlSw
Replay-Nonce: SNfE-fac3TJaKbusbX_RSsbt2eB37vRh7rSJThgf2x1U
Expires: Tue, 18 Apr 2017 07:11:37 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Tue, 18 Apr 2017 07:11:37 GMT
Connection: close

{
"type": "urn:acme:error:invalidEmail",
"detail": "Error creating new registration",
"status": 400
}.
 

ger64

Verified User
Joined
Apr 18, 2017
Messages
5
Alternative

I have installed another free (en simpel) certificate at the DirectAdmin login 2222 page.

And succeded imidiately.

See: https://www.sslforfree.com

Very easy (and for 3 months).

Maybe a tip for other admins.
 

ger64

Verified User
Joined
Apr 18, 2017
Messages
5
Resolved

Well, just to let you know ...

I have rebuild the server with DirectAdmin, updated CentOS7, DirectAdmin etc and at the very beginning of the adjustments (DNS and nameservers were already resolved) …

Situation (last time)
Started with:

web10.domain.tld
domain.tld was in the beginning under the Admin > User Level.
And the errors came with processing asking LetsEncrypt SSL.
other domain (in an individual reseller account), outside admin: No problem. Succeeded.

- - -

Situation now:

web10.domain.tld
domain.tld was in the beginning under the Admin > User Level.
and stayed there.
Asked for LetsEncrypt SSL and yes, the output was succeeded.

So Conclusion?
Maybe not a good idea to put the domain.tld (from the web.domain.tld) outside the Admin > User Level.

Maybe this is the answer for some DirectAdmin webmaster who search the solution?

Thanks
 

Webbera

Verified User
Joined
May 26, 2017
Messages
6
Hello ;)

I had same problem with lets encrypt I solve it by deleting deleting all let's encrypted files and then I build it again with custom build ;)

Also there can be problem if you are running it with live server that you reach maximum numbers of SSL per hour so you can check it later.
 

ayeweb

Verified User
Joined
Nov 27, 2016
Messages
61
My hosting provider solved this, But i don't know how... :confused:
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
4,216
Location
Maastricht
Check it out, sslforfree is also generating Letsencrypt. It's more secure to let your own server do it then some external domain.
So I would advise against this tip.
 
Top