GreenLock3 error messages are not clear. #12

Nytt Ärende

Ghost · 2019-12-03T16:55:24Z

Ghost kommenterad

2019-12-03 16:55:24 +00:00

Hi. I use GreenLock3 within MeshCentral, and when my users post an error log, GreenLock3 reports an error with no details. For example, the log below (Originally posted here https://github.com/Ylianst/MeshCentral/issues/701) shows that GreenLock3 times out after one second exactly, but no indications as to why. The web server then gets the challenge requests.

If there is any way to get a more explicit error message, that would be most appreciated.

Thanks,
Ylian

$ node node_modules/meshcentral/ --debug cert,web,webrequest

MeshCentral HTTP redirection server running on port 80.

CERT: Initializing Let's Encrypt support, using GreenLock v3.1.5

CERT: Getting certs from local store

ACME Directory URL: https://acme-staging-v02.api.letsencrypt.org/directory

CERT: Notify: error: {"length":0}

CERT: Unable to get certs from local store (Staging)

MeshCentral v0.4.5-c, WAN mode.

MeshCentral Intel(R) AMT server running on meshcentral.xxxxx.com:4433.

MeshCentral HTTPS server running on meshcentral.xxxxx.com:443.

WEBREQUEST: /agent.ashx/.websocket

CERT: Checking certificate for meshcentral.xxxxx.com (Staging)

CERT: Notify: error: {"length":0}

CERT: Unable to get a certificate (Staging, 1004ms): [{"site":{"subject":"meshcentral.xxxxx.com","altnames":["meshcentral.xxxxx.com"]},"error":{"0":"e","1":"r","2":"r","3":"o","4":"r","length":5}}]

WEBREQUEST: /.well-known/acme-challenge/letsdebug-test (RedirServer)

CERT: Challenge meshcentral.xxxxx.com/letsdebug-test

WEBREQUEST: / (RedirServer)

WEBREQUEST: /.well-known/acme-challenge/yyyyyy(RedirServer)

CERT: Challenge meshcentral.xxxxx.com/yyyyyy

WEBREQUEST: /.well-known/acme-challenge/yyyyyy(RedirServer)

CERT: Challenge meshcentral.xxxxx.com/yyyyyy

WEBREQUEST: /.well-known/acme-challenge/yyyyyy(RedirServer)

CERT: Challenge meshcentral.xxxxx.com/yyyyyy

WEBREQUEST: /.well-known/acme-challenge/yyyyyy(RedirServer)

CERT: Challenge meshcentral.xxxxx.com/yyyyyy

Hi. I use GreenLock3 within MeshCentral, and when my users post an error log, GreenLock3 reports an error with no details. For example, the log below (Originally posted here https://github.com/Ylianst/MeshCentral/issues/701) shows that GreenLock3 times out after one second exactly, but no indications as to why. The web server then gets the challenge requests. If there is any way to get a more explicit error message, that would be most appreciated. Thanks, Ylian $ node node_modules/meshcentral/ --debug cert,web,webrequest MeshCentral HTTP redirection server running on port 80. CERT: Initializing Let's Encrypt support, using GreenLock v3.1.5 CERT: Getting certs from local store ACME Directory URL: https://acme-staging-v02.api.letsencrypt.org/directory CERT: Notify: error: {"length":0} CERT: Unable to get certs from local store (Staging) MeshCentral v0.4.5-c, WAN mode. MeshCentral Intel(R) AMT server running on meshcentral.xxxxx.com:4433. MeshCentral HTTPS server running on meshcentral.xxxxx.com:443. WEBREQUEST: /agent.ashx/.websocket WEBREQUEST: /agent.ashx/.websocket CERT: Checking certificate for meshcentral.xxxxx.com (Staging) CERT: Notify: error: {"length":0} CERT: Unable to get a certificate (Staging, 1004ms): [{"site":{"subject":"meshcentral.xxxxx.com","altnames":["meshcentral.xxxxx.com"]},"error":{"0":"e","1":"r","2":"r","3":"o","4":"r","length":5}}] WEBREQUEST: /.well-known/acme-challenge/letsdebug-test (RedirServer) CERT: Challenge meshcentral.xxxxx.com/letsdebug-test WEBREQUEST: / (RedirServer) WEBREQUEST: /.well-known/acme-challenge/yyyyyy(RedirServer) CERT: Challenge meshcentral.xxxxx.com/yyyyyy WEBREQUEST: /.well-known/acme-challenge/yyyyyy(RedirServer) CERT: Challenge meshcentral.xxxxx.com/yyyyyy WEBREQUEST: /.well-known/acme-challenge/yyyyyy(RedirServer) CERT: Challenge meshcentral.xxxxx.com/yyyyyy WEBREQUEST: /.well-known/acme-challenge/yyyyyy(RedirServer) CERT: Challenge meshcentral.xxxxx.com/yyyyyy

Logga in för att delta i denna konversation.

Ingen Etikett

Ingen Milsten

Ingen tilldelad

1 Deltagare

Notiser

Förfallodatum

Förfallodatumet är ogiltigt eller utanför gränserna. Använd formatet 'åååå-mm-dd'.

Inget förfallodatum satt.

Beroenden

No dependencies set.

Reference: root/greenlock.js#12