Troubleshooting
"No GateKeeper account exists for this email"
Your Google sign-in worked; you just don't have a GateKeeper account yet. Somebody with user administration rights needs to create one. See Signing in.
Only @gcdtech.com accounts may sign in
You picked a personal Google account. Sign out of Google, or use the account chooser to pick your work account.
"You do not have access to this account"
You don't hold a permission on it. The dropdown lists every registered account, not only yours — see Permissions for how access is granted and what to ask for.
If you did have access recently, the likeliest explanations are an expired temporary grant or being removed from an access group.
My AWS credentials stopped working
They expired. Every session lasts at most an hour, and that limit can't be raised.
Get a fresh set, and if it keeps interrupting you, switch to the
command line tool — it renews in the background, and
credential_process keeps long jobs running.
The website keeps asking me to sign in
The site renews itself quietly, but it can only do that if the browser can tell which Google account to use without asking. Common causes:
- you're signed into several Google accounts in that browser;
- you signed out of Google, or your Google session expired;
- you dismissed the Google prompt enough times that it's being suppressed.
Signing in normally once usually settles it. A private window is a quick way to confirm it's a Google-account-chooser problem rather than GateKeeper.
I can't reach a server, bastion or database
Usually your IP address has changed. Check the address on your dashboard matches where you're actually connecting from — including whether your VPN is on — and update it. See Your details.
Changes don't reach client environments instantly, so allow a few minutes.
gatekeeper: command not found
Either the install didn't finish, or ~/.local/bin isn't on your PATH. Re-run the installer; it
says so explicitly if the directory isn't on your path.
If you've just installed it, open a new terminal — or run exec $SHELL — so the shell picks it up.
gatekeeper connect prints credentials instead of setting them
The shell hook isn't loaded. It's the line the installer adds to your shell config; open a new terminal, or re-run the installer if it isn't there.
Something else
Worth including when you ask:
- what you were doing, and the account name or id;
- the exact error, copied rather than described;
- for the CLI, the output of
gatekeeper -v, which says which deployment you're pointed at.