When a user tries to Login with Google, it says “user is not registered in WordPress”
The free version of the plugin allows existing WordPress accounts to login using Google credentials, but it will not create accounts if they do not already exist in WordPress. I presume there is no WordPress account with the email address that corresponds to the Google account attempting to login.
You would need to purchase the premium or enterprise versions of the plugin if you want to sync users from a Google Apps domain to WordPress – i.e. to auto-create WordPress users for anyone with a Google account on your company’s domain, and to ensure that users can no longer login to WordPress after their Google accounts are deactivated.
If you’re already using the Premium or Enterprise version, please ensure the Domain Control tab in Settings -> Google Apps Login is set up correctly, including the ‘Auto-create users on my domain’ checkbox being checked.
I can’t login to WordPress at all any more!
Plugins sometimes conflict with each other, or configuration is incomplete, so you find you can’t access your WordPress site. For that reason, it is important to have a way to remove plugins and perform other low-level resets if needed.
If Login with Google isn’t working, you should still be able to enter your regular WordPress username/password to access the site. (Unless you have selected the option to forbid this for accounts in your Google Apps domain, in the premium or enterprise versions.)
If you have set your site to automatically login with Google, you can override that behavior by going to the following URL on your site:
If you still can’t login, after resetting your WordPress username and password, you should start to disable some plugins that are likely to be causing a problem. Of course you can’t access your Plugins page in WordPress admin, so you will need access to your server’s database or file system.
Here is a useful guide explaining what to do, courtesy of WP Beginner.
If you have Google Apps Login Enterprise installed, and you have accidentally configured the Domain Control tab in a way that means none of your users is an admin user any longer, you may need to change your user back to being an admin via MySQL. See here for instructions.
I install the plugin, and my wp-login.php page is just blank
The only time we’ve seen users experience a blank screen has been because they don’t have CURL enabled on their server.
Read this article describing how you can debug and (hopefully) get an error message to see if that is the problem.
Or, since most often the problem is that CURL needs installing, it may be easier for you to jump straight to finding out whether CURL is installed, and enabling it if not. If that doesn’t solve the problem, you may need to debug as above.
Users sometimes can’t login because Google chooses their personal Gmail account
Here’s what happens whenever you click Login with Google, and it depends how many Google accounts are currently logged-in within the same browser:
- If currently logged in to 0 Google accounts, you will be asked to login to one and the plugin will attempt to login to WordPress against that account
- If currently logged in to exactly 1 Google account, Google will automatically return that account for the WordPress login attempt
- If currently logged in to 2 or more Google accounts, Google will show the user a list of current accounts and allow them to choose which one they want for the WordPress login
Then, if the selected Google account doesn’t match an existing WordPress account and doesn’t come from a Google Apps domain that is authorized in the plugin to have a WordPress account created for it, the user will be told:
Email address needs to be in mycompany.com. email@example.com is not authorized – Sign out of Google to switch accounts
If this is causing confusion, one possibility is to tick the option in Advanced Options of Settings -> Google Apps Login labelled ‘Force user to confirm Google permissions every time’. This adds an extra step to everyone’s login flow asking them to confirm they are happy for Google to connect to the WordPress site (by default, they only see this the very first time). The only reason for this option is to give the user a chance to see (in the top right corner) which Google account has been picked up, and give them the opportunity to change it.
When attempting ‘Login with Google’ I see Invalid JSON in service response
After clicking ‘Login with Google’, and authorizing your Google account, you are redirected back to the WordPress login page and see the error message: Invalid JSON in service response: <followed by a load of strange characters>
This is because Google has recently started compressing some of their responses from their API calls, and older servers are unable to interpret it.
Please ask your web host if they can update to a newer CURL version that has libz/gzip/idn enabled.
Server-side Caching no longer works on my site
Google Apps Login attempts to set its wordpress_google_apps_login cookie on every page of your site. This cookie is only really needed on the wp-login.php page, but many sites have unusual configuration of the login page, so by default the plugin sets the cookie on every page. This can affect some server-side caching systems which turn off caching because this cookie is different for each user.
You can instruct the plugin to only write the cookie on the wp-login.php page in the first place, and this should fix the cache for the rest of your site.
We have instructions providing code that you can add to your Theme’s functions.php file or similar.