1. Forum
  2. FidoNet
  3. SYNCHRONET

  • Re: synchronet behind a reverse proxy

    From Tracker1@1:103/705 to martylake on Wednesday, December 01, 2021 23:17:57
    On 11/24/21 12:52, martylake wrote:

    Is your syncrhonet running on Windows by chance?

    Unfortunately not. It's running on raspberrypi4 raspbian under docker.

    Are you running the bbs-io image, or something you cooked up?

    Only asking as I was considering changing on how the volumes are done... instead of having each subdirectory under sbbs mounted, simply mounting /sbbs-files and the "init" at startup would symlink from /sbbs (this way
    /exec in particular is still preserved/original and the rest would
    largely work the same.
    --
    Michael J. Ryan - tracker1@roughneckbbs.com
    ---
    ￭ Synchronet ￭ Roughneck BBS - roughneckbbs.com
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tracker1@1:103/705 to martylake on Wednesday, December 01, 2021 23:29:30
    On 11/25/21 14:04, martylake wrote:
    Sorry, I should have asked if you did a development / git-based installation >> in the first place. Once you have one working, let me know. I'll tinker with >> this a bit tonight if I'm able, or tomorrow.

    Ok, I will focus on getting a git-based installation ready ASAP and let you know. Thank you very much for offering help on that !
    The daily builds of the bbs-io/synchronet image is from git... anything committed should arrive as a new nightly within 48 hours.

    nightly-20211201
    Last pushed 14 hours ago by tracker1

    https://hub.docker.com/repository/docker/bbsio/synchronet/tags
    --
    Michael J. Ryan - tracker1@roughneckbbs.com
    ---
    ￭ Synchronet ￭ Roughneck BBS - roughneckbbs.com
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tracker1@1:103/705 to deon on Wednesday, December 01, 2021 23:33:17
    On 11/25/21 16:38, deon wrote:
    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...

    The haproxy websocket connection should forward the given path(s) to the websocket port on synchronet as a tcp connection... or upcycle... I
    don't know if haproxy supports acting as a websocket<->tcp gateway directly.

    I've tried to make a specific path or websocket connection upgrade work
    to reverse-proxy to a different port, but it doesn't want to work
    correctly... kind of wish that websocket connection
    support/configuration was directly in the sbbs http service itself,
    which would make that part much easier to work with.
    --
    Michael J. Ryan - tracker1@roughneckbbs.com
    ---
    ￭ Synchronet ￭ Roughneck BBS - roughneckbbs.com
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tracker1@1:103/705 to echicken on Wednesday, December 01, 2021 23:35:13
    On 11/26/21 02:08, echicken wrote:

    You mentioned something in an earlier message about HAProxy
    lowercasing the names of HTTP headers. If the client sends 'Some-
    Header: Some Data', can I expect the upstream to receive 'some-header:
    Some Data'? This will become important, because it looks like the
    websocket service currently does case-sensitive matching on header
    lines.

    The name portion of headers is supposed to be case-insensitive for HTTP.
    And from the prior message, that's my understanding is that it is
    indeed normalizing to lower-case.
    --
    Michael J. Ryan - tracker1@roughneckbbs.com
    ---
    ￭ Synchronet ￭ Roughneck BBS - roughneckbbs.com
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tracker1@1:103/705 to echicken on Wednesday, December 01, 2021 23:41:02
    On 11/27/21 13:06, echicken wrote:
    Okay, so it sounds like various cases are being handled as
    expected. I'll merge this in later today.

    Thanks for your help with testing all of that - I made these
    changes without actually running any of the scripts myself.

    Sorry for jumping in late on this one... was just catching up on messages.
    --
    Michael J. Ryan - tracker1@roughneckbbs.com
    ---
    ￭ Synchronet ￭ Roughneck BBS - roughneckbbs.com
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From martylake@1:103/705 to Tracker1 on Monday, December 06, 2021 01:48:03
    Re: Re: synchronet behind a reverse proxy
    By: Tracker1 to martylake on Wed Dec 01 2021 11:17 pm

    Dear Tracker|
    Are you running the bbs-io image, or something you cooked up?
    Yes, I am running the nightly from docker hub.

    Only asking as I was considering changing on how the volumes are done... instead of having each subdirectory under sbbs mounted, simply mounting /sbbs-files and the "init" at startup would symlink from /sbbs (this way /exec in particular is still preserved/original and the rest would
    largely work the same.
    It sounds like a good idea to me, even if I don't understand what would be the benefits apart from saving some lines of volumes mount in docker-compose.yml ?
    --- SBBSecho 3.14-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)