Re: Re: synchronet behind a reverse proxy
By: martylake to deon on Thu Nov 25 2021 10:23 am
> > So reconfigure the websockets part to connect to haproxy's port, not SBBS directly.
>
> The issue is that websocket is a protocol on top of http, that's why we need a websocket->telnet proxy. The issue if I understand correctly is that this proxy is not forwarding haproxy information to the backend.
Correct, there are two paths that could address this.
* The websocket connects to haproxy, not SBBS directly.
* The websocket speaks that haproxy protocol when talking with SBBS directly.
The first is probably easy to do, if you can configure it via a config file (sorry I dont know).
The second would require development I'm guessing...
...лоеп
---
ю Synchronet ю Alterant | an SBBS in Docker on Pi!
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
|