Hi @saruncloudspring
As you see in the documentation of WP Engine:
520-530 error codes are usually indicate Cloudflare specific errors.
I checked some topics, and as I see some hosts may limit the number of requests over the /wp-login.php page:
and since we are trying to handle over the OAuth flow over the default login page, that could block our requests as well.
I am not really sure if WP Engine also has such limitations, but what you could try is making Nextend Social Login to handle the OAuth flow and the Register flow over other pages.
For that you should use our “Page for register flow” and the “OAuth redirect uri proxy page” settings, that both can be found in our Global Settings > General tab:
For the Page for register flow setting: You should create a new page and place the shortcode into it: [nextend_social_login_register_flow] then select that page for this setting. Extra information before the registration with social login – like Terms and Conditions – would be asked on this page.
For the OAuth redirect uri proxy page setting: You should create another new and completely empty page ( that you won’t use for anything else ) and select it as OAuth redirect uri proxy page. Once it is done, the redirect URL of each configured provider will change, as the OAuth flow will be handled over this new page instead of the /wp-login.php page. So you will need to add the new redirect URLs into each of your Apps. ( Nextend Social Login will also warn you about this with a message, where you can see all the steps, but actually, you can find the redirect URLs in the Getting Started section of the providers, too. – The redirect URLs are the URLs that usually contain this query string: “?loginSocial=” )
Once it is done, make sure the created pages are publicly accessible and don’t forget to exclude the created pages from all kind of caching -including in Cloudflare – since these pages will need to run PHP codes when a user connects with social login.
Best regards,
Laszlo.
