Project needs updated

[inhahe]

It looks like this is abandonware, but I'll say that fTelnetProxy is old now, and the SSL functions it uses are incompatible with modern browsers.
Also, the Visual Studio solution for it seems to be incomplete. It couldn't find some files/directories and wouldn't build.
(It also uses a .net framework that's so old I didn't have it installed, and I installed it, but for some reason VS still complained that I didn't have the necessary framework.)
Oh yeah, and the links to the binaries for fTelnetClient no longer work; fortunately, I already had the binaries from years ago.

It would be okay if there's a newer and better HTML<->telnet interface out there--is there one?

By the way, the way I got around the SSL functions being outdated, with the help of claude.ai, was with this nginx clause:

server {
    listen 16668 ssl;
    server_name inhahe.com;
    
    ssl_certificate /etc/letsencrypt/live/inhahe.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/inhahe.com/privkey.pem;
    
    location / {
        proxy_pass http://127.0.0.1:16669;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;

        proxy_read_timeout 3600s;
        proxy_send_timeout 3600s;

    }
}

Where 16669 is the port fTelnetProxy is set to listen to, and 16668 is the port the fTelnet HTML is set to target.

[rickparrish]

It looks like this is abandonware, but I'll say that fTelnetProxy is old now, and the SSL functions it uses are incompatible with modern browsers.

Not sure what makes you think it's abandonware? Also, not sure which SSL functions you're referring to. It's supported TLS 1.2 for years, so maybe you mean TLS 1.3? I guess it'd be cool if it supported that, but 1.2 is good enough for me so I haven't looked into 1.3.

Also, the Visual Studio solution for it seems to be incomplete. It couldn't find some files/directories and wouldn't build.

I should probably make it more prominent, but there's a note at the end of the README saying that RMLib is also needed: https://github.com/rickparrish/RMLib

Oh yeah, and the links to the binaries for fTelnetClient no longer work; fortunately, I already had the binaries from years ago.

Thanks for the heads up, looks like GitHub changed the method for linking to raw files. I'll go update those links in a second.

It would be okay if there's a newer and better HTML<->telnet interface out there--is there one?

Not sure if you're referring to fTelnet or fTelnetProxy with this comment. If fTelnet, then I'm not sure, I haven't looked for other solutions lately. If fTelnetProxy, then Websockify is what I used prior to creating fTelnetProxy, so you might try it to see if it is better.

[inhahe]

Oh, it's still in active development? That's cool. I don't remember what made me think it's abandonware. I think I remember going to update something and it was already up to date from years and years ago. Or maybe the commits shown on the main page were really old. I don't know. Oh, and the .net framework target version being really old.

Regarding the TLS, I kept getting an error when trying to connect to it in Chrome. Claude.ai showed me a command to run to inspect the handshake process, and it said the results indicated a version mismatch, which was what I'd suspected. Bypassing TLS using the code I included in the original post solved the issue.

[inhahe]

Oh, but that may have been an old version of fTelnetProxy that wouldn't connect, now that I think of it. Because I couldn't get the newer version because I couldn't compile it and the binary links didn't work. I just downloaded the newer version since you fixed the link, but I'll continue using the older version the way I'm using it because I know it works, so I can't verify that the newer version is actually compatible with the latest Chrome.

[rickparrish]

Not really in active development, since it does what I need for the public proxies, and most people either use one of those or are running Synchronet and use the proxy that ships with it. So not a lot of people run their own instance of fTelnetProxy, but if anyone does and runs into problems I'm more than happy to make updates as needed.

And yeah, if you have an older version that predates the TLS 1.2 fix, then that would definitely cause issues with modern browsers that have dropped 1.0 and 1.1 support.

Never a bad idea to have nginx sitting in front of an internet-facing server, so sticking to what you have now seems like a good plan.

Although looking at the commit log, since the TLS 1.2 commit I do see one important commit that frees up resources to avoid crashes, although that probably isn't an issue on a computer with decent resources (some of the public proxies only have 128MB RAM, so are more sensitive to memory leaks).