# What do you want to address?
(This step is required; examples are shown below)
# Describe your matter briefly
To reproduce this bug:
- Using Gitea web, create a new user as a Gitea admin. Do not log in.
- Attempt to log in to the new account with the Gitnex mobile app, using basic HTTP auth. In real life this situation would be as if a Gitea admin gave a fresh account to a mobile user and asked them to log in using the provided credentials.
What did you expect? (Useful when addressing bugs)
I expect a screen to show up saying “Welcome to Gitea! Please change your password now.”
Instead, I get a toast saying “Could not reach server.”
If I try multiple times I get the same result. Can’t log in.
When I examine my Gitea logs I see that Gitnex is attempting to call the
change_password endpoint but the UI is failing to handle the result of the call, preventing me from signing in:
2020-08-30 05:18:08: Started GET /api/v1/version for <CLIENT IP> 2020-08-30 05:18:08: Completed GET /api/v1/version 302 Found in 39.127934ms 2020-08-30 05:18:08: Started GET /user/settings/change_password for <CLIENT IP> 2020-08-30 05:18:08: Completed GET /user/settings/change_password 200 OK in 25.133715ms
I resolved the issue by logging in to Gitea with the new account with Gitea web, and changing the password there. I was then able to log in with the new password in Gitnex.
Some additional details (Useful, when we are trying to reproduce a bug)
- The version of Gitea you are using: 1.12
- The version of GitNex you are using: 3.1
- Phone OS version and model: Android
- The type of certificate you are using (self-signed, signed): none
- How you used to log in (via password or token): basic HTTP auth password
PS: this caused me quite a bit of confusion! I didn’t know what was wrong until I inspected the Gitea logs. I was worried I needed to be using HTTPS or something.