• Letsyncrypt help

    From HusTler@1:103/705 to All on Sat Dec 14 15:45:33 2019
    This is long but I'm at a dead end so I'm going to take a chance. This is my letsyncrypt.ini After I ran jsexec letsyncrypt.js

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true
    GroupReadableKeyFile = false

    [Domains]
    havens.synchronetbbs.org = /sbbs/web/root



    [key_id] acme-v02.api.letsencrypt.org=https://acme-v02.api.letsencrypt.org/acme/acct/738 04856

    Before I ran jsexec letsyncrypt.js the [key_id] was empty

    Below is the results I got when I ran jsexec letsyncrypt.js


    root@havens:/sbbs/ctrl# jsexec letsyncrypt.js

    JSexec v3.17c-Linux (rev 1.210) - Execute Synchronet JavaScript Module
    Compiled Nov 27 2019 16:15:07 with GCC 7.4.0

    Loading configuration files from /sbbs/ctrl
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 8388608 bytes
    JavaScript: Initializing context (stack: 16384 bytes)

    Reading script from /sbbs/exec/letsyncrypt.js
    /sbbs/exec/letsyncrypt.js compiled in 0.00 seconds
    Getting directory.
    Calling newAccount.
    0009 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    0009 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    {
    "type": "urn:ietf:params:acme:error:accountDoesNotExist",
    "detail": "No account exists with the provided key",
    "status": 400
    }
    Calling newAccount.
    0009 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    0009 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Location: https://acme-v02.api.letsencrypt.org/acme/acct/73804856
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Link: <https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf>;rel="terms- of-service"
    Calling newOrder.
    0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Location: https://acme-v02.api.letsencrypt.org/acme/order/73804856/1755750520 Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Getting authorization.
    0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Creating /sbbs/web/root/.well-known/acme-challenge/g7yWQLcK3jXu-WnzWdTJkfLLjRlftE1KOlInj RXj-BU
    Accepting challenge.
    0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Location: https://acme-v02.api.letsencrypt.org/acme/chall-v3/1731241950/8igCUQ Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Link: <https://acme-v02.api.letsencrypt.org/acme/authz-v3/1731241950>;rel="up" Polling authorization.
    0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Polling authorization.
    0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index" {"type":"http-01","status":"invalid","error":{"type":"urn:ietf:params:acme:erro r:connection","detail":"Fetching http://havens.synchronetbbs.org/.well-known/acme-challenge/g7yWQLcK3jXu-WnzWdTJ kfLLjRlftE1KOlInjRXj-BU: Connection refused","status":400},"url":"https://acme-v02.api.letsencrypt.org/acme/chall-v 3/1731241950/8igCUQ","token":"g7yWQLcK3jXu-WnzWdTJkfLLjRlftE1KOlInjRXj-BU","val idationRecord":[{"url":"http://havens.synchronetbbs.org/.well-known/acme-challe nge/g7yWQLcK3jXu-WnzWdTJkfLLjRlftE1KOlInjRXj-BU","hostname":"havens.synchronetb bs.org","port":"80","addressesResolved":["45.56.88.52"],"addressUsed":"45.56.88 .52"}]}
    !JavaScript : uncaught exception: Authorization failed... https://acme-v02.api.letsencrypt.org/acme/authz-v3/1731241950 /sbbs/exec/letsyncrypt.js executed in 25.32 seconds
    !Module (letsyncrypt.js) set exit_code: 1

    JavaScript: Destroying context
    JavaScript: Destroying runtime

    Returning error code: 1
    root@havens:/sbbs/ctrl#


    Any help as to why I can't get a certificate? Keep in mind I have No clue as to who owns and is responsible for synchronetbbs.org. I don't what I'm looking at here. I just see a lot of "failed" lines. Thanks

    H A V E N S B B S havens.synchro.net:23

    ---
    þ Synchronet þ Havens BBS havens.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to HusTler on Mon Dec 16 10:51:58 2019
    Re: Letsyncrypt help
    By: HusTler to All on Sat Dec 14 2019 03:45 pm

    This is long but I'm at a dead end so I'm going to take a chance. This is my letsyncrypt.ini After I ran jsexec letsyncrypt.js

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true
    GroupReadableKeyFile = false

    [Domains]
    havens.synchronetbbs.org = /sbbs/web/root

    Does that path match the [Web] RootDirectory value in your ctrl/sbbs.ini file?

    digital man

    This Is Spinal Tap quote #1:
    Nigel Tufnel: These go to eleven.
    Norco, CA WX: 59.1øF, 26.0% humidity, 1 mph E wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.10-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Altere@1:103/705 to HusTler on Mon Dec 16 16:49:54 2019
    Re: Letsyncrypt help
    By: HusTler to All on Sat Dec 14 2019 03:45 pm

    This is long but I'm at a dead end so I'm going to take a chance. This is my letsyncrypt.ini After I ran jsexec letsyncrypt.js

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true
    GroupReadableKeyFile = false

    [Domains]
    havens.synchronetbbs.org = /sbbs/web/root



    [key_id] acme-v02.api.letsencrypt.org=https://acme-v02.api.letsencrypt.org/acme /acct/73804856

    Before I ran jsexec letsyncrypt.js the [key_id] was empty


    You should have [State] as well, if not I would remove the contents under [key_id], add [State] after it with a blank line between to two and, remove letsyncrypt.key and ssl.cert from your ctrl directory then run jsexec letsyncrypt.js --force to regenerate the key files and populate key_id and state in the ini.

    -altere

    ---
    þ Synchronet þ Athelstan BBS þ athelstan.org þ telnet:23 | ssh:2222
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Mortifis@1:103/705 to HusTler on Wed Dec 18 11:26:16 2019
    This is long but I'm at a dead end so I'm going to take a chance.
    This is
    my letsyncrypt.ini After I ran jsexec letsyncrypt.js

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true
    GroupReadableKeyFile = false

    [Domains]
    havens.synchronetbbs.org = /sbbs/web/root



    [key_id] acme-v02.api.letsencrypt.org=https://acme-
    v02.api.letsencrypt.org/a
    cme/acct/73804856

    Before I ran jsexec letsyncrypt.js the [key_id] was empty

    Below is the results I got when I ran jsexec letsyncrypt.js


    root@havens:/sbbs/ctrl# jsexec letsyncrypt.js

    JSexec v3.17c-Linux (rev 1.210) - Execute Synchronet JavaScript Module Compiled Nov 27 2019 16:15:07 with GCC 7.4.0

    Loading configuration files from /sbbs/ctrl
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 8388608 bytes
    JavaScript: Initializing context (stack: 16384 bytes)

    Reading script from /sbbs/exec/letsyncrypt.js
    /sbbs/exec/letsyncrypt.js compiled in 0.00 seconds
    Getting directory.
    Calling newAccount.
    0009 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    0009 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    {
    "type": "urn:ietf:params:acme:error:accountDoesNotExist",
    "detail": "No account exists with the provided key",
    "status": 400
    }
    Calling newAccount.
    0009 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    0009 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Location: https://acme-v02.api.letsencrypt.org/acme/acct/73804856
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Link: <https://letsencrypt.org/documents/LE-SA-v1.2-November-15-
    2017.pdf>;re
    l="terms-of-service"
    Calling newOrder.
    0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Location: https://acme-v02.api.letsencrypt.org/acme/order/73804856/1755750520
    Link:
    <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Getting authorization.
    0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Creating /sbbs/web/root/.well-known/acme-challenge/g7yWQLcK3jXu-
    WnzWdTJkfLLj
    RlftE1KOlInjRXj-BU
    Accepting challenge.
    0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Location: https://acme-v02.api.letsencrypt.org/acme/chall-v3/1731241950/8igCUQ
    Link:
    <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Link:
    <https://acme-v02.api.letsencrypt.org/acme/authz-
    v3/1731241950>;rel="up"
    Polling authorization.
    0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    Polling authorization.
    0008 TLS ERROR 'No data was read because the remote system closed the connection (recv() == 0)' (-1) popping data
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    {"type":"
    http-01","status":"invalid","error":
    {"type":"urn:ietf:params:acme:error:conn
    ection","detail":"Fetching http://havens.synchronetbbs.org/.well-
    known/acme-
    challenge/g7yWQLcK3jXu-WnzWdTJkfLLjRlftE1KOlInjRXj-BU: Connection
    refused","
    status":400},"url":"https://acme-v02.api.letsencrypt.org/acme/chall-
    v3/17312
    41950/8igCUQ","token":"g7yWQLcK3jXu-WnzWdTJkfLLjRlftE1KOlInjRXj-
    BU","validat
    ionRecord":[{"url":"http://havens.synchronetbbs.org/.well-known/acme-
    challen
    ge/g7yWQLcK3jXu-WnzWdTJkfLLjRlftE1KOlInjRXj-
    BU","hostname":"havens.synchrone
    tbbs.org","port":"80","addressesResolved":
    ["45.56.88.52"],"addressUsed":"45.
    56.88.52"}]}
    !JavaScript : uncaught exception: Authorization failed... https://acme-v02.api.letsencrypt.org/acme/authz-v3/1731241950 /sbbs/exec/letsyncrypt.js executed in 25.32 seconds
    !Module (letsyncrypt.js) set exit_code: 1

    JavaScript: Destroying context
    JavaScript: Destroying runtime

    Returning error code: 1
    root@havens:/sbbs/ctrl#


    Any help as to why I can't get a certificate? Keep in mind I have No
    clue
    as to who owns and is responsible for synchronetbbs.org. I don't what
    I'm
    looking at here. I just see a lot of "failed" lines. Thanks

    H A V E N S B B S havens.synchro.net:23

    When I follow the ip address 45.56.88.52 I get havens.synchro.net yet you
    have [Domains] havens.synchronetbbs.org in your letsyncrypt.ini file so
    the hash does not match which negates the certificate ... try changing [Domains] to havens.synchro.net; delete the [Key_id] and [State] then
    rerun ./jsexec letsyncrypt.js --force

    Please post your results

    ---
    þ Synchronet þ AlleyCat! BBS - http://alleycat.synchro.net:81
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From HusTler@1:103/705 to Digital Man on Tue Dec 17 11:24:19 2019
    Re: Letsyncrypt help
    By: Digital Man to HusTler on Mon Dec 16 2019 10:51 am

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true
    GroupReadableKeyFile = false

    [Domains]
    havens.synchronetbbs.org = /sbbs/web/root
    Does that path match the [Web] RootDirectory value in your ctrl/sbbs.ini

    Which? Are you saying Directory = /directory should be
    Directory = /sbbs/web/root?


    H A V E N S B B S havens.synchro.net:23

    ---
    þ Synchronet þ Havens BBS havens.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to HusTler on Tue Dec 17 09:15:38 2019
    Re: Letsyncrypt help
    By: HusTler to Digital Man on Tue Dec 17 2019 11:24 am

    Re: Letsyncrypt help
    By: Digital Man to HusTler on Mon Dec 16 2019 10:51 am

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true
    GroupReadableKeyFile = false

    [Domains]
    havens.synchronetbbs.org = /sbbs/web/root
    Does that path match the [Web] RootDirectory value in your ctrl/sbbs.ini

    Which? Are you saying Directory = /directory should be
    Directory = /sbbs/web/root?

    No. I'm saying the path specified in the [Domains] section needs to match the [Web] RootDirectory value in your ctrl/sbbs.ini file.

    digital man

    Synchronet "Real Fact" #3:
    Synchronet version 2 was written in C and 8086 assembly programming languages. Norco, CA WX: 53.9øF, 22.0% humidity, 4 mph W wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.10-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From HusTler@1:103/705 to Mortifis on Tue Dec 17 14:38:37 2019
    Re: Re: Letsyncrypt help
    By: Mortifis to HusTler on Wed Dec 18 2019 11:26 am

    When I follow the ip address 45.56.88.52 I get havens.synchro.net yet you have [Domains] havens.synchronetbbs.org in your letsyncrypt.ini file so
    the hash does not match which negates the certificate ... try changing [Domains] to havens.synchro.net; delete the [Key_id] and [State] then
    rerun ./jsexec letsyncrypt.js --force

    Please post your results

    Ok I followed yours and DM's instruction. My letsyncrypt.ini and sbbs.ini have my root directory as /sbbs/webv4/root

    here are the results after I run letsyncrypt.js

    The script compiles but no results echo back.
    I then log back on to the server and reboot

    Now both havens.synchro.net and havens.synchronetbbs.org "close unexpectedly <--------------snip----------------------->
    Here's a sniplet of my letsyncrypt.ini and sbbs.ini

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true
    GroupReadableKeyFile = false

    [Domains]
    havens.synchro.net = /sbbs/webv4/root

    [State]

    [key_id]

    <------------------------------snip----------------------------------->

    [Web] Web (HTTP) Server
    AutoStart = True
    ; HTTP interface(s)
    Interface =
    Port = 80
    HTTPS interface(s)
    TLSInterface =
    TLSPort = 443
    MaxClients = 150

    RootDirectory=/sbbs/webv4/root
    TOSAGreed = true
    ErrorDirectory=/sbbs/webv4/root/error
    IndexFileNames = index.html,index.ssjs,index.xjs
    CGIDirectory = cgi-bin
    CGIExtensions = .cgi
    DefaultCGIContent = text/plain
    Authentication = Basic,Digest,TLS-PSK
    JavaScriptExtension = .ssjs
    MaxInactivity = 120



    root@huavens:/sbbs/ctrl# jsexec letsyncrypt.js --force

    JSexec v3.17c-Linux (rev 1.210) - Execute Synchronet JavaScript Module
    Compiled Nov 27 2019 16:15:07 with GCC 7.4.0

    Loading configuration files from /sbbs/ctrl
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 8388608 bytes
    JavaScript: Initializing context (stack: 16384 bytes)

    Reading script from /sbbs/exec/letsyncrypt.js
    /sbbs/exec/letsyncrypt.js compiled in 0.00 seconds


    After this I have no control. ctrl -c -x -d does not give me the prompt back. H A V E N S B B S havens.synchro.net:23

    ---
    þ Synchronet þ Havens BBS havens.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to HusTler on Tue Dec 17 12:49:57 2019
    Re: Re: Letsyncrypt help
    By: HusTler to Mortifis on Tue Dec 17 2019 02:38 pm

    Re: Re: Letsyncrypt help
    By: Mortifis to HusTler on Wed Dec 18 2019 11:26 am

    When I follow the ip address 45.56.88.52 I get havens.synchro.net yet
    you
    have [Domains] havens.synchronetbbs.org in your letsyncrypt.ini file so the hash does not match which negates the certificate ... try changing [Domains] to havens.synchro.net; delete the [Key_id] and [State] then rerun ./jsexec letsyncrypt.js --force

    Please post your results

    Ok I followed yours and DM's instruction. My letsyncrypt.ini and
    sbbs.ini
    have my root directory as /sbbs/webv4/root

    here are the results after I run letsyncrypt.js

    The script compiles but no results echo back.
    I then log back on to the server and reboot

    Rebooting... the computer?

    Now both havens.synchro.net and havens.synchronetbbs.org "close
    unexpectedly
    <--------------snip----------------------->
    Here's a sniplet of my letsyncrypt.ini and sbbs.ini

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true
    GroupReadableKeyFile = false

    [Domains]
    havens.synchro.net = /sbbs/webv4/root

    [State]

    [key_id]

    When the [State] and [key_id] sections are empty, that says that the letsyncrypt.js did not work.


    <------------------------------snip----------------------------------->

    [Web] Web (HTTP) Server
    AutoStart = True
    ; HTTP interface(s)
    Interface =
    Port = 80
    HTTPS interface(s)
    TLSInterface =
    TLSPort = 443
    MaxClients = 150

    RootDirectory=/sbbs/webv4/root
    TOSAGreed = true

    That "TOSAgreed" key doesn't belong in your sbbs.ini file (though it's not harming anything being there either).

    root@huavens:/sbbs/ctrl# jsexec letsyncrypt.js --force

    JSexec v3.17c-Linux (rev 1.210) - Execute Synchronet JavaScript Module Compiled Nov 27 2019 16:15:07 with GCC 7.4.0

    Loading configuration files from /sbbs/ctrl
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 8388608 bytes
    JavaScript: Initializing context (stack: 16384 bytes)

    Reading script from /sbbs/exec/letsyncrypt.js
    /sbbs/exec/letsyncrypt.js compiled in 0.00 seconds

    I'm not clear why you're running letsyncrypt.js manually rather than as a timed event as instructioned on the wiki.synchro.net page.

    I'm not clear why you're using the --force command-line option.

    After this I have no control. ctrl -c -x -d does not give me the prompt back.

    Typing 'reset' and enter will likely get your control back.

    digital man

    Synchronet/BBS Terminology Definition #78:
    UART = Universal Asynchronous Receiver/Transmitter
    Norco, CA WX: 62.0øF, 16.0% humidity, 2 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.10-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Altere@1:103/705 to Digital Man on Tue Dec 17 20:44:27 2019
    Re: Re: Letsyncrypt help
    By: Digital Man to HusTler on Tue Dec 17 2019 12:49 pm

    Yes, I know I'm responding to DM, but this is for both actually.

    When I follow the ip address 45.56.88.52 I get havens.synchro.net yet you have [Domains] havens.synchronetbbs.org in your letsyncrypt.ini file so the hash does not match which negates the certificate ... try Please post your results

    [Domains]
    havens.synchro.net = /sbbs/webv4/root

    I'm not really sure that matters. Since both hosts resolve to the ip address, I would throw both of them in there so the cert works for both hosts.

    [Domains]
    havens.synchro.net = /sbbs/webv4/root
    havens.synchronetbbs.org = /sbbs/webv4/root

    [State]

    [key_id]

    When the [State] and [key_id] sections are empty, that says that the letsyncrypt.js did not work.

    I'm no expert at this but could it be hanging or failing because it's looking for [key_id] first and not [State]? Those two are swapped from the original in cvs.

    I'm not clear why you're running letsyncrypt.js manually rather than as a timed event as instructioned on the wiki.synchro.net page.

    I'm not clear why you're using the --force command-line option.

    This is probably due to a couple of us running it manually and giving our examples on how we've worked around initial problems, due to our own mess ups. -altere

    ---
    þ Synchronet þ Athelstan BBS þ athelstan.org þ telnet:23 | ssh:2222
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rampage@1:103/705 to HusTler on Wed Dec 18 07:52:24 2019
    Re: Re: Letsyncrypt help
    By: HusTler to Mortifis on Tue Dec 17 2019 14:38:37


    Here's a sniplet of my letsyncrypt.ini and sbbs.ini

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true

    get rid of that Directory line in the global section... it isn't pointing to anywhere valid anyway...


    )\/(ark

    ---
    þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Altere@1:103/705 to Rampage on Wed Dec 18 10:30:29 2019
    Re: Re: Letsyncrypt help
    By: Rampage to HusTler on Wed Dec 18 2019 07:52 am

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true

    get rid of that Directory line in the global section... it isn't pointing
    to
    anywhere valid anyway...

    I believe that's for the letsencrypt.org side.

    -altere

    ---
    þ Synchronet þ Athelstan BBS þ athelstan.org þ telnet:23 | ssh:2222
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From HusTler@1:103/705 to Rampage on Wed Dec 18 15:34:06 2019
    Re: Re: Letsyncrypt help
    By: Rampage to HusTler on Wed Dec 18 2019 07:52 am

    Here's a sniplet of my letsyncrypt.ini and sbbs.ini

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory

    get rid of that Directory line in the global section... it isn't pointing
    to
    anywhere valid anyway...

    Ok.. I'll give it a try. I'll try anything once. ;-)


    H A V E N S B B S havens.synchro.net:23

    ---
    þ Synchronet þ Havens BBS havens.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From HusTler@1:103/705 to Altere on Wed Dec 18 16:14:23 2019
    Re: Re: Letsyncrypt help
    By: Altere to Rampage on Wed Dec 18 2019 10:30 am

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true

    get rid of that Directory line in the global section... it isn't
    pointing
    to anywhere valid anyway...

    I believe that's for the letsencrypt.org side.


    This certificate shit has to be the most stupid thing I've ever had to deal with as a BBS Sysop.
    H A V E N S B B S havens.synchro.net:23

    ---
    þ Synchronet þ Havens BBS havens.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rampage@1:103/705 to Altere on Thu Dec 19 06:55:36 2019
    Re: Re: Letsyncrypt help
    By: Altere to Rampage on Wed Dec 18 2019 10:30:29


    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true

    get rid of that Directory line in the global section... it isn't pointing to anywhere valid anyway...

    I believe that's for the letsencrypt.org side.

    it doesn't exist at all in my letyncrypt.ini file at all... in fact, the only thing i started with was TOSAgreed=true on the first line... i have only one domain at this time...


    )\/(ark

    ---
    þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Rampage on Thu Dec 19 10:00:29 2019
    Re: Re: Letsyncrypt help
    By: Rampage to Altere on Thu Dec 19 2019 06:55 am

    Re: Re: Letsyncrypt help
    By: Altere to Rampage on Wed Dec 18 2019 10:30:29


    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true

    get rid of that Directory line in the global section... it isn't pointing to anywhere valid anyway...

    I believe that's for the letsencrypt.org side.

    it doesn't exist at all in my letyncrypt.ini file at all... in fact, the only thing i started with was TOSAgreed=true on the first line... i have only one domain at this time...

    "/directory" is the default value of the letsyncrypt.ini Directory key. So having it present and set to "/directory" is the same as not having it. It's required for the ACMEv2 protocol exchange and does not refer to a directory on the BBS's local file system.

    digital man

    This Is Spinal Tap quote #23:
    David St. Hubbins: I envy us.
    Norco, CA WX: 58.8øF, 31.0% humidity, 4 mph WSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.10-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Altere@1:103/705 to Rampage on Thu Dec 19 11:07:15 2019
    Re: Re: Letsyncrypt help
    By: Rampage to Altere on Thu Dec 19 2019 06:55 am

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true

    get rid of that Directory line in the global section... it isn't pointing to anywhere valid anyway...

    I believe that's for the letsencrypt.org side.

    it doesn't exist at all in my letyncrypt.ini file at all... in fact, the only thing i started with was TOSAgreed=true on the first line... i have only one domain at this time...

    Well perhaps it's not required, but I saw it as part of letsencrypt.org/directory or something like that when I ran jexec manually. Not sure why you don't have it in yours, it's there in the cvs version.

    -altere

    ---
    þ Synchronet þ Athelstan BBS þ athelstan.org þ telnet:23 | ssh:2222
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Altere@1:103/705 to HusTler on Thu Dec 19 11:24:22 2019
    Re: Re: Letsyncrypt help
    By: HusTler to Altere on Wed Dec 18 2019 04:14 pm

    Host = acme-v02.api.letsencrypt.org
    Directory = /directory
    TOSAgreed = true

    get rid of that Directory line in the global section... it isn't pointing to anywhere valid anyway...

    I believe that's for the letsencrypt.org side.


    This certificate shit has to be the most stupid thing I've ever had to deal with as a BBS Sysop.

    <shrug> No one else has had this much of a problem getting it going. Have you tried removing the files that were created and letting the timed even re-create them? It's been recommended twice but I haven't seen any confirmation that you've done that. At this point I'd probably obtain a fresh copy of letsyncrypt.ini from cvs as well and follow the wiki to the T aside from having both your hosts.domains under [Domains].

    Sometimes you just have to start over until you get it right and figure out where you went wrong. In this case, there's letsyncrypt.ini, letsyncrypt.key, and ssl.cert involved, remove them and get a fresh copy of the .ini, and follow the wiki.

    -altere

    ---
    þ Synchronet þ Athelstan BBS þ athelstan.org þ telnet:23 | ssh:2222
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From HusTler@1:103/705 to Altere on Fri Dec 20 14:48:06 2019
    Re: Re: Letsyncrypt help
    By: Altere to HusTler on Thu Dec 19 2019 11:24 am

    This certificate shit has to be the most stupid thing I've ever had
    to deal with as a BBS Sysop.

    <shrug> No one else has had this much of a problem getting it going. Have
    you tried removing the files that were
    created and letting the timed even re-create them? It's been recommended
    twice but I haven't seen any confirmation
    that you've done that. At this point I'd probably obtain a fresh copy of
    letsyncrypt.ini from cvs as well and follow
    the wiki to the T aside from having both your hosts.domains under
    [Domains].

    No one else runs their BBS on a synchronetbbs.org server. I tried all the things you mentioned 5 times. I don't know how the DNS works with synchronetbbs.org or how https works with havens.synchronetbbs.org. When I run jsexec letsyncrypt.js it compiles and then locks up. I can't report anything cause the scrypt never finishes. It does create all the files after I reboot eg. letsyncrypt.key, ssl.cert and cryplib.key but the cert for https is not valid. Anyway thanks for your help. I've had enough and I'm going to abandon ship on this https thing.
    H A V E N S B B S havens.synchro.net:23

    ---
    þ Synchronet þ Havens BBS havens.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From mark lewis@1:3634/12.73 to Digital Man on Mon Dec 23 13:54:54 2019

    On 2019 Dec 19 10:00:28, you wrote to Rampage:

    "/directory" is the default value of the letsyncrypt.ini Directory
    key. So having it present and set to "/directory" is the same as not having it. It's required for the ACMEv2 protocol exchange and does not refer to a directory on the BBS's local file system.

    ahh, ok... i didn't have it at all when i set mine up... i had to create my letsyncrypt.ini myself since i'm running close to the bleeding edge of the code base...

    echo TOSAgreed=true > /sbbs/ctrl/letsyncrypt.ini
    touch /sbbs/data/syncrypt.now

    i think i tried copying some stuff from the wiki page but didn't understand it and how to do multiple domains with it at that time so i punted to only one domain, ran the above, everything worked, and i haven't looked back so far... my letsyncrypt.ini has only 6 lines in it, FWTW...

    )\/(ark

    Once men turned their thinking over to machines in the hope that this would set them free. But that only permitted other men with machines to enslave them.
    ... Half the people you know are below average.
    ---
    * Origin: (1:3634/12.73)