echicken wrote to Hemo <=-
Re: Thanks for the new web interface
By: Hemo to Accession on Thu Dec 15 2016 16:31:17
sigh< yeah. got those. I see the connect in the sbbs.log, butlogin, then eventually drops the connect.
never send the
Which connection do you see happening in your logs? There should be
two:
Step one: fTelnet connects to the websocket server
Step two: the websocket server connects to your terminal server
Step two happens locally, so the telnet (or rlogin) connection would appear to be coming from localhost.
I have the whole section added to modopts.ini, made sure the [logon] section was setup as shown.
Dec 15 21:44:54 agility synchronet: srvc 0048 WebSocketRLogin RLogin: Unable to connect to server.
It says unable to connect to server. At this point, I don't know where the WebSocketRLogin is trying to connect to. The ip of the local nic adapter
echicken wrote to Hemo <=-
Re: Thanks for the new web in
By: Hemo to echicken on Thu Dec 15 2016 22:06:00
I have the whole section added to modopts.ini, made sure the [logon] section was setup as shown.
For the record, that only matters for the "Games" page.
Dec 15 21:44:54 agility synchronet: srvc 0048 WebSocketRLogin RLogin: Unable to connect to server.
It says unable to connect to server. At this point, I don't know where the WebSocketRLogin is trying to connect to. The ip of the local nic adapter
It's trying to connect to what's exported to the JS environment as 'system.inet_addr'. I suspect that in your case, your BBS server is unable to properly resolve or connect to this address.
I recommended replacing references to 'system.inet_addr' in websocket-telnet-service.js with '"127.0.0.1"' - have you tried that
yet? I expect it will solve your problem. If it does, do the same to websocket-rlogin-service.js.
tried that. same results - no change. I tried 127.0.0.1, the local internal ip of 192.168.1.130, the IP of the router, the public ip.
Re: Thanks for the new web in16 2016 16:56:00
By: Hemo to echicken on Fri Dec
tried that. same results - nochange. I tried 127.0.0.1, the local
internal ip of 192.168.1.130, theIP of the router, the public ip.
On your BBS server, please tryusing telnet client to connect to all
the above on ports 23 and 513 (orwherever ports your system is
listening on for telnet and rloginclients). What are the results?
After I changed SCFG’!Networks’!Internet
E-mail Address to bbs.ujoint.org and
restarted things, it works.
else, and the system.inet_addr value in
the javascript is getting the entry
from SCFG’!Networks’!Internet E-mail
Based on what I've switched to make
things work, I would guess that the
sbbs.ini value is used for something
else, and the system.inet_addr value in
the javascript is getting the entry
from SCFG’!Networks’!Internet E-mail
Address.
Re: Thanks for the new web in
By: Hemo to echicken on Sun Dec 18 2016 10:32:00
After I changed SCFG’!Networks’!Internet
E-mail Address to bbs.ujoint.org and
restarted things, it works.
You don't necessarily need to keep it that way; it was probably just a bad idea for me to use system.inet_addr to begin with. Changes I pushed to the websocket proxy services should work around this altogether.
Anyway, the websocket servers will now proxy to the TelnetInterface / RLoginInterface as configured in sbbs.ini, or if that is not configured (or set to 0.0.0.0) it will connect to 127.0.0.1.
Incidentally, your message seemed to be wrapping at around 40 columns. How did you post that message?
Sysop: | Ragnarok |
---|---|
Location: | Dock Sud, Bs As, Argentina |
Users: | 136 |
Nodes: | 10 (0 / 10) |
Uptime: | 62:15:41 |
Calls: | 15,175 |
Calls today: | 2 |
Files: | 19,862 |
D/L today: |
86 files (16,573K bytes) |
Messages: | 1,693,889 |