Troubleshoot sign-in on a community site

Selecting Sign in or Join on a community site sends you to lockers.social, where you sign in with your password or with Google, and returns you to the page you started on. While it returns you, the page reads Signing you in.

Two things have to work: the trip out and the trip back. The message you see tells you which half stopped, and the fix is different for each. The full walkthrough is in Sign in to a community.

Both of these appear after the return, on the community's own address. Each one shows a Start again button that begins the sign-in again from the community you were entering.

These two appear before you get back, on lockers.social. Both show Return to the community and start again. and a Lockers home link.

Continue with Google appears on lockers.social only when Google sign-in is available. If it is missing, sign in with your email and password.

If the form says We couldn't start Google sign-in. Try again., select Continue with Google once more. If the message comes back, sign in with your email and password, or check that your browser is not blocking the Google window or cookies for lockers.social.

Google signs you in to an existing Lockers account only when that account has already confirmed its email address. If you made an account with the same email but never confirmed it, sign in with its password, or reset the password, instead of using Google. A closed account cannot sign in with Google either.

After a connection problem, a community page can show you as signed out while your sign-in is still good. Lockers keeps retrying in the background for about a minute and reloads the page once the connection is back, so the first thing worth trying is nothing at all. Give it that minute. If the page still shows you signed out, select Sign in and let the normal trip run.

Sign-in needs cookies allowed for lockers.social and for the community's own address. Browser settings and privacy extensions block cookies site by site, so one community can fail while the rest of the web behaves normally. Allow both addresses in whatever is doing the blocking, then start the sign-in from the community site again.

If you are not sure which setting is at fault, open the same community in a different browser. If the sign-in completes there, the block is in the first browser's settings or in one of its extensions.