Auth0 Home Blog Docs

WordPress Plugin -unable to login - Could not reach the server

wordpress
wordpress-login-with
failed-login

#1

I am looking to integrate this service with a Backbone WordPress installation with wordpress core files installed in stage.mysite.com/wp/ directory.

I am using the Login by Auth0 plugin and went through the wizard process. When it got to the login and migrate the administrator user process and later the plugins login page I receive an error.

WE COULD NOT REACH THE SERVER. PLEASE CHECK YOUR CONNECTION AND TRY AGAIN.

I have reviewed the settings and they appear correct…

Allowed callback URLs
http://stage.mysite.com/wp/index.php?auth0=1, http://stage.mysite.com/wp/wp-login.php

Allowed Origin URLs
http://stage.mysite.com/wp/wp-login.php, http://stage.mysite.com/wp/wp-admin/admin.php?page=wpa0-setup&step=2&profile=social


#2

This is being handled through another support channel, but for the benefit of other wanted to include a summary here. So the underlying cause in this specific case was that the recent deprecation notice for Lock 10 and below when used in embedded login scenarios meant that new tenants don’t even have access to those API’s. In addition, the Wordpress plugin current version is still making use of Lock 10 so the issue will surface in new tenants due to unavailability of legacy API’s; there’s already ongoing work to update the Wordpress plugin to Lock 11 so this will be addressed in the next version of the plugin.


#3

@jmangelo

What other support channel would that be?

The WordPress plugin is still up for download with no mention of the breaking changes anywhere whatsoever.

  • not on the plugin page
  • not on github
  • not on your own documentation

Just spent half a day trying to figure out a the issue only to find out it is something to do at your end. At least have the diligence to put a note in the plugin description to inform new users of the upcoming changes.

I would ask about what the timeline is for the WordPress update but not bothered as will look for an alternate solution since you are obviously an unreliable and unprofessional provider to work with.


#4

@jmangelo what support channel would that be? The plugin is still up for download with no mention of breaking changes:

  • not on the plugin page
  • not on github
  • not on your own documentation

Spent half a day trying to figure out the issue only to find out it is something on your end. At least have the diligence to put a note in the plugin description to inform new users of the upcoming changes.

I would ask about the timeline is for the update but not bothered as will look for an alternate solution since you are obviously an unreliable and unprofessional provider to work with.


#5

For the support channel available see: https://auth0.com/docs/support#support-channels

I would agree that this was not documented as best as we wanted; the reality was that there were (technically) no breaking changes at the plugin. The plugin won’t work only on new tenants that don’t have available certain deprecated functionality so given the breaking changes happened elsewhere we missed this and failed to properly document it in the plugin while there was no update.


#6

Hi @jared : here’s the official 3.5.0 release


#7