Documentation contents

I can’t sign in

Check the message Gadka displays. What you do next depends on whether your password is incorrect, you lack access or you’ve made too many attempts.

Messages on the login screen

MessageCauseWhat to do
No Gadka server responds at this address.The domain or port is incorrect, or the server is unavailable.Check the domain. See The app can’t connect to the server.
Incorrect workspace, email or password.One of the three fields is incorrect.Check the workspace name (lowercase), email address, and password.
Too many sign-in attempts. Try again in … seconds.You’ve reached the limit on attempts to sign in.Wait for the time shown.
This account has been deactivated.An administrator disabled the account.Ask your administrator to reactivate it.
Invalid code. Try again.The authentication code (2FA) is incorrect.Check the time on your phone and enter a fresh code.
The sign-in attempt expired. Sign in again.The session timed out before you entered the code.Start signing in again.
This account has no access to this workspace. Ask an administrator for an invitation.You’re using SSO and have no Gadka account.Ask for an invitation.
Single sign-on failed. Try again.Gadka couldn’t sign you in through SSO.Try again and report the error to your administrator.
The identity provider is temporarily unavailable. Try again shortly.The server can’t reach the identity provider.Try again later.

I forgot my password

Gadka doesn’t send emails, so you won’t receive a link to reset your password.

  • If your organization uses SSO, select Sign in with ….
  • Otherwise, contact your administrator.

See Outgoing email and invitations.

I don’t have the phone with my 2FA codes

  1. On the Two-step verification screen, select Use a recovery code.
  2. Enter one of the codes you saved when you enabled 2FA.
  3. After signing in, set up 2FA on your new phone. See Set up 2FA.

I can’t see the SSO button

  • Enter both the domain and the workspace name to display the button.
  • The Windows and Linux apps don’t support SSO yet. Sign in with your password.

If you see This invitation is invalid or has expired., someone has already used or revoked the link, or the link expired after seven days. Ask your administrator for a new invitation.

For server administrators

SymptomWhat to check
Nobody can sign in.Run systemctl status gadka gadka-proxy and journalctl -u gadka -n 50.
Everyone sees Too many sign-in attempts at the same time.Installations from before version 0.3.2 lack the api.trusted_proxies setting. Add it as described in Configuration file.
An existing user is denied access through SSO.The identity provider may be omitting email_verified: true or sending a different email address from the one in Gadka.
Two-step verification is not configured on this server.The file specified by crypto.mfa_key_file is missing.
The only owner has lost access.Create a new owner account with gadka admin user-create --role owner.