Hello, just wondering how i should troubleshoot to find out why let's encrypt is not working for new sites? Standard ispconfig cron logs do not show anything Where should i look, or is there a verbose command line i can use to see any warnings/errors? Thanks..
Here is what the output is from debug... 2019-01-28 16:36:08,335EBUG:letsencrypt.cli:Root logging level set at 30 2019-01-28 16:36:08,336:INFO:letsencrypt.cli:Saving debug log to /var/log/letsencrypt/letsencrypt.log 2019-01-28 16:36:08,337EBUG:letsencrypt.cli:letsencrypt version: 0.4.1 2019-01-28 16:36:08,337EBUG:letsencrypt.cli:Arguments: ['-n', '--text', '--agree-tos', '--expand', '--authenticator', 'webroot', '--server', 'https://acme-v02.api.letsencrypt.org/directory', '--rsa-key-size', '4096', '--email', '[email protected]', '--domains', 'lounge2.theloungesound.ca', '--webroot-path', '/usr/local/ispconfig/interface/acme'] 2019-01-28 16:36:08,337EBUG:letsencrypt.cliiscovered plugins: PluginsRegistry(PluginEntryPoint#webroot,PluginEntryPoint#null,PluginEntryPoint#manual,PluginEntryPoint#standalone) 2019-01-28 16:36:08,337EBUG:letsencrypt.cli:Requested authenticator webroot and installer None 2019-01-28 16:36:08,338EBUG:letsencrypt.plugins.webroot:Creating root challenges validation dir at /usr/local/ispconfig/interface/acme/.well-known/acme-challenge 2019-01-28 16:36:08,338EBUG:letsencrypt.display.ops:Single candidate plugin: * webroot Description: Webroot Authenticator Interfaces: IAuthenticator, IPlugin Entry point: webroot = letsencrypt.plugins.webroot:Authenticator Initialized: <letsencrypt.plugins.webroot.Authenticator object at 0x7f4ff8cc9f10> Prep: True 2019-01-28 16:36:08,338EBUG:letsencrypt.cli:Selected authenticator <letsencrypt.plugins.webroot.Authenticator object at 0x7f4ff8cc9f10> and installer None 2019-01-28 16:36:08,589EBUG:root:Sending GET request to https://acme-v02.api.letsencrypt.org/directory. args: (), kwargs: {} 2019-01-28 16:36:08,594:INFO:requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org 2019-01-28 16:36:08,700EBUG:requests.packages.urllib3.connectionpool:"GET /directory HTTP/1.1" 200 658 2019-01-28 16:36:08,701EBUG:root:Received <Response [200]>. Headers: {'Content-Length': '658', 'Expires': 'Mon, 28 Jan 2019 16:36:08 GMT', 'Strict-Transport-Security': 'max-age=604800', 'Server': 'nginx', 'Connection': 'keep-alive', 'Pragma': 'no-cache', 'Cache-Control': 'max-age=0, no-cache, no-store', 'Date': 'Mon, 28 Jan 2019 16:36:08 GMT', 'X-Frame-Options': 'DENY', 'Content-Type': 'application/json'}. Content: '{\n "jk9L4W45V-Q": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417",\n "keyChange": "https://acme-v02.api.letsencrypt.org/acme/key-change",\n "meta": {\n "caaIdentities": [\n "letsencrypt.org"\n ],\n "termsOfService": "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf",\n "website": "https://letsencrypt.org"\n },\n "newAccount": "https://acme-v02.api.letsencrypt.org/acme/new-acct",\n "newNonce": "https://acme-v02.api.letsencrypt.org/acme/new-nonce",\n "newOrder": "https://acme-v02.api.letsencrypt.org/acme/new-order",\n "revokeCert": "https://acme-v02.api.letsencrypt.org/acme/revoke-cert"\n}' 2019-01-28 16:36:08,702EBUG:acme.client:Received response <Response [200]> (headers: {'Content-Length': '658', 'Expires': 'Mon, 28 Jan 2019 16:36:08 GMT', 'Strict-Transport-Security': 'max-age=604800', 'Server': 'nginx', 'Connection': 'keep-alive', 'Pragma': 'no-cache', 'Cache-Control': 'max-age=0, no-cache, no-store', 'Date': 'Mon, 28 Jan 2019 16:36:08 GMT', 'X-Frame-Options': 'DENY', 'Content-Type': 'application/json'}): '{\n "jk9L4W45V-Q": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417",\n "keyChange": "https://acme-v02.api.letsencrypt.org/acme/key-change",\n "meta": {\n "caaIdentities": [\n "letsencrypt.org"\n ],\n "termsOfService": "https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf",\n "website": "https://letsencrypt.org"\n },\n "newAccount": "https://acme-v02.api.letsencrypt.org/acme/new-acct",\n "newNonce": "https://acme-v02.api.letsencrypt.org/acme/new-nonce",\n "newOrder": "https://acme-v02.api.letsencrypt.org/acme/new-order",\n "revokeCert": "https://acme-v02.api.letsencrypt.org/acme/revoke-cert"\n}' 2019-01-28 16:36:08,704EBUG:letsencrypt.cli:Exiting abnormally: Traceback (most recent call last): File "/usr/bin/letsencrypt", line 9, in <module> load_entry_point('letsencrypt==0.4.1', 'console_scripts', 'letsencrypt')() File "/usr/lib/python2.7/dist-packages/letsencrypt/cli.py", line 1986, in main return config.func(config, plugins) File "/usr/lib/python2.7/dist-packages/letsencrypt/cli.py", line 689, in obtain_cert le_client = _init_le_client(config, authenticator, installer) File "/usr/lib/python2.7/dist-packages/letsencrypt/cli.py", line 206, in _init_le_client acc, acme = _determine_account(config) File "/usr/lib/python2.7/dist-packages/letsencrypt/cli.py", line 191, in _determine_account config, account_storage, tos_cb=_tos_cb) File "/usr/lib/python2.7/dist-packages/letsencrypt/client.py", line 116, in register acme = acme_from_config_key(config, key) File "/usr/lib/python2.7/dist-packages/letsencrypt/client.py", line 41, in acme_from_config_key return acme_client.Client(config.server, key=key, net=net) File "/usr/lib/python2.7/dist-packages/acme/client.py", line 63, in __init__ self.net.get(directory).json()) File "/usr/lib/python2.7/dist-packages/acme/messages.py", line 169, in from_json raise jose.DeserializationError(str(error)) DeserializationError: Deserialization error: Wrong directory fields
After running the command i got this... root@one:/etc/postfix# /usr/local/ispconfig/server/server.sh An unexpected error occurred: DeserializationError: Deserialization error: Wrong directory fields Please see the logfiles in /var/log/letsencrypt for more details. finished.
The post by..... ExaconAT ...in this link: https://www.howtoforge.com/communit...ing-since-updating-to-ispconfig-3-1-13.79882/ solved it for me! Yay!
