From: Jeroen van Veen <jvanveen@protonmail.com>
To: "galene@lists.galene.org" <galene@lists.galene.org>
Subject: [Galene] Websocket close 1006 (abnormal closure): unexpected EOF
Date: Tue, 05 Jan 2021 10:56:25 +0000 [thread overview]
Message-ID: <0-dxBS5LC_odE5dSkuOGwoOb2FmQ7PYcbBgSGpmtz2R1ek9xklqHKQ6UCO11J1JvU5np1csOcujLTfM3ZU_48ub3yZ1EQRcYuTbarD6EkN4=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Hi,
I've been testing with Galene a bit, but noticed that I got disconnected automatically after a while.
It seems that mywebsocket connection is killed:
2021/01/05 11:24:22 client: websocket: close 1006 (abnormal closure): unexpected EOF
Another client had no disconnect issues at all. I'm not sure if this is a Gorilla websocket issue(https://stackoverflow.com/questions/61108552/go-websocket-error-close-1006-abnormal-closure-unexpected-eof), an unstable wifi connection at my side or whether Nginx may be an issue. Anyone?
My nginx config:
server {
listen 443 ssl;
server_name galene.domain.app;
index index.html;
access_log /var/log/nginx/galene.domain.app.access.log;
error_log /var/log/nginx/galene.domain.app.error.log;
location /ws {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host;
proxy_pass https://127.0.0.1:8443;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}
location / {
proxy_pass https://127.0.0.1:8443;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}
ssl_certificate /etc/letsencrypt/live/galene.domain.app/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/galene.domain.app/privkey.pem; # managed by Certbot
}
[-- Attachment #2: Type: text/html, Size: 5084 bytes --]
next reply other threads:[~2021-01-05 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 10:56 Jeroen van Veen [this message]
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
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='0-dxBS5LC_odE5dSkuOGwoOb2FmQ7PYcbBgSGpmtz2R1ek9xklqHKQ6UCO11J1JvU5np1csOcujLTfM3ZU_48ub3yZ1EQRcYuTbarD6EkN4=@protonmail.com' \
--to=jvanveen@protonmail.com \
--cc=galene@lists.galene.org \
/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