Several users have emailed me that SSH stopped working a few days ago. I can't figure it out - well, all I've really done is a reboot and looked in Mystic settings; everything LOOKS normal and I didn't make any changes.

I don't know where to dig in deeper. Did some system update mess something up - cryptlib or something?? Guess I can check the logs to see if theres any complaints or errors; anyone had Mystic just stop SSH working abruptly?



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On 16 Oct 2026, paulie420 said the following...

Several users have emailed me that SSH stopped working a few days ago. I can't figure it out - well, all I've really done is a reboot and looked
in Mystic settings; everything LOOKS normal and I didn't make any
changes.

I don't know where to dig in deeper. Did some system update mess
something up - cryptlib or something?? Guess I can check the logs to see if theres any complaints or errors; anyone had Mystic just stop SSH working abruptly?

I have rebooted here numerous times and have run updates and kernal updates on my board with no issues.. I am running a48 though I think you are on a49. Could it be an issue with A49??


|11 Bucko |14- |06Wrong Number Family Of BBS' |07- |03www.wrgnbr.com

... Kilometers are shorter than miles. Save gas, take your trip in kilometers

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

Hey paulie420!

On Fri, Oct 16 2026 18:40:44 -0700, you wrote:

Several users have emailed me that SSH stopped working a few days ago. I can't figure it out - well, all I've really done is a reboot and looked in Mystic settings; everything LOOKS normal and I didn't make any changes.

I don't know where to dig in deeper. Did some system update mess something up - cryptlib or something?? Guess I can check the logs to see if theres any complaints or errors; anyone had Mystic just stop SSH working
abruptly?

Are you receiving all messages, or just ignoring them?

I could have sworn I replied to you about this, and even sent you a message on your BBS..

After it failing for me with the latest version of Syncterm, I tried to connect to your ssh server with a linux terminal, and had to specify the "aes128-cbc" cipher on the command line.

There is now a separate option in Syncterm "Allow AES128-CBC" and the default setting is "No". Here is what google says:

"AES-128-CBC itself is not deprecated, but CBC-mode cipher suites using AES-128 are being phased out in favor of more secure modes like AES-GCM due to vulnerabilities such as padding oracle attacks."

I don't know, but hopefully I'm at least heading you in the right direction as far as where to look.

Either way, the fact that Mystic doesn't (and may never) support anything newer than a certain cryptlib version, is not a good thing. For now, you can tell the people that are having issues to make sure to use that cipher, but if you want to make sure ssh is supported on your BBS well into the future, you may want to try to run a more current SSH server that can actually be updated when things like this happen, and just have it spawn your BBS.

