On Thu, Sep 22, 2016 at 05:54:35AM -0400, adrhc wrote:
Hi there,
> What is the thing writing to nginx? (stunnel, I think)
> stunnel according to the setup:
I strongly suspect that your stunnel is not doing what you want it to do.
If you "tcpdump" the traffic out of stunnel; or if you replace
Hi, here's some clarifications:
What is the thing writing to nginx? (stunnel, I think)
stunnel according to the setup:
Transmission remote GUI:443 -> sshttp:443 -> stunnel:1443 ->
nginx:127.0.0.1:443 (no ssl, with listen ... proxy_protocol,
port_in_redirect on)
How is it configured?
[tls]
accept
On Wed, Sep 21, 2016 at 04:05:22AM -0400, adrhc wrote:
> Hi, the log come from nginx error log. I simply start the Transmission
> remote GUI and I get only this in error log:
This looks to me that the thing that is writing to nginx, is not writing
what nginx expects to read.
What is the thing
Hi, the log come from nginx error log. I simply start the Transmission
remote GUI and I get only this in error log:
2016/09/21 10:32:13 [error] 3909#0: *327 broken header: "> :
X,u \kc ; J=ޛXfoVr_<0 , ( $
k j i h 9 8 7 6 2 . * & = 5 / + ' #
On Mon, Sep 19, 2016 at 09:08:57AM -0400, adrhc wrote:
Hi there,
> nginx-1.11.3
> Transmission remote GUI:443 -> sshttp:443 -> stunnel:1443 ->
> nginx:127.0.0.1:443 (no ssl, with listen ... proxy_protocol,
> port_in_redirect on)
There are a lot of potential moving parts there.
>
Hi, while having this setup:
nginx-1.11.3
Linux utg353l 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Transmission remote GUI:443 -> sshttp:443 -> stunnel:1443 ->
nginx:127.0.0.1:443 (no ssl, with listen ... proxy_protocol,
port_in_redirect on)
