Subj : Re: synchronet behind a reverse proxy
To   : martylake
From : deon
Date : Thu Nov 25 2021 10:43:15

  Re: Re: synchronet behind a reverse proxy
  By: martylake to martylake on Wed Nov 24 2021 01:23 am

Hey Marty,

 > I am in the process of replacing traefik with haproxy. I got ssh, webv4 and telnet working so far.
 >
 > ws is a bit problematic because haproxy (from 2.1 https://www.haproxy.com/fr/blog/haproxy-2-1/ ) Defaulted HTTP Representation to HTX . Which means it feeds lowercased headers, and one needs to override this behavior by providing a dictionnary of
 > headers not to be lowercased, and this insulting option h1-case-adjust-bogus-server
 >
 > With that solved, if I disable synchronet's HA_PROXY, the ws telnet works great. But if I enable HA_PROXY, term is complaining that ws did not provide enough information and shut downs the connexion.

I dont use websockets, so I dont know the extent to which it can be configured.

Your problem is this

 > 11/24 09:16:12 srvc 0037 WS Connecting to localhost:23

When you enable HAPROXY, the only connections that can come in from port 23 are *from* haproxy. If the websockets is connecting directly to port 23, then the haproxy code will drop the connection, as seen by:

 > 11/24 09:16:12 term 0040 Working out client address from HAProxy PROTO
 > 11/24 09:16:13 term 0040 multisock read_socket() - No data?

So reconfigure the websockets part to connect to haproxy's port, not SBBS directly.


....лоеп

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

.