I'm not sure -- I haven't been able to duplicate it here with the latest dev build.
Could you try setting up a new installation in a new directory using the latest sbbs_dev.zip and sbbs_run.zip to see if the problem occurs for you there? Depending on whether it works / doesn't work that'll help narrow things down a little bit.
Hi Ree! I did some testing and modifying the ftelnet.inc file in this way the system works:
<div id = "fTelnetContainer" class = "fTelnetContainer"> </ div>
<script> document.write ('<script src = "// embed-v2.ftelnet.ca/js/ftelnet- loader.norip.xfer.js?v=' + (new Date ()). getTime () + ' "> <\ / script>'); </ script>
<Script>
var WSS = (location.protocol.toLowerCase () == 'https:');
var Options = new fTelnetOptions ();
Options.BareLFtoCRLF = false;
Options.BitsPerSecond = 57600;
Options.ConnectionType = 'telnet';
Options.Emulation = 'ansi-bbs';
Options.Enter = '\ r';
Options.Font = 'CP437';
Options.ForceWss = false;
Options.Hostname = '@@ HostName @@';
Options.LocalEcho = false;
//Options.Port = (WSS? @@ WSSPort @@: @@ WSPort @@);
Options.Port = 23;
Options.ProxyHostname = 'proxy-nl.ftelnet.ca';
Options.ScreenColumns = 80;
Options.ScreenRows = 25;
Options.WebSocketUrlPath = '/? Port = @@ TelnetPort @@';
var fTelnet = new fTelnetClient ('fTelnetContainer', Options);
</ Script>
As you can see I modified the "Options.Port" variable and I have the
value "23" and I added a new call "Options.ProxyHostname", with these changes it works.
It seems that the Synchronet part that handles port "1123" and "11235" does
not work and actually started not to go since I updated the system .exe files. I also have to give proof that you told me and in the next few days I'll let you know how it went.
Bye
Thomas Bampi
F. KrueGer
--- SBBSecho 3.04-Win32
* Origin: Veleno BBS -
http://velenobbs.ddns.net (2:333/808)