Skip to content

fix(signin): say why a sign-in couldn't start in plain words - #25

Merged
otherworld-dev merged 2 commits into
devfrom
d907-plain-signin-errors
Nov 6, 2026
Merged

otherworld-dev merged 2 commits into
devfrom
d907-plain-signin-errors

Conversation

@otherworld-dev

Copy link
Copy Markdown
Owner

When the server couldn't be reached, sign-in showed the raw Go error. It now says what went wrong in a short sentence naming the server: no answer, address not found, connection refused, untrusted certificate, a 404, a server error, or an answer that isn't Nextcloud. The raw error still goes to the log.

When the server didn't answer, Android's sign-in screen showed the raw Go
error ("start login flow: Post …: context deadline exceeded (Client.Timeout
exceeded while awaiting headers)") and the desktop window showed the same
behind "error:". Starting the login flow now returns a short message naming
the server for the common cases: no answer in time, address not found,
connection refused, untrusted certificate, a plain-http server typed without
http://, a 404 (with a hint about Nextcloud in a subfolder), a server error,
and an answer that isn't Nextcloud. The raw error still goes to the log and
stays wrapped for errors.Is. Both apps get it, they show the text as it comes.
d907
# Conflicts:
#	cmd/nimbo-gui/frontend/dist/assets/index-B4DLXM4K.js
#	cmd/nimbo-gui/frontend/dist/assets/index-B_IgXu9_.js
#	cmd/nimbo-gui/frontend/dist/assets/index-DtAKrFT6.js
#	cmd/nimbo-gui/frontend/dist/index.html
@otherworld-dev
otherworld-dev merged commit 0fb66e6 into dev Nov 6, 2026
3 checks passed
@otherworld-dev
otherworld-dev deleted the d907-plain-signin-errors branch November 6, 2026 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant