From: Jeroen van Veen <jvanveen@protonmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Juliusz Chroboczek <jch@irif.fr>,
"galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Re: Websocket close 1006 (abnormal closure): unexpected EOF
Date: Tue, 05 Jan 2021 18:16:57 +0000 [thread overview]
Message-ID: <N398smZMbKqVq1MFM8wuaZyCPbWmNjq1RCDZ9ck9gE9vijVRRjqUR--_AhwiVd6mi511L0CI0RDe37wJk7MX53xHSpZg203Ej37sgDvJwCs=@protonmail.com> (raw)
In-Reply-To: <87v9cba11z.fsf@toke.dk>
Thanks for the help and info! I tested both the patch and the proxy timeout config
change. The patch fixes the issue with the default nginx timeout and the config does
the same using the existing code.
cheers,
Jeroen
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Op dinsdag, januari 5, 2021 3:52 PM, Toke Høiland-Jørgensen <toke@toke.dk> schreef:
> 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;
>
> in my nginx config (though I'm not proxying Galene)...
>
> -Toke
>
> Galene mailing list -- galene@lists.galene.org
> To unsubscribe send an email to galene-leave@lists.galene.org
next prev parent reply other threads:[~2021-01-05 18:17 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 [this message]
2021-01-05 18:44 ` Michael Ströder
2021-01-05 21:49 ` Toke Høiland-Jørgensen
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='N398smZMbKqVq1MFM8wuaZyCPbWmNjq1RCDZ9ck9gE9vijVRRjqUR--_AhwiVd6mi511L0CI0RDe37wJk7MX53xHSpZg203Ej37sgDvJwCs=@protonmail.com' \
--to=jvanveen@protonmail.com \
--cc=galene@lists.galene.org \
--cc=jch@irif.fr \
--cc=toke@toke.dk \
/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