Good afternoon,

I am running Synchronet v3.19 for Windows. I have all been running with no issues until today or possibly yesterday. The web client hands up when trying to connect using the connect via telnet button.

The services have all worked, and the rest still do. This is the only known issue I am aware of. This could have been going on longer that just a few days. (I don't normally connect in this fashion) I use ssh, rlogin, or regular telnet.

Any ideas/thoughts would be greatly appreciated.

Thank you,

Jerry (Stingray)

Re: Web Client
By: StingRay to all on Fri Sep 20 2024 11:37 am

I am running Synchronet v3.19 for Windows. I have all been running with no issues until today or possibly yesterday. The web client hands up when trying to connect using the connect via telnet button.

The "web client" is fTelnet. fTelnet uses WebSockets to communicate with the terminal (Telnet) server. So your Synchronet web socket services (one for secure connections, one for non-secure) need to be working (they are by default) and the appropriate ports open in your firewall/gateway and/or port-forwarded to your BBS.
--
digital man (rob)

Sling Blade quote #2:
Karl (re: killing Doyle): I hit him two good whacks in the head with it.
Norco, CA WX: 73.5°F, 52.0% humidity, 1 mph SSE wind, 0.00 inches rain/24hrs

First, thank you for the quick reply.

I will have to dive deeper. All ports are open and firewall open. Everything was working fine and so far, the ftelnet is the only thing not currently working to my knowledge.

I have backups so I will try restoring if I can not figure it out.

-Jerry (Stingray)

Re: Web Client
By: StingRay to Digital Man on Fri Sep 20 2024 11:58 am

First, thank you for the quick reply.

I will have to dive deeper. All ports are open and firewall open. Everything was working fine and so far, the ftelnet is the only thing not currently working to my knowledge.

I have backups so I will try restoring if I can not figure it out.

backups will only help if you used to work fine, but now does not. So, that may not be the best plan.

Have you checked your services log output for connections to the web socket service(s) at the same time you're trying to use ftelnet?
--
digital man (rob)

Synchronet "Real Fact" #90:
Synchronet/DSZ "hack" of '93: http://wiki.synchro.net/history:hack93
Norco, CA WX: 73.5°F, 52.0% humidity, 1 mph SSE wind, 0.00 inches rain/24hrs

All systems had been running perfectly. I just got a wild hair and tried to log in today via web client and realized it was not working.

I just checked the log when trying to connect.

Fri Sep 20 14:51:41 2024 master/a2a9dc027 a-net-online.lol
srvc 2252 WSS TLS ERROR 'Data has not been initialised' (-11) setting session active

Fri Sep 20 14:51:41 2024 master/a2a9dc027 a-net-online.lol
srvc 1864 WSS TLS ERROR 'Data has not been initialised' (-11) setting session active

So, I assume the issue is going to be greater than I initially thought?

-Jerry (Stingray)

Re: Web Client
By: StingRay to Digital Man on Fri Sep 20 2024 12:11 pm

All systems had been running perfectly. I just got a wild hair and tried to log in today via web client and realized it was not working.

I just checked the log when trying to connect.

Fri Sep 20 14:51:41 2024 master/a2a9dc027 a-net-online.lol
srvc 2252 WSS TLS ERROR 'Data has not been initialised' (-11) setting session active

Fri Sep 20 14:51:41 2024 master/a2a9dc027 a-net-online.lol
srvc 1864 WSS TLS ERROR 'Data has not been initialised' (-11) setting session active

So, I assume the issue is going to be greater than I initially thought?

WSS service is the "Web Sockets Secure" service, so it's trying to use TLS (transation layer security, the same security system used to provide the [s] security in HTTPS). Looks like incoming TLS to the WSS isn't working. But https connections to your web server are working okay?
--
digital man (rob)

Rush quote #42:
Media messiahs preying on my fears, pop culture prophets playing in my ears Norco, CA WX: 74.6°F, 50.0% humidity, 1 mph SSE wind, 0.00 inches rain/24hrs

That is correct. HTTPS web connections are working, ssh and mail TLS are working as well.

That is what I found to be odd. Every service as been up and running for 20 days. I tried a system reboot & restarted my fiber router. Still the only thing I am finding to not work or "hang up" is the ftelnet when trying to use from the web client.

SSL is showing active and correct.

-Jerry (Stingray)

Re: Web Client
By: StingRay to Digital Man on Fri Sep 20 2024 12:45 pm

That is correct. HTTPS web connections are working, ssh and mail TLS are working as well.

That is what I found to be odd. Every service as been up and running for 20 days. I tried a system reboot & restarted my fiber router. Still the only thing I am finding to not work or "hang up" is the ftelnet when trying to use from the web client.

SSL is showing active and correct.

Strange. I have no immediate ideas.
--
digital man (rob)

Steven Wright quote #27:
Experience is something you don't get until just after you need it.
Norco, CA WX: 66.4°F, 71.0% humidity, 6 mph W wind, 0.00 inches rain/24hrs

I'll keep reading forums and digging in to it this afternoon.
Thanks again for your quick responses! Much appreciated!

-Jerry (StingRay)

---
￭ Synchronet ￭ ANETO

The log line you pasted indicates it's a TLS error, but not sure why the cert would work for https but not wss.

Does port 443 connect directly to Synchronet, or are you also running IIS and reverse proxying to Synchronet?

---
￭ Synchronet ￭ fTelnet Demo Server - ftelnet.synchro.net

Re: Web Client
By: StingRay to Digital Man on Fri Sep 20 2024 12:11:47

I just got a wild hair...

Then comb it! :)

