From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Michael Ströder" <michael@stroeder.com>,
"galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Re: Websocket close 1006 (abnormal closure): unexpected EOF
Date: Tue, 05 Jan 2021 22:49:04 +0100 [thread overview]
Message-ID: <87h7nv9hrj.fsf@toke.dk> (raw)
In-Reply-To: <59143aab-df95-92d8-db78-3129c2e02fb4@stroeder.com>
Michael Ströder <michael@stroeder.com> writes:
> On 1/5/21 3:52 PM, Toke Høiland-Jørgensen wrote:
>> Juliusz Chroboczek <jch@irif.fr> writes:
>>
>>>> I've been testing with Galene a bit, but noticed that I got disconnected
>>>> automatically after a while.
>>>
>>> Nginx timing out the websocket, perhaps? Could you please try with the
>>> following patch applied?
>>
>> Yeah, the default timeout in nginx is 60s:
>> https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_read_timeout
>>
>> so if Galene actually waits that long it is likely that it trips the
>> timeout...
>>
>> I just normally put
>>
>> proxy_read_timeout 1200s;
>> proxy_send_timeout 1200s;
>
> 20min? Really? Even 120s would be quite long.
Yeah, won't necessarily recommend this for an internet-facing
deployment. But this is mostly for services I run for myself internally
(and I'm not proxying Galene at all), and the server has plenty of
resources to spare to keep a few sockets open :)
-Toke
next prev parent reply other threads:[~2021-01-05 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 10:56 [Galene] " Jeroen van Veen
2021-01-05 14:42 ` [Galene] " Juliusz Chroboczek
2021-01-05 14:52 ` Toke Høiland-Jørgensen
2021-01-05 18:16 ` Jeroen van Veen
2021-01-05 18:44 ` Michael Ströder
2021-01-05 21:49 ` Toke Høiland-Jørgensen [this message]
2021-01-08 13:19 ` Juliusz Chroboczek
2021-01-08 14:24 ` Michael Ströder
2021-01-08 14:58 ` Juliusz Chroboczek
2021-01-08 16:03 ` Michael Ströder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7nv9hrj.fsf@toke.dk \
--to=toke@toke.dk \
--cc=galene@lists.galene.org \
--cc=michael@stroeder.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox