Login hangs silently when the relay refuses the connection

littlefox commented

2026-10-18 22:01:08 +00:00

Owner

When kom-relay refuses a WebSocket (HTTP 503: too many connections from this address, or in all; or 403 for an origin not allowed), the login page just stays as it is: no message, the button seemingly doing nothing. Found in the e2e suite, where specs that left extra browsers open filled the relay's per-address limit (8) and a later login hung for 15 s (the specs are fixed to close them).

The app should say what happened, e.g. 'Reläet tar inte emot fler anslutningar från din adress just nu' for 503 and 'Reläet tillåter inte den här sidan' for 403, and offer to try again.

When kom-relay refuses a WebSocket (HTTP 503: too many connections from this address, or in all; or 403 for an origin not allowed), the login page just stays as it is: no message, the button seemingly doing nothing. Found in the e2e suite, where specs that left extra browsers open filled the relay's per-address limit (8) and a later login hung for 15 s (the specs are fixed to close them). The app should say what happened, e.g. 'Reläet tar inte emot fler anslutningar från din adress just nu' for 503 and 'Reläet tillåter inte den här sidan' for 403, and offer to try again.

littlefox added the

kind/bug

area/web

labels

2026-10-18 22:01:08 +00:00

littlefox referenced this issue

2026-10-18 22:10:33 +00:00

Inbox as chats: personal texts grouped by who they're with #134

littlefox referenced this issue from a commit

2026-10-18 22:10:34 +00:00

Inbox as chats: personal texts grouped by who they're with

littlefox referenced this issue from a commit

2026-10-19 07:57:52 +00:00

Say why when the relay refuses the connection

littlefox referenced this issue from a pull request that will close it,

2026-10-19 07:57:56 +00:00

Say why when the relay refuses the connection #142

littlefox closed this issue

2026-10-19 08:28:21 +00:00

littlefox commented

2026-10-19 08:28:26 +00:00

Author

Owner

Merged in #142. The relay now accepts a connection it won't serve and closes it at once with 4004 (full for your address), 4005 (full) or 4006 (page not allowed). The login says which, instead of 'Kunde inte nå servern… kontrollera adressen'.

Verified:

relay integration tests for per-address, total, X-Forwarded-For and origins;
new e2e relay.spec in Chromium (a full relay, a disallowed origin, and no relay at all, with relays on 4901/4903 in tools/e2e.sh);
tls.spec still passes;
CI green.

Merged in #142. The relay now accepts a connection it won't serve and closes it at once with 4004 (full for your address), 4005 (full) or 4006 (page not allowed). The login says which, instead of 'Kunde inte nå servern… kontrollera adressen'. Verified: - relay integration tests for per-address, total, X-Forwarded-For and origins; - new e2e relay.spec in Chromium (a full relay, a disallowed origin, and no relay at all, with relays on 4901/4903 in tools/e2e.sh); - tls.spec still passes; - CI green.

Rows
Columns

Login hangs silently when the relay refuses the connection #133