Subj : Re: fTelnet
To   : Shurato
From : tassiebob
Date : Mon Oct 21 2024 06:45 pm

 Sh>  ta> websockify --cert /etc/letsencrypt/live/xxx.com/fullchain.pem
 Sh>  ta> --key=/etc/letsencrypt/live/xxx.com/privkey.pem --ssl-only
 Sh>  ta> --log-file=/var/log/websockify/websockify.log --daemon
 Sh>  ta> 192.46.220.211:2443 bbs.tassiebob.com:2323
 Sh> 
 Sh>  ta> This is basically what I'm using thanks to a previous poster.
 Sh> 
 Sh> I would suggest that your target ip is internal to avoid leaking the
 Sh> security.

I'm not sure I see the point?

The 192.46.220.211:2443 can be found in the web page that fTelnet is embedded in, and I believe needs to be a public IP so that the fTelnet client running in someone's browser can connect to it.

The bbs.tassiebob.com:2323 is just the regular host:port of the BBS that anyone would use if they used a native terminal.

In my case I can't use private addressing anyway as the BBS and the websockify proxy are on separate machines, on separate networks, in separate physical locations.

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
 * Origin: TassieBob BBS, Hobart, Tasmania (21:3/169)

.