---
■ Synchronet ■ End Of The Line BBS - endofthelinebbs.com

Re: Web Client
By: StingRay to all on Fri Sep 20 2024 11:37:50

Good afternoon,

I am running Synchronet v3.19 for Windows. I have all been running with no issues until today or possibly yesterday. The web
client
hands up when trying to connect using the connect via telnet button.

The services have all worked, and the rest still do. This is the only known issue I am aware of. This could have been going on
longer that just a few days. (I don't normally connect in this fashion) I use ssh, rlogin, or regular telnet.

Any ideas/thoughts would be greatly appreciated.

Thank you,

Jerry (Stingray)

I'm having the same issue. I'm using v3.20a on Rasbian.

Accessing https://lunarout.synchro.net:14443 from outside my LAN the "Connect via Telnet" doesn't work.

The telnet screen just goes black.

While on my LAN it does work.

Ports for my system are not standard at my firewall.

Looking through this thread. I didn't see a resolution for this issue.

StringRay, did you ever find a solution, or cause to the behavior?

---
■ Synchronet ■ Lunar Outpost BBS

Accessing https://lunarout.synchro.net:14443 from outside my LAN the "Connect via Telnet" doesn't work.

The telnet screen just goes black.

While on my LAN it does work.

Ports for my system are not standard at my firewall.

Check your port forwarding rules on your router/firewall and make sure that 14443 is open and pointed to your BBS machine.


* SLMR 2.1a * The first myth of management is that it exists.
---
■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Web Client
By: Dumas Walker to BBSING on Thu Nov 14 2024 10:10:00

Accessing https://lunarout.synchro.net:14443 from outside my LAN the "Connect via Telnet" doesn't work.

The telnet screen just goes black.

While on my LAN it does work.

Ports for my system are not standard at my firewall.

Check your port forwarding rules on your router/firewall and make sure that 14443 is open and pointed to your BBS machine.

Hi Dumas,

Its there. I can get to the webpage and login without using the "Connect via Telenet" button.

I've even opened standard ports, and still it doesn't work.

I'm not understanding why it just goes blank.

Are there logs specific to what I think is fTelnet?

I'm new to the setup of this system.

Take Care
Bbsing

---
■ Synchronet ■ Lunar Outpost BBS

Re: Web Client
By: bbsing to Dumas Walker on Thu Nov 14 2024 04:03 pm

Re: Web Client
By: Dumas Walker to BBSING on Thu Nov 14 2024 10:10:00

Accessing https://lunarout.synchro.net:14443 from outside my LAN the "Connect via Telnet" doesn't work.

The telnet screen just goes black.

While on my LAN it does work.

Ports for my system are not standard at my firewall.

Check your port forwarding rules on your router/firewall and make sure that 14443 is open and pointed to your BBS machine.

Hi Dumas,

Its there. I can get to the webpage and login without using the "Connect via Telenet" button.

I've even opened standard ports, and still it doesn't work.

I'm not understanding why it just goes blank.

Are there logs specific to what I think is fTelnet?

fTelnet uses Websockets, so you're interested in the WS and WSS services, configured in your ctrl/service.ini file.

See also https://wiki.synchro.net/faq:tcpip#ports
--
digital man (rob)

Breaking Bad quote #41:
Academy hire you right out of the womb? You guys get younger every year!
Norco, CA WX: 53.1°F, 85.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs

Re: Web Client
By: bbsing to Dumas Walker on Thu Nov 14 2024 04:03 pm

Howdy,

Accessing https://lunarout.synchro.net:14443 from outside my LAN the "Connect via Telnet" doesn't work.

The telnet screen just goes black.

Check your port forwarding rules on your router/firewall and make sure that 14443 is open and pointed to your BBS machine.

I've even opened standard ports, and still it doesn't work.

I'm not understanding why it just goes blank.

What ports have you opened?

The telnet connect button is making a websocket connection on port 11235. I've tried connecting to that port and got no response - so it's likely your firewall is dropping it, or if it is forwarding it, the host it is forwarding it to is either wrong, or if correct that host is dropping it.


...δεσ∩

---
■ Synchronet ■ AnsiTEX bringing back videotex but with ANSI

Ports for my system are not standard at my firewall.

Check your port forwarding rules on your router/firewall and make sure

hat

14443 is open and pointed to your BBS machine.

Its there. I can get to the webpage and login without using the "Connect via Telenet" button.

That proves that your web port is open (likely 80 unless you changed it to 14443). For ftelnet to work from remote, you also need to have a couple of other ports open. Check your ctrl\services.ini for the following sections:

;WebSocket service (for fTelnet loaded via http://).
;For troubleshooting, please see https://www.ftelnet.ca/synchronet/
[WS]
Port=1123
Options=NO_HOST_LOOKUP
Command=websocketservice.js

;WebSocket Secure service (for fTelnet loaded via https://).
;For troubleshooting, please see https://www.ftelnet.ca/synchronet/
[WSS]
Port=11235
Options=NO_HOST_LOOKUP | TLS
Command=websocketservice.js

If you don't have the ports listed open on your firewall, your remove
ftelnet connections won't work.

Are there logs specific to what I think is fTelnet?

That would be a question for digital man but, if those ports above are not open, I am not sure there would be any activity for synchronet to log.


* SLMR 2.1a * An atheist is a man with no invisible means of support.
---
■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Web Client
By: deon to bbsing on Fri Nov 15 2024 19:25:34

Re: Web Client
By: bbsing to Dumas Walker on Thu Nov 14 2024 04:03 pm

Howdy,

Accessing https://lunarout.synchro.net:14443 from outside my LAN the "Connect via Telnet" doesn't work.

The telnet screen just goes black.

Check your port forwarding rules on your router/firewall and make sure that 14443 is open and pointed to your BBS machine.

I've even opened standard ports, and still it doesn't work.

I'm not understanding why it just goes blank.

What ports have you opened?

I did not have port 11235 open. I do now and its working.

The telnet connect button is making a websocket connection on port 11235. I've tried connecting to that port and got no response - so it's likely your firewall is dropping it, or if it is forwarding it, the host it is forwarding it to is either wrong, or if correct that host is dropping it.

Thank you deon.

---
■ Synchronet ■ Lunar Outpost BBS

Re: Web Client
By: Dumas Walker to BBSING on Fri Nov 15 2024 09:31:00

Ports for my system are not standard at my firewall.

Check your port forwarding rules on your router/firewall and make sure

hat

14443 is open and pointed to your BBS machine.

Its there. I can get to the webpage and login without using the "Connect via Telenet" button.

That proves that your web port is open (likely 80 unless you changed it to 14443). For ftelnet to work from remote, you also need to have a couple of other ports open. Check your ctrl\services.ini for the following sections:

;WebSocket service (for fTelnet loaded via http://).
;For troubleshooting, please see https://www.ftelnet.ca/synchronet/
[WS]
Port=1123
Options=NO_HOST_LOOKUP
Command=websocketservice.js

;WebSocket Secure service (for fTelnet loaded via https://).
;For troubleshooting, please see https://www.ftelnet.ca/synchronet/
[WSS]
Port=11235
Options=NO_HOST_LOOKUP | TLS
Command=websocketservice.js

If you don't have the ports listed open on your firewall, your remove ftelnet connections won't work.

Ports in that service where not open. I didn't realize they needed to be open.

I've opened the secure port for fTelnet and its working properly.

Are there logs specific to what I think is fTelnet?

That would be a question for digital man but, if those ports above are not open, I am not sure there would be any activity for synchronet to log.

Thanks Dumas.

---
■ Synchronet ■ Lunar Outpost BBS

Re: Web Client
By: Digital Man to bbsing on Thu Nov 14 2024 22:51:39

Re: Web Client
By: bbsing to Dumas Walker on Thu Nov 14 2024 04:03 pm

Re: Web Client
By: Dumas Walker to BBSING on Thu Nov 14 2024 10:10:00

Accessing https://lunarout.synchro.net:14443 from outside my LAN the "Connect via Telnet" doesn't work.

The telnet screen just goes black.

fTelnet uses Websockets, so you're interested in the WS and WSS services, configured in your ctrl/service.ini file.

See also https://wiki.synchro.net/faq:tcpip#ports

Thank you Digital Man,

after reading the posts from you Dumas, Deon, and the wiki fTelnet is working.

I opened port 11235 and everything all is good with the webclient fTelnet.

Bbsing

---
■ Synchronet ■ Lunar Outpost BBS

Ports in that service where not open. I didn't realize they needed to be

pen.

I've opened the secure port for fTelnet and its working properly.

Good deal!


* SLMR 2.1a * Do device drivers need a chauffeur's license?
---
■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Web Client
By: Dumas Walker to BBSING on Sat Nov 16 2024 12:35:00

Ports in that service where not open. I didn't realize they needed to be

pen.

I've opened the secure port for fTelnet and its working properly.

Good deal!

Thanks for your help Dumas.

---
■ Synchronet ■ Lunar Outpost BBS