• Letsyncrypt

    From Mortifis@1:103/705 to All on Sunday, August 25, 2019 09:50:35
    Just wondering if there has been any updates to letsyncrypt. My latest update is from Aug 14th and I am still getting this error:

    (executed manually jsexec letsyncrypt --force)

    Reading script from C:\sbbs\exec\letsyncrypt.js
    C:\sbbs\exec\letsyncrypt.js compiled in 0.00 seconds
    Getting directory.
    Calling newOrder.
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    {
    "type": "urn:ietf:params:acme:error:malformed",
    "detail": "JWS verification error",
    "status": 400
    }
    !JavaScript : uncaught exception: newOrder responded with 400 not 201

    My letsyncrypt.ini is:

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

    [Domains]
    alleycat.synchro.net=/sbbs/etrucker
    emptykeg.synchro.net=/sbbs/etrucker
    [key_id] acme-v02.api.letsencrypt.org=https://acme-v02.api.letsencrypt.org/acme /acct/51915535


    My doctor said I have the body of a 25 year old ... and the mind of a 10 :-/

    ---
    Synchronet AlleyCat! BBS - http://alleycat.synchro.net:81
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Mortifis on Sunday, August 25, 2019 13:15:36
    Re: Letsyncrypt
    By: Mortifis to All on Sun Aug 25 2019 09:50 am

    Just wondering if there has been any updates to letsyncrypt. My latest update is from Aug 14th and I am still getting this error:

    (executed manually jsexec letsyncrypt --force)

    Reading script from C:\sbbs\exec\letsyncrypt.js
    C:\sbbs\exec\letsyncrypt.js compiled in 0.00 seconds
    Getting directory.
    Calling newOrder.
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    {
    "type": "urn:ietf:params:acme:error:malformed",
    "detail": "JWS verification error",
    "status": 400
    }
    !JavaScript : uncaught exception: newOrder responded with 400 not 201

    My letsyncrypt.ini is:

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

    [Domains]
    alleycat.synchro.net=/sbbs/etrucker
    emptykeg.synchro.net=/sbbs/etrucker
    [key_id] acme-v02.api.letsencrypt.org=https://acme-v02.api.letsencrypt.org/acme /acct/51915535

    Maybe try renaming or moving your ctrl/letsyncrypt.key file.

    digital man

    Synchronet/BBS Terminology Definition #45:
    LF = Line Feed (ASCII 10, Ctrl-J)
    Norco, CA WX: 92.2F, 35.0% humidity, 8 mph E wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.09-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Mortifis@1:103/705 to Digital Man on Monday, August 26, 2019 08:43:46
    @MSGID: <5D62EC68.46053.sync_sys@vert.synchro.net>
    @REPLY: <5D62841B.1225.dove-syncops@alleycat.synchro.net>
    @TZ: c1e0
    Re: Letsyncrypt
    By: Mortifis to All on Sun Aug 25 2019 09:50 am

    Just wondering if there has been any updates to letsyncrypt. My latest update is from Aug 14th and I am still getting this error:

    (executed manually jsexec letsyncrypt --force)

    Reading script from C:\sbbs\exec\letsyncrypt.js C:\sbbs\exec\letsyncrypt.js compiled in 0.00 seconds
    Getting directory.
    Calling newOrder.
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    {
    "type": "urn:ietf:params:acme:error:malformed",
    "detail": "JWS verification error",
    "status": 400
    }
    !JavaScript : uncaught exception: newOrder responded with 400 not 201

    My letsyncrypt.ini is:

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

    [Domains]
    alleycat.synchro.net=/sbbs/etrucker
    emptykeg.synchro.net=/sbbs/etrucker
    [key_id] acme-v02.api.letsencrypt.org=https://acme-v02.api.letsencrypt.org/acme /acct/51915535

    Maybe try renaming or moving your ctrl/letsyncrypt.key file.

    digital man

    That was the first thing I tried, also tried deleting the file and running the script again with the same results. alleycat is on port 81, could that be an issue? I have a letsencrypt on my apache server on port 80


    My doctor said I have the body of a 25 year old ... and the mind of a 10 :-/

    ---
    Synchronet AlleyCat! BBS - http://alleycat.synchro.net:81
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Mortifis on Monday, August 26, 2019 13:45:08
    Re: Re: Letsyncrypt
    By: Mortifis to Digital Man on Mon Aug 26 2019 08:43 am

    @MSGID: <5D62EC68.46053.sync_sys@vert.synchro.net>
    @REPLY: <5D62841B.1225.dove-syncops@alleycat.synchro.net>
    @TZ: c1e0
    Re: Letsyncrypt
    By: Mortifis to All on Sun Aug 25 2019 09:50 am

    Just wondering if there has been any updates to letsyncrypt. My latest update is from Aug 14th and I am still getting this error:

    (executed manually jsexec letsyncrypt --force)

    Reading script from C:\sbbs\exec\letsyncrypt.js C:\sbbs\exec\letsyncrypt.js compiled in 0.00 seconds
    Getting directory.
    Calling newOrder.
    Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
    {
    "type": "urn:ietf:params:acme:error:malformed",
    "detail": "JWS verification error",
    "status": 400
    }
    !JavaScript : uncaught exception: newOrder responded with 400 not 201

    My letsyncrypt.ini is:

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

    [Domains]
    alleycat.synchro.net=/sbbs/etrucker emptykeg.synchro.net=/sbbs/etrucker
    [key_id] acme-v02.api.letsencrypt.org=https://acme-v02.api.letsencrypt.org/acme /acct/51915535

    Maybe try renaming or moving your ctrl/letsyncrypt.key file.

    That was the first thing I tried, also tried deleting the file and running the script again with the same results. alleycat is on port 81, could that be an issue?

    I don't see any method of telling letsencrypt to valid your domain using a non-standard TCP port. Anyone know? If there's no configuration setting, then perhaps you'll have to, at least temporarily, use port 80 for your verification.



    digital man

    Synchronet "Real Fact" #11:
    DOVE-Net was originally an exclusive ("elite") WWIVnet network in O.C., Calif. Norco, CA WX: 94.4F, 27.0% humidity, 3 mph NW wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.09-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Alterego@1:103/705 to Digital Man on Tuesday, August 27, 2019 08:17:16
    Re: Re: Letsyncrypt
    By: Digital Man to Mortifis on Mon Aug 26 2019 01:45 pm

    That was the first thing I tried, also tried deleting the file and running the script again with the same results. alleycat is on port 81, could that be an issue?

    I don't see any method of telling letsencrypt to valid your domain using a
    non-standard TCP port. Anyone know? If there's no configuration setting, then perhaps you'll have to, at least temporarily, use
    port 80 for your verification.

    I think I've been here before, and no, as far as I can remember you cannot use anything other than http (port 80) for validation - if you choose that validation method.

    Alterantively, you can use DNS validation, where a token needs to be populated in DNS, and letsencrypt validates that its been updated by a DNS query. I use that process for wildcards, using cloudflare DNS (they have an API that enables
    you to automate it).
    ...*

    ... Desperate diseases require desperate remedies.

    ---
    Synchronet Alterant | an SBBS in Docker on Pi!
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Mortifis@1:103/705 to Alterego on Tuesday, August 27, 2019 10:26:04
    @VIA: ALTERANT
    @MSGID: <5D645A6C.1168.dove-syncops@bbs.leenooks.net>
    @REPLY: <5D6444D4.46070.sync_sys@vert.synchro.net>
    @TZ: 1258
    Re: Re: Letsyncrypt
    By: Digital Man to Mortifis on Mon Aug 26 2019 01:45 pm

    That was the first thing I tried, also tried deleting the file and running the script again with the same results. alleycat is on port 81, could that be an issue?

    I don't see any method of telling letsencrypt to valid your domain using a non-standard TCP port. Anyone know? If there's no configuration setting, then perhaps you'll have to, at least temporarily, use
    port 80 for your verification.

    I think I've been here before, and no, as far as I can remember you cannot use anything other than http (port 80) for validation - if you choose that validation method.

    Alterantively, you can use DNS validation, where a token needs to be populated in DNS, and letsencrypt validates that its been updated by a DNS query. I use that process for wildcards, using cloudflare DNS (they have an API that enables you to automate it).

    A viable option, however, in this instance, I am not going to ask DM and/or our devs to add TXT record support to dyndns.js nor WebHops and Redirects to accommodate non-standard ports. I had tried to add a virtualhost and a redirect to my Apache that resides on a separate system which has SSL/TLS encryption but SBBS Web Server still failed. No worries I appreciate the info




    My doctor said I have the body of a 25 year old ... and the mind of a 10 :-/

    ---
    Synchronet AlleyCat! BBS - http://alleycat.synchro.net:81
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Mortifis on Tuesday, August 27, 2019 09:22:24
    Re: Re: Letsyncrypt
    By: Mortifis to Alterego on Tue Aug 27 2019 10:26 am

    @VIA: ALTERANT
    @MSGID: <5D645A6C.1168.dove-syncops@bbs.leenooks.net>
    @REPLY: <5D6444D4.46070.sync_sys@vert.synchro.net>
    @TZ: 1258
    Re: Re: Letsyncrypt
    By: Digital Man to Mortifis on Mon Aug 26 2019 01:45 pm

    That was the first thing I tried, also tried deleting the file and running the script again with the same results. alleycat is on port 81, could that be an issue?

    I don't see any method of telling letsencrypt to valid your domain using a non-standard TCP port. Anyone know? If there's no configuration setting, then perhaps you'll have to, at least temporarily, use
    port 80 for your verification.

    I think I've been here before, and no, as far as I can remember you cannot use anything other than http (port 80) for validation - if you choose that validation method.

    Alterantively, you can use DNS validation, where a token needs to be populated in DNS, and letsencrypt validates that its been updated by a DNS query. I use that process for wildcards, using cloudflare DNS (they have an API that enables you to automate it).

    A viable option, however, in this instance, I am not going to ask DM and/or our devs to add TXT record support to dyndns.js nor WebHops and Redirects to accommodate non-standard ports. I had tried to add a virtualhost and a redirect to my Apache that resides on a separate system which has SSL/TLS encryption but SBBS Web Server still failed. No worries I appreciate the info

    I'll look into adding TXT record support.

    digital man

    This Is Spinal Tap quote #9:
    David St. Hubbins: I mean, it's not your job to be as confused as Nigel.
    Norco, CA WX: 77.4F, 63.0% humidity, 0 mph W wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.09-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Mortifis on Tuesday, August 27, 2019 09:38:14
    Re: Re: Letsyncrypt
    By: Digital Man to Mortifis on Tue Aug 27 2019 09:22 am

    Re: Re: Letsyncrypt
    By: Mortifis to Alterego on Tue Aug 27 2019 10:26 am

    @VIA: ALTERANT
    @MSGID: <5D645A6C.1168.dove-syncops@bbs.leenooks.net>
    @REPLY: <5D6444D4.46070.sync_sys@vert.synchro.net>
    @TZ: 1258
    Re: Re: Letsyncrypt
    By: Digital Man to Mortifis on Mon Aug 26 2019 01:45 pm

    That was the first thing I tried, also tried deleting the file and running the script again with the same results. alleycat is on port 81, could that be an issue?

    I don't see any method of telling letsencrypt to valid your domain using a non-standard TCP port. Anyone know? If there's no configuration setting, then perhaps you'll have to, at least temporarily, use
    port 80 for your verification.

    I think I've been here before, and no, as far as I can remember you cannot use anything other than http (port 80) for validation - if you choose that validation method.

    Alterantively, you can use DNS validation, where a token needs to be populated in DNS, and letsencrypt validates that its been updated by a DNS query. I use that process for wildcards, using cloudflare DNS (they have an API that enables you to automate it).

    A viable option, however, in this instance, I am not going to ask DM and/or our devs to add TXT record support to dyndns.js nor WebHops and Redirects to accommodate non-standard ports. I had tried to add a virtualhost and a redirect to my Apache that resides on a separate system which has SSL/TLS encryption but SBBS Web Server still failed. No worries I appreciate the info

    I'll look into adding TXT record support.

    Get the latest dyndns.js from CVS and then add a "TXT" value to the [dyndns] section of your ctrl/modopts.ini file. Let me know how that works for ya,

    digital man

    Synchronet "Real Fact" #26:
    The Synchronet Web Server was written predominantly by Stephen Hurd (Deuce). Norco, CA WX: 78.7F, 59.0% humidity, 2 mph SSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.09-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Mortifis@1:103/705 to Digital Man on Monday, September 02, 2019 17:09:56
    @MSGID: <5D655C76.46076.sync_sys@vert.synchro.net>
    @REPLY: <5D6558C0.46075.sync_sys@vert.synchro.net>
    @TZ: c1e0
    Re: Re: Letsyncrypt
    By: Digital Man to Mortifis on Tue Aug 27 2019 09:22 am

    I'll look into adding TXT record support.

    Get the latest dyndns.js from CVS and then add a "TXT" value to the [dyndns] section of your ctrl/modopts.ini file. Let me know how that works for ya,

    digital man

    I updated my dyndns.js but am not sure what keys=values to put in modopts.ini [dyndns] (I assume I have to add [dyndns] to modopts.ini) or how to tell letsyncrypt.js that it should use DNS Validation instead of http :/

    Seems my brain is reverting to a newbie LOL




    My doctor said I have the body of a 25 year old ... and the mind of a 10 :-/

    ---
    Synchronet AlleyCat! BBS - http://alleycat.synchro.net:81
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Mortifis on Monday, September 02, 2019 20:05:34
    Re: Re: Letsyncrypt
    By: Mortifis to Digital Man on Mon Sep 02 2019 05:09 pm

    @MSGID: <5D655C76.46076.sync_sys@vert.synchro.net>
    @REPLY: <5D6558C0.46075.sync_sys@vert.synchro.net>
    @TZ: c1e0
    Re: Re: Letsyncrypt
    By: Digital Man to Mortifis on Tue Aug 27 2019 09:22 am

    I'll look into adding TXT record support.

    Get the latest dyndns.js from CVS and then add a "TXT" value to the [dyndns] section of your ctrl/modopts.ini file. Let me know how that works for ya,

    digital man

    I updated my dyndns.js but am not sure what keys=values to put in modopts.ini [dyndns] (I assume I have to add [dyndns] to modopts.ini)

    Yes, you'd have to add that section to modopts.ini, like this:

    [dyndns]
    txt=some text
    wildcard=true

    or how
    to tell letsyncrypt.js that it should use DNS Validation instead of http :/

    That, I don't know. There's been some doubt about whether or not letsencrypt will actually follow a CNAME as well (which is how the wildcards are supported), so I am curious for someone to try that out.

    digital man

    This Is Spinal Tap quote #11:
    Nigel Tufnel: No. no. That's it, you've seen enough of that one.
    Norco, CA WX: 80.1F, 52.0% humidity, 5 mph E wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.09-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Mortifis@1:103/705 to Digital Man on Tuesday, September 03, 2019 09:02:03
    I updated my dyndns.js but am not sure what keys=values to put in modopts.ini [dyndns] (I assume I have to add [dyndns] to modopts.ini)

    Yes, you'd have to add that section to modopts.ini, like this:

    [dyndns]
    txt=some text
    wildcard=true

    or how
    to tell letsyncrypt.js that it should use DNS Validation instead of http :/

    That, I don't know. There's been some doubt about whether or not letsencrypt will actually follow a CNAME as well (which is how the wildcards are supported), so I am curious for someone to try that out.

    digital man


    If I am understanding correctly, the dns provider (I assume it is vert.synchro.net) needs to have a CNAME or NS record that is used in DNS-01 Validation. I personally would not expect either you, Duece or EC revamp or create an entire API that stores the TXT records for each *.synchro.net subdomain, but we will keep looking at work arounds :-/

    I suppose one solution would be to somehow make the ssl.cert less self-signed then we wouldn't need letsencrypt or certbot :)


    My doctor said I have the body of a 25 year old ... and the mind of a 10 :-/

    ---
    Synchronet AlleyCat! BBS - http://alleycat.synchro.net:81
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Mortifis@1:103/705 to Digital Man on Tuesday, September 03, 2019 17:35:11

    [dyndns]
    txt=some text
    wildcard=true

    I ran jsexec dyndns.js <qwk-pass> and noticed that there is also an RX ttl? so I added that to my modopts.ini

    how's this look and what does dyndns.synchro.net expect and do with the TX(s)?

    [dyndns]
    ip =
    ip6 =
    ttl =84600
    mx = alleycat.synchro.net
    txt = AlleyCat BBS
    loc = vert.synchro.net IN LOC 33 55 46.493 N 117 33 18.323 W 190m 10m 100m 10m wildcard = true
    port = 81
    tlsport = 443

    I used the loc of Norco, CA lol since I believe it is asking the location of your dyndns server :-)



    My doctor said I have the body of a 25 year old ... and the mind of a 10 :-/

    ---
    Synchronet AlleyCat! BBS - http://alleycat.synchro.net:81
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Mortifis on Tuesday, September 03, 2019 14:52:37
    Re: Re: Letsyncrypt
    By: Mortifis to Digital Man on Tue Sep 03 2019 09:02 am

    I updated my dyndns.js but am not sure what keys=values to put in modopts.ini [dyndns] (I assume I have to add [dyndns] to modopts.ini)

    Yes, you'd have to add that section to modopts.ini, like this:

    [dyndns]
    txt=some text
    wildcard=true

    or how
    to tell letsyncrypt.js that it should use DNS Validation instead of http :/

    That, I don't know. There's been some doubt about whether or not letsencrypt will actually follow a CNAME as well (which is how the wildcards are supported), so I am curious for someone to try that out.

    digital man


    If I am understanding correctly, the dns provider (I assume it is vert.synchro.net) needs to have a CNAME or NS record that is used in DNS-01 Validation. I personally would not expect either you, Duece or EC revamp or create an entire API that stores the TXT records for each *.synchro.net subdomain, but we will keep looking at work arounds :-/

    Well, I kind of already did that. You can have your TXT record for your *.synchro.net subdomain. And you can have wildcards so that whatever.yourbbs.synchro.net will resolve (via CNAME) to yourbbs.synchro.net

    I suppose one solution would be to somehow make the ssl.cert less self-signed then we wouldn't need letsencrypt or certbot :)

    The whole point of using letsencrypt is have a certificate authority (not "self") assign/authenticate the certificate. Before letsyncrypt, the only option we had was self-signed.


    digital man

    This Is Spinal Tap quote #27:
    As long as there's, y'know, sex and drugs, I can do without the rock and roll. Norco, CA WX: 93.5F, 41.0% humidity, 16 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.09-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Mortifis on Tuesday, September 03, 2019 14:58:25
    Re: Re: Letsyncrypt
    By: Mortifis to Digital Man on Tue Sep 03 2019 05:35 pm


    [dyndns]
    txt=some text
    wildcard=true

    I ran jsexec dyndns.js <qwk-pass> and noticed that there is also an RX ttl? so I added that to my modopts.ini

    That won't be used.

    how's this look and what does dyndns.synchro.net expect and do with the TX(s)?

    [dyndns]
    ip =
    ip6 =
    ttl =84600
    mx = alleycat.synchro.net
    txt = AlleyCat BBS
    loc = vert.synchro.net IN LOC 33 55 46.493 N 117 33 18.323 W 190m 10m 100m 10m

    The syntax of that "loc" value is wrong.

    wildcard = true
    port = 81
    tlsport = 443

    "port" and "tlsport" are not supported keys in the [dyndns] section of modopts.ini. See this for details:
    http://wiki.synchro.net/module:dyndns

    I used the loc of Norco, CA lol since I believe it is asking the location of your dyndns server :-)

    No, it's asking the location of *your* BBS. Why would my service ask *you* the location of itself?


    digital man

    This Is Spinal Tap quote #27:
    As long as there's, y'know, sex and drugs, I can do without the rock and roll. Norco, CA WX: 93.4F, 40.0% humidity, 13 mph E wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.09-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Mortifis@1:103/705 to Digital Man on Tuesday, September 03, 2019 22:26:38

    [dyndns]
    loc = vert.synchro.net IN LOC 33 55 46.493 N 117 33 18.323 W 190m 10m 100m 10m

    The syntax of that "loc" value is wrong.


    What is the proper usage? I followed the link on the wiki:

    loc = LOC records alleycat.synchro.net IN LOC 44 44 44.184 N 63 22 59.951 W 49m 10m 100m 10m

    is that correct?

    My doctor said I have the body of a 25 year old ... and the mind of a 10 :-/

    ---
    Synchronet AlleyCat! BBS - http://alleycat.synchro.net:81
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Mortifis on Tuesday, September 03, 2019 19:13:51
    Re: Re: Letsyncrypt
    By: Mortifis to Digital Man on Tue Sep 03 2019 10:26 pm


    [dyndns]
    loc = vert.synchro.net IN LOC 33 55 46.493 N 117 33 18.323 W 190m 10m 100m 10m

    The syntax of that "loc" value is wrong.


    What is the proper usage? I followed the link on the wiki:

    loc = LOC records alleycat.synchro.net IN LOC 44 44 44.184 N 63 22 59.951 W 49m 10m 100m 10m

    is that correct?

    No, it would be more like this:
    loc = 33 54 18.602 N 117 31 28.933 W 289.00m 10m 100m 10m


    digital man

    Synchronet/BBS Terminology Definition #40:
    IMAP = Internet Message Access Protocol
    Norco, CA WX: 85.1F, 49.0% humidity, 6 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.09-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Mortifis@1:103/705 to Digital Man on Wednesday, September 04, 2019 09:22:40
    @MSGID: <5D6F1DDF.46225.sync_sys@vert.synchro.net>
    @REPLY: <5D6F12CE.1402.dove-syncops@alleycat.synchro.net>
    @TZ: c1e0
    Re: Re: Letsyncrypt
    By: Mortifis to Digital Man on Tue Sep 03 2019 10:26 pm


    [dyndns]
    loc = vert.synchro.net IN LOC 33 55 46.493 N 117 33 18.323 W 190m 10m 100m 10m

    The syntax of that "loc" value is wrong.


    What is the proper usage? I followed the link on the wiki:

    loc = LOC records alleycat.synchro.net IN LOC 44 44 44.184 N 63 22 59.951 W 49m 10m 100m 10m

    is that correct?

    No, it would be more like this:
    loc = 33 54 18.602 N 117 31 28.933 W 289.00m 10m 100m 10m

    LOL, good thing I've never claimed to be intelligent. I followed the (see http://dnsloc.net/ for details) on the dyndns wiki and used their script result and read their link to https://en.wikipedia.org/wiki/LOC_record

    I seem to confuse easily these days; great, now I have to buy plaid spandex pants and learn to play golf :-)


    My doctor said I have the body of a 25 year old ... and the mind of a 10 :-/

    ---
    Synchronet AlleyCat! BBS - http://alleycat.synchro.net:81
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From HusTler@1:103/705 to All on Friday, December 06, 2019 05:26:45
    Thu Dec 5 22:45:40 2019 havens.synchronetbbs.org
    evnt SYNCRYPT Web root for TOSAgreed is not a directory (true)

    What am I doing wrong?


    HusTler @ Havens BBS
    havens.synchro.net

    ---
    Synchronet Havens BBS havens.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Mortifis@1:103/705 to HusTler on Saturday, December 07, 2019 08:17:46
    Thu Dec 5 22:45:40 2019 havens.synchronetbbs.org
    evnt SYNCRYPT Web root for TOSAgreed is not a directory (true)

    What am I doing wrong?

    what does your ctrl/letsyncrypt.ini look like?

    ---
    Synchronet AlleyCat! BBS - http://alleycat.synchro.net:81
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From HusTler@1:103/705 to Mortifis on Saturday, December 07, 2019 09:51:50
    Re: Re: Letsyncrypt
    By: Mortifis to HusTler on Sat Dec 07 2019 08:17 am

    evnt SYNCRYPT Web root for TOSAgreed is not a directory (true)

    What am I doing wrong?

    what does your ctrl/letsyncrypt.ini look like?

    [Domains]
    synchronetbbs.org = /sbbs/webv4/root
    TOSAgreed=true

    Hustler @ <-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 Saturday, December 07, 2019 14:59:29
    Re: Re: Letsyncrypt
    By: HusTler to Mortifis on Sat Dec 07 2019 09:51 am

    Re: Re: Letsyncrypt
    By: Mortifis to HusTler on Sat Dec 07 2019 08:17 am

    evnt SYNCRYPT Web root for TOSAgreed is not a directory (true)

    What am I doing wrong?

    what does your ctrl/letsyncrypt.ini look like?

    [Domains]
    synchronetbbs.org = /sbbs/webv4/root
    TOSAgreed=true

    TOSAgreed doesn't belong in the [Domains] section, it belongs in the global (top most) section of the file.


    digital man

    Synchronet "Real Fact" #10:
    The name "DOVE-Net" was suggested by King Drafus (sysop of The Beast's Domain). Norco, CA WX: 60.2F, 93.0% humidity, 3 mph ESE wind, 0.10 inches rain/24hrs --- SBBSecho 3.10-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Marisag@1:103/705 to HusTler on Monday, December 09, 2019 00:19:46
    Re: Re: Letsyncrypt
    By: HusTler to Mortifis on Sat Dec 07 2019 09:51:50

    what does your ctrl/letsyncrypt.ini look like?

    [Domains]
    synchronetbbs.org = /sbbs/webv4/root
    TOSAgreed=true

    Shouldn't that be havens.synchronetbbs.org?

    Marisa
    --- https://SynchronetBBS.org/OurServers - A list of all our websites
    --- https://SynchronetBBS.org/HostSplash - SBBS hosting for $14/month
    Synchronet Amiga City - The BBS for the Amiga - more than 3,500+ files
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Marisag on Monday, December 09, 2019 11:32:37
    Re: Re: Letsyncrypt
    By: Marisag to HusTler on Mon Dec 09 2019 12:19 am

    Re: Re: Letsyncrypt
    By: HusTler to Mortifis on Sat Dec 07 2019 09:51:50

    what does your ctrl/letsyncrypt.ini look like?

    [Domains]
    synchronetbbs.org = /sbbs/webv4/root
    TOSAgreed=true

    Shouldn't that be havens.synchronetbbs.org?

    Indeed.

    digital man

    Synchronet/BBS Terminology Definition #20:
    DOS = Disk Operating System (as in PC-DOS and MS-DOS)
    Norco, CA WX: 57.5F, 84.0% humidity, 7 mph NE wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.10-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)