i remember, some time in the last several weeks, that someone else had a problem using https and wss but i don't recall the particulars of the solution...
currently i have http/ws working fine so members can use the web interface (original default theme) to access the doors... yesterday i've set up the letsyncrypt stuff and now have working https (for the first time ever) but when
i try to access the doors, ftelnet says that it cannot connect to my wss port (11245)... sync is listening on that port but i can't get there for some reason... it is properly forwarded in my firewall/router and my firewall/router
does hairpinning properly...
i'm not sure what i'm missing :?
i'm not sure what i'm missing :?
Did you put WSS on port 11245 or is that a typo meaning 11235?
Perhaps check both SBBS services.ini and your routers port forwarding
and make sure they match.
i remember, some time in the last several weeks, that someone else had a problem using https and wss but i don't recall the particulars of the solution...
currently i have http/ws working fine so members can use the web interface (original default theme) to access the doors... yesterday i've set up the letsyncrypt stuff and now have working https (for the first time ever) but when
i try to access the doors, ftelnet says that it cannot connect to my wss port (11245)... sync is listening on that port but i can't get there for some reason... it is properly forwarded in my firewall/router and my firewall/router
does hairpinning properly...
i'm not sure what i'm missing :?
i'm not sure what i'm missing :?
By default it tries to connect to localhost.
If you want to use a different interface, specify the IP or hostname
on the command-line(s) in services.ini:
[WSS] Port=11235
Options=NO_HOST_LOOKUP|TLS
Command=websocket service.js synchro.net
On 2019 Feb 20 15:18:10, you wrote to me:^^^^^
connections to port 11245 work just fine to/from localhost over both IPv4
^^^^^If you want to use a different interface, specify the IP or hostname
on the command-line(s) in services.ini:
[WSS] Port=11235
Options=NO_HOST_LOOKUP|TLS
Command=websocket service.js synchro.net
On 2019 Feb 20 15:18:10, you wrote to me:line,
i'm not sure what i'm missing :?
By default it tries to connect to localhost.
thanks, rob... from what i can see, using netcat on the sestar command
connections to port 11245 work just fine to/from localhost over both IPv4 and IPv6... at least i can connect and see that connection in the logs... after that i just CTRL-C 'cause there's nothing else i can do at thatpoint
;)
i'm kinda wondering, now, if i should somehow disable IPv6 in sbbs to eliminate
that maybe there's some sort of IPv4->IPv6 attempt going on? i don't use IPv6 at all even though it is operational... my router/firewall can't do IPv6 so it is blocked at the perimeter in both directions...
unfortunately those links above are broken but i found this on https://www.ftelnet.ca/download/ ... is the #1 statement still true or is the note out of date?
----- snip -----
If you can't/don't want to run fTelnetProxy, then there are two other options. I don't regularly test with these other proxies though, so I make no guarantee that I won't break things for them in the future (I won't intentionally do it, but I may unintentionally do it and not realize because I don't have the time to test with all three on a regular basis)
1. If you run Synchronet, you can try websocketservice.js. NOTE: This does not support secure wss:// connections at this time
Re: https to wss
By: mark lewis to all on Wed Feb 20 2019 09:23 am
By default it tries to connect to localhost. If you want to use a different interface, specify the IP or hostname on the command-line(s) in services.ini: [WSS]
Port=11235
Options=NO_HOST_LOOKUP|TLS
Command=websocketservice.js synchro.net
digital man
Re: https to wss
By: mark lewis to all on Wed Feb 20 2019 09:23 am
inBy default it tries to connect to localhost. If you want to use a different interface, specify the IP or hostname on the command-line(s)
services.ini: [WSS]
Port=11235
Options=NO_HOST_LOOKUP|TLS
Command=websocketservice.js synchro.net
digital man
Interesting, so if I have, say, 3 systems each running an instance of Synchronet I could point 2 of them to the one that I want my DOORS to run on? ie:
[WSS]
Port=11235
options=NO_HOST_LOOKUP|TLS
Command=websocketservice.js alleycat.synchro.net
[WS]
Port=1235
options=NO_HOST_LOOKUP
Command=websocketservice.js alleycat.synchro.net
Re: Re: https to wss
By: Mortifis to Digital Man on Wed Feb 20 2019 08:53 pm
Re: https to wss
By: mark lewis to all on Wed Feb 20 2019 09:23 am
command-line(s)By default it tries to connect to localhost. If you want to use a different interface, specify the IP or hostname on the
runin services.ini: [WSS]
Port=11235
Options=NO_HOST_LOOKUP|TLS
Command=websocketservice.js synchro.net
digital man
Interesting, so if I have, say, 3 systems each running an instance of Synchronet I could point 2 of them to the one that I want my DOORS to
on? ie:
[WSS]
Port=11235
options=NO_HOST_LOOKUP|TLS
Command=websocketservice.js alleycat.synchro.net
[WS]
Port=1235
options=NO_HOST_LOOKUP
Command=websocketservice.js alleycat.synchro.net
If they're all sharing the same userbase.
digital man
workgroupIf they're all sharing the same userbase.
It's been 20+ years since I did that, one system is Linux, one is win7 and another is win10 ... I suppose if I have the 2 windows on the same
and set the /sbbs/data/user on primary windows that has the user base Iwant
and doors as a shared folder and setup Samaba on the Linuxbox and set SCFG user base to the winblows7? or be lazy and duplcate the user base on all systems ...
You keep saying 11245 is that intentional? the actual default wss port is 11235
i'm kinda wondering, now, if i should somehow disable IPv6 in sbbs to
eliminate that maybe there's some sort of IPv4->IPv6 attempt going on?
i don't use IPv6 at all even though it is operational... my
router/firewall can't do IPv6 so it is blocked at the perimeter in
both directions...
What is/are the exact error message(s) being displayed and logged when
the connection attempt fails?
1. If you run Synchronet, you can try websocketservice.js. NOTE: This
does not support secure wss:// connections at this time
websocketservice.js supports WSS now.
What is/are the exact error message(s) being displayed and logged when
the connection attempt fails?
i was getting this...
Feb 21 10:19:10 sestar sbbs: web 0058 HTTPS connection accepted from: 192.168.42.1 port 49785
Feb 21 10:19:10 sestar sbbs: web 0058 TLS ERROR 'Bad argument,
parameter 3' (-3) setting private key
Feb 21 10:19:10 sestar sbbs: web 0058 TLS ERROR 'Data has not been initialised' (-11) setting session active
now i'm getting the above again... this after several working accesses... then suddenly firefox is saying it can't validate the returned data (i think) and the above error lines are being logged...
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 42:39:15 |
Calls: | 6,648 |
Files: | 12,193 |
Messages: | 5,329,574 |