• Re: SSH error: Unable to set key (-2)

    From MobbyG@21:1/219 to Warpslide on Thursday, August 19, 2021 10:41:20
    On 19 Aug 2021, Warpslide said the following...
    You can also post to the Fidonet MYSTIC echo. g00r00 who is the author
    of Mystic hangs out there and would probably know the answer to this.

    OK, I'll hop on a BBS with Fido and do that.

    Thanks!

    73.
    Rich, KB2MOB

    --- Mystic BBS v1.12 A47 2021/04/08 (Raspberry Pi/32)
    * Origin: Radio Freqs & Geeks BBS Running on a Pi400 (21:1/219)
  • From Warpslide@21:3/110 to MobbyG on Thursday, August 19, 2021 11:18:58
    On 19 Aug 2021, MobbyG said the following...

    OK, I'll hop on a BBS with Fido and do that.

    If you wanted to get on Fidonet yourself, reach out to Gregory Deyss (21:1/127) who is the net coordinator for New York State and he should be able to help you out.


    Jay

    ... Everybody has a right to pronounce foreign names as he chooses.

    --- Mystic BBS v1.12 A47 2021/08/17 (Raspberry Pi/32)
    * Origin: Northern Realms (21:3/110)
  • From Avon@21:1/101 to Warpslide on Sunday, August 22, 2021 16:55:12
    On 18 Aug 2021 at 09:56p, Warpslide pondered and said...

    I believe the key is located at mystic/data/ssl.cert:

    I'm unsure how to regenerate the file though if you can't restore it
    from backup. I know Mystic generated mine, just not sure how/when.

    I understand if you delete this then restart Mystic server it will regen the key.

    Best, Paul

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From mobbyg@21:1/101 to Avon on Monday, August 23, 2021 05:41:32
    On 22 Aug 2021 at 04:55p, Avon pondered and said...

    I understand if you delete this then restart Mystic server it will regen the key.

    Yes Paul, that is correct.

    And for future reference, g00r00 was able to diagnose the issue. I installed the beat which didn't work with Mystic. So I just grabbed 3.43 as it says on the wiki that is known to work.

    So I did a sudo make clean and recompiled 3.43. Fired the BBS back up and it connected no problem. I'm back to 100% on the BBS.

    73.
    Rich, KB2MOB

    |04---- |15Rich Lawrence, KB2MOB
    |14//// |15SysOp of Radio Freqs & Geeks BBS
    |01--v|10/// |07-Ham/Shortwav Radio, Tabletop Gaming and General Geekery- |11\\|02xx/ |08mobbyg@gmail.com

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Avon@21:1/101 to mobbyg on Monday, August 23, 2021 14:55:26
    On 23 Aug 2021 at 05:41a, mobbyg pondered and said...

    Yes Paul, that is correct.

    And for future reference, g00r00 was able to diagnose the issue. I installed the beat which didn't work with Mystic. So I just grabbed 3.43 as it says on the wiki that is known to work.

    So I did a sudo make clean and recompiled 3.43. Fired the BBS back up
    and it connected no problem. I'm back to 100% on the BBS.

    Good news Rich, thanks for the confirm and glad you got things working again.

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)