If g00r00 isn't coming back, you may have to do some workarounds, because at some point it may completely stop working. Unfortunately, it most likely won't be just you that is affected by this. ;(

Regards,
Accession

... He who laughs last, thinks slowest.
--- AmberEdit/linux 0.9.3
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

On 16 Oct 2026, paulie420 said the following...

Several users have emailed me that SSH stopped working a few days ago. I can't figure it out - well, all I've really done is a reboot and looked
in Mystic settings; everything LOOKS normal and I didn't make any
changes.

I don't know where to dig in deeper. Did some system update mess
something up - cryptlib or something?? Guess I can check the logs to see if theres any complaints or errors; anyone had Mystic just stop SSH working abruptly?

I had problems with earlier versions (don't remember which, Sorry!) of
syncTERM and upgraded to 1.10a (Debug). I now can connect to mine but I have to press the return key twice to get anything to show up. Are they running syncTERM by any chance? If so, it would be interesting to know what version.

|10ogg
|10S|02YSOP, |10A|02ltair |10I|02V |10B|02BS |10S|02SBBSS|07-|10M|07-|100|020003 |10C|02ertified |10B|02BS |10S|02YSOP

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Altair IV BBS (altairiv.ddns.net:2323) (21:2/147)

On 16 Oct 2026, paulie420 said the following...

Several users have emailed me that SSH stopped working a few days ago. I can't figure it out - well, all I've really done is a reboot and looked
in Mystic settings; everything LOOKS normal and I didn't make any
changes.

I don't know where to dig in deeper. Did some system update mess
something up - cryptlib or something?? Guess I can check the logs to see if theres any complaints or errors; anyone had Mystic just stop SSH working abruptly?

It's entirely possible there was an update that screwed something up. Your best bet is to make sure logging is set to verbose, shut down MIS, restart, attempt a connection, then check the logs.

I'm actually trying to connect now, and the port doesn't seem open. Do you have it blocked in your firewall, either in the OS or in your router?

--- Mystic BBS v1.12 A49 2024/05/12 (Linux/64)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)

Several users have emailed me that SSH stopped working a few days ago can't figure it out

I have rebooted here numerous times and have run updates and kernal updates on my board with no issues.. I am running a48 though I think you are on a49. Could it be an issue with A49??

Haven't figured it out yet - I'm sure I will, but... yea; SSH just dead to the w0rld.

I checked my port forwards on Xfinity, Mystic settings/menus... but gonna p0ke around the other things I mentioned in the OP post.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Are you receiving all messages, or just ignoring them?

I could have sworn I replied to you about this, and even sent you a message on your BBS..

I did miss your msg - but see it now.

Hmmmmmm... maybe? I *am* using a pre-compiled cryptlib b/c of an old Ubuntu issue a couple years ago w/ compiling cryptlib under Ubuntu... maybe I'll poke around there first.

I remember we used to deleted the old cert, the reinstall/setup cryptlib to get SSH working under Mystic. Thanks for the infoz... no other Mystic sysops are complaining about SSH dying, but - I did use that precompiled thing. Grrrr.

If g00r00 isn't coming back, you may have to do some workarounds,
because at some point it may completely stop working. Unfortunately, it most likely won't be just you that is affected by this. ;(

We've been doing that for years. If I had it to do all over again, of course I'd go w/ Synchronet - but HEAVILY modify it from the ground up, at the code level - but I don't have that luxury. I sure wish g00 would FOSS Mystic so we could make it AWESOME. At this point, its kinda like... cmon, dude.

There are [some] people with huge communities on Mystic software and... well, I guess its his regardless. But that doesn't help people utilizing it in 2026. :/

Shit - it could be vibe coded in a week w/ 1m tokens.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

I had problems with earlier versions (don't remember which, Sorry!) of syncTERM and upgraded to 1.10a (Debug). I now can connect to mine but I have to press the return key twice to get anything to show up. Are they running syncTERM by any chance? If so, it would be interesting to know what version.

No - zero connection at all. However, yer reply gives me an idea; gonna test on other terminal software... but no, theres not even a connection. :/

Hmmm



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Hey paulie420!

On Fri, Oct 16 2026 20:30:54 -0700, you wrote:

Hmmmmmm... maybe? I *am* using a pre-compiled cryptlib b/c of an old
Ubuntu issue a couple years ago w/ compiling cryptlib under Ubuntu...
maybe I'll poke around there first.

I think you're using a precompiled cryptlib because Mystic doesn't support anything higher than that. ;(

If g00r00 isn't coming back, you may have to do some workarounds,
because at some point it may completely stop working. Unfortunately, it
most likely won't be just you that is affected by this. ;(

We've been doing that for years. If I had it to do all over again, of course I'd go w/ Synchronet - but HEAVILY modify it from the ground up, at the code level - but I don't have that luxury. I sure wish g00 would FOSS Mystic so we could make it AWESOME. At this point, its kinda like... cmon, dude.

I wasn't saying to move away from Mystic. I'm just saying you may need to use a different ssh server, and have it load up Mystic upon login. It would have been nice if he would have implemented it that way, instead of just saying "grab cryptlib version 'x', and it'll work. Well, what happens when cryptlib updates 100 times and starts dropping support for certain cipers due to vulnerabilities?

Regards,
Accession

... I'm sarcastic, what's your superpower?
--- AmberEdit/linux 0.9.3
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

It's entirely possible there was an update that screwed something up.
Your best bet is to make sure logging is set to verbose, shut down MIS, restart, attempt a connection, then check the logs.

I'm actually trying to connect now, and the port doesn't seem open. Do
you have it blocked in your firewall, either in the OS or in your router?

Ports open at the router... :/ Nothing changed on MY END.

Checking Mystic logs and all the BS. Grrrrr. :P

Thanks maskreet



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Haven't figured it out yet - I'm sure I will, but... yea; SSH just dead
to the w0rld.

Shut down MIS server, delete "ssl.cert" file in mystic/data folder and restart MIS. It worked for me. Also with syncTERM 1.10a my SSH login also stop
working. I changed cryptlib versions but same thing.

... He who puts his nose to the grindstone is a bloody fool.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

Hey Gods69!

On Sat, Oct 17 2026 10:56:50 +0200, you wrote:

restart MIS. It worked for me. Also with syncTERM 1.10a my SSH login also stop working. I changed cryptlib versions but same thing.

I said it in a previous message:

There is now a separate option in Syncterm (1.10a) "Allow AES128-CBC" and the default setting is "No". You probably need to change that to "Yes."

Regards,
Accession

... Sarcasm, because beating people up is illegal.
--- AmberEdit/linux 0.9.3
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Shit - it could be vibe coded in a week w/ 1m tokens.

How much is 1m tokens?

***wcTaglines: You never know what you know!
--- Platinum Xpress/Win/WINServer v10.0gr17
* Origin: Inland Utopia BBS * Ontario, California (21:4/108)

There is now a separate option in Syncterm (1.10a) "Allow AES128-CBC"
and the default setting is "No". You probably need to change that to "Yes."

It connect but only in ASCII b/w mode, not ANSI. The auto detection don't work.

... Lonely is a man without love.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

Hey Gods69!

On Sat, Oct 17 2026 18:32:04 +0200, you wrote:

It connect but only in ASCII b/w mode, not ANSI. The auto detection don't work.

What is doing the auto detection, Mystic or Syncterm? And what if you try to force it to ansi?

I'm unaware of any ANSI issue. We were discussing why it wasn't connecting to SSH.

Regards,
Accession

... Politicians and diapers should be changed regularly for the same reasons. --- AmberEdit/linux 0.9.3
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Haven't figured it out yet - I'm sure I will, but... yea; SSH just de to the w0rld.

Shut down MIS server, delete "ssl.cert" file in mystic/data folder and restart MIS. It worked for me. Also with syncTERM 1.10a my SSH login
also stop working. I changed cryptlib versions but same thing.

... He who puts his nose to the grindstone is a bloody fool.

I did that today - SSH logins are still dead.

Great.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

paulie420 wrote:

I did that today - SSH logins are still dead.

There's an alternative - just put a different frontend to listen for inbound ssh connections.

https://github.com/ryanfantus/bbsfw

-esc
--- ViSiON/3 v0.9.4/Linux
* Origin: gEMENON (21:3/237)

I'm unaware of any ANSI issue. We were discussing why it wasn't
connecting to SSH.

I roll back to SuncTERM v1.9. Also now, i'm using more "TERMinator" software, no issues at all.

... Many are cold, but few are frozen.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

I did that today - SSH logins are still dead.

What is the SSH port to give a try ?

... Science clears the field upon which technology can build.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

Hey paulie420!

On Sat, Oct 17 2026 21:30:58 -0700, you wrote:

I did that today - SSH logins are still dead.

What do your logs say about SSH when you start MIS? Did you disable it? Is it not binding properly?

"It's dead" doesn't help anyone try to help you fix it. Provide some more detailed information, or it'll probably stay dead. :/

Regards,
Accession

... He who laughs last, thinks slowest.
--- AmberEdit/linux 0.9.3
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Hey Gods69!

On Sun, Oct 18 2026 09:07:12 +0200, you wrote:

I roll back to SuncTERM v1.9. Also now, i'm using more "TERMinator" software, no issues at all.

Ok. Just be aware I don't think it's a bug in Syncterm. It seems quite a few are phasing out the cipher that Mystic uses in most popular SSH servers and clients, unless you force it (at this time - but I imagine it'll eventually be removed completely).

Regards,
Accession

... If at first you don't succeed, destroy all evidence that you tried.
--- AmberEdit/linux 0.9.3
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Ok. Just be aware I don't think it's a bug in Syncterm. It seems quite a few are phasing out the cipher that Mystic uses in most popular SSH servers and clients, unless you force it (at this time - but I imagine it'll eventually be removed completely).

OK. Well Syncterm 1.10a screw up my BBS SSH logins!. I fixed it changing the cryptlib version and deleting the "ssl.cert" file.

... Lion tamer wants tamer lion. (Billboard ad.)

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

paulie420 wrote:

I did that today - SSH logins are still dead.

There's an alternative - just put a different frontend to listen for inbound ssh connections.
https://github.com/ryanfantus/bbsfw

Yessir - thanks for the option. Ticks me off that I can't figure it out, tho. Still gonna muck thru the logs and see if theres any clues.

Prolly something so stupid.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Yessir - thanks for the option. Ticks me off that I can't figure it out, tho. Still gonna muck thru the logs and see if theres any clues.

Change cryptlib version (libcl.so) and delete the "ssl.cert" if necessary.
This worked for me.

... I BM. You BM. We all BM for IBM!

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

Change cryptlib version (libcl.so) and delete the "ssl.cert" if
necessary. This worked for me.

Nope - got it 'fixed' but it was a weird one...

My router/software showed my port 1338 forward to BBS VM like always, but... removed it and re-added it; freaking SSH works again.

So its like either my Xfinity, or router software got borked somehow??? And like... who would of ever even tried that since the forward showed valid like always - so... thats why it was hard to find.

2oFB SSH back up - Syncterm users will see something about a new cert and have to accept on first connection. :/ Stupid...



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On 19 Oct 2026, paulie420 said the following...

Change cryptlib version (libcl.so) and delete the "ssl.cert" if necessary. This worked for me.

Nope - got it 'fixed' but it was a weird one...

My router/software showed my port 1338 forward to BBS VM like always, but... removed it and re-added it; freaking SSH works again.

So its like either my Xfinity, or router software got borked somehow??? And like... who would of ever even tried that since the forward showed valid like always - so... thats why it was hard to find.

I *kind of* called. Good you got it working again man!

--- Mystic BBS v1.12 A49 2024/05/12 (Linux/64)
* Origin: throwbackbbs.com -\- meriden, ct -\- (21:1/114)

Nope - got it 'fixed' but it was a weird one...

My router/software showed my port 1338 forward to BBS VM like always, but... removed it and re-added it; freaking SSH works again.

Glad it work again! :-)

... You can't get there from here.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Gods69 BBS (21:3/220)

[SSH fixed @ 2oFB]

I *kind of* called. Good you got it working again man!

Yep... its always DNS - or some other Xfinity ERR0R. :P



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)