Subj : Re: synchronet behind a reverse proxy
To   : echicken
From : martylake
Date : Fri Nov 26 2021 13:54:55

  Re: Re: synchronet behind a reverse proxy
  By: echicken to martylake on Fri Nov 26 2021 01:46 pm

 > Good catch - thank you.
You are welcome.

 > I have no problem with it, especially if it's well-formatted for the medium
 > (80x24).
Duely noted.

 > I just pushed a couple of changes: your patch, and a fix because the
 > websocket service was sending the wrong client address. Please update and
 > let me know how it goes.
I just pulled, and I confirm it works great for me. I did not a difference for the address fix, as I˙use the same computer for dev and testing. I looks good to me though.

What is the process to deliver this fix to the docker image ? And how do you manage synchronet's configuration files with regard to upgrading synchronet ? The way I did it (modifying the files in ctrl/ and overwriting /web from /backups), I feel like I will loose these modifications next time I pull, but maybe I am wrong ?



I have an unrelated issue, should I open a new "thread" for it ? YMODEM-G upload with the ftelnet ws works for very small files (<144ko) but does not work anymore for bigger files (>174ko).

Here are the logs. I don't know how to paste from syncterm, but I will type them:
* sexyz: !Receive timeout (3 seconds)
this one several times while I˙choose the menu upload and selets my file in the OS file picker
* sexyz: !Too many errors (1)
* sexyz: !File Transfer Failure
* sexyz: !Error fetching YMODEM header block
While this happens, ftelnet sends all the file, and synchronet treats them as inputed keys.

I don't reproduce the issue if I upload files using syncterm.

Is it a known defect ?

Best,
--- SBBSecho 3.14-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.