Subj : Re: synchronet behind a reverse proxy
To   : martylake
From : deon
Date : Fri Nov 26 2021 16:22:34

  Re: Re: synchronet behind a reverse proxy
  By: martylake to deon on Thu Nov 25 2021 08:34 pm

Howdy,

 >  > The first is probably easy to do, if you can configure it via a config file (sorry I dont know).
 >
 > Unfortunately, there seems to be lots of options for forwarding websocket to a websocket server:
 >   internet-ws -> haproxy -> server ws
 > but no option for proxying:
 >   internet-ws -> haproxy -> raw tcp with haproxy_proto preamble

Not sure we are talking the same thing...

For normal telnet it is this:

telnet -> haproxy (telnet port) -> sbbs (telnet port).

So, for websocket telnet client, it would be:

browser -> haproxy (http port) -> websocket -> haproxy (telnet port) -> sbbs (telnet port)

Or, if websocket can talk haproxy proto:

browser -> haproxy (http port) -> websocket -> sbbs (telnet port with haproxy proto introduction)

Looks like echicken was working on the last item - I would have thought for the first one, you can change "localhost:23" to "haproxy:23"?


....лоеп

---
 ю Synchronet ю Alterant | an SBBS in Docker on Pi!
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.