FB login – Customers end up WP admin login screen

Hi, when trying to login with FB you end up WP admin area. https://anylistingseo.com/wp-login.php?nsl-notice=1 Google, X working just fine, only FB has this issue. You can test it here: https://anylistingseo.com/my-account/ Hi @negotiatoruk I get the same problem for Google and X too. I believe the problem is that registration is disabled on your website. By default Nextend Social Login will inherit the membership setting from WordPress (WordPress>Settings>General>Membership – Membership Anyone can register). If you would like to enable the registration with Nextend Social Login, please navigate to Nextend Social Login>Global Settings>General tab>Membership and set it to Enabled: https://nextendweb.com/nextend-social-login-docs/global-settings/ In this way users with social providers will be able to login/register even when the default WordPress membership is disabled. Why it might have worked for you for Google and X is because you had a WordPress account that either had the social media account linked to it, or there was an email match, so we logged you in, instead of trying to register a new account. Hi, Anyone can register is enabled both WP + Plugin. We are getting same result. https://snipboard.io/Ef36Jj.jpg @negotiatoruk Now I am able to sign up no problem (you can probably see a few recently registered accounts from my tests). Did you manage to figure it out in the meantime? If the issue is still present, then it is most likely from a 3rd party plugin or custom code that runs on your wp-login page, and intercepts our flow, as by default we use the default wp-login page. You could do a conflict test by making a backup of your website, then disable your plugins one by one until the error is gone to find out what does it exactly. Alternatively, you can try and force Nextend Social Login to handle its flows over other pages. For this you need to use our “OAuth redirect uri proxy page” and “Page for register flow” settings. Both of these can be found in our Global settings > General tab: https://social-login.nextendweb.com/documentation/settings/general-settings/ and you should configure them in the following way: For the Page for register flow: You should create a new page and add 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, Username, Password, Email – would be asked on this page. ( Make sure you don’t use this page for anything else! ) For the OAuth redirect uri proxy page: You should create another new and completely empty page ( that you won’t use for anything else either ) 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 configured Apps again. ( 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=” ) I think we should find the couse of the issue first. As it worked for several years Hi @negotiatoruk ! Plugins and themes are often updating their codes, creating new features, and this can cause that after some years they are messing up already working other plugins. So if you would like to find the cause of the issue, we suggest to: Create a backup of your website, to ensure the following process won’t do any irreversible issues. Turn off your plugins one-by-one, and do a test after each deactivation. Most likely a plugin will cause this problem, so you will find the cause this way and contact its developers to ask them about it. If you would still see an issue, change to a default Twenty[any] theme, to confirm that the theme causes the problem. Then the theme’s developers could be contacted and asked what changed in their codes and how to avoid this unwanted result. Tested evrything, no results. Maybe it is caching issue. @robertnextendweb After repeated tests, the issue is in your plugin. Google and X sign-ins work, but Facebook does not. We tested on a clean install and found no theme or plugin conflicts. Clicking “Continue with Facebook” often opens the user’s personal Facebook page in the popup instead of the OAuth dialog, and the flow never returns to our site. Please investigate and advise a fix. Hi @negotiatoruk I am Laszlo, I am one of the developers of Nextend Social Login. I also checked the login with Facebook multiple times and it worked fine for me, too. So I read back your conversation history with my colleagues and in your screenshot: https://snipboard.io/Ef36Jj.jpg I see an error message: ERROR: Invalid Username Or Password. Attempts remaining: 0 that doesn’t come from us nor WordPress. So you definitely have a third party plugin that creates a conflict. Based on the error message, it is a probably security plugin that counts failed login attempts, and it has already blocked you because you had multiple failed login attempts. So future attempts will be blocked as well! With the above mentioned plugin/theme conflict test you could find that plugin. I am not really sure if this security plugin blocks the connection over only the /wp-login.php page or not, but I can see that you didn’t make the configurations that Robert suggested. I can tell this by inspecting the URL of our social buttons, they still point to your /wp-login.php page, although if you did the suggested configurations they should already point to the new page that you selected as “OAuth redirect uri proxy page”. So first of all please configure the “OAuth redirect uri proxy page” and “Page for register flow” settings as per Robert’s suggestions. If you still see the problem even after that: Nextend Social Login has a feature called “Support login restrictions”, that allows third parties to prevent the login with social login. E.g. this can be useful when you want to prevent the login with social login as well for blocked users ( just like in your case ), or if you want to prevent the login with social login until the account is not verified, you can read more about this feature here: https://social-login.nextendweb.com/documentation/getting-started/troubleshooting/login-restrictions/ So next, you should check if this feature is enabled or not. If it is, then try disabling it. You can find this setting at Nextend Social Login > Global Settings > General tab: https://social-login.nextendweb.com/documentation/settings/general-settings/#support-login-restriction If you made both of the configurations that I suggested above, but the problem still occurs: then since: the login with Facebook worked fine for us and you told the other providers worked fine for you, too I could also imagine that you are trying to connect with a Facebook account that’s email address might be the same as one of your WordPress admin accounts, and the security plugin might force some s ort of verification for admin users, so they will block the social login to that account. To figure out if this is the case or not, you should: try the login with another Facebook account ( make sure there is no admin account on your site with its email address ) and just in case the security plugin blocked by IP address, I would suggest you to try the login with another IP, e.g. using your phone’s cellular data ( make sure you don’t use Wi-Fi, as that way your IP could be the same as the blocked one ) As for your tests on the site with the clean install: When you press the social button, Nextend Social Login redirects the user to the OAuth authorization endpoint of the provider. It is entirely up to the provider how they handle the OAuth request, but in case of Facebook they should: either throw an error message if something is wrong with your App configuration or with the authorization request or display the OAuth consent screen but it should definitely not display your profile page. So I think that is most likely a temporary problem on the end of Facebook. But if you still see the problem, then in order to see what is happening please get in touch with us directly over the ticket system: https://social-login.nextendweb.com/support/ and send us a screen record ( video ) of the requests. You can check the requests like this: open a new tab open the browser console ( e.g. in Google Chrome you can do this by pressing right click on the page and choose “Inspect” ) choose the “Network” tab: https://developer.chrome.com/docs/devtools/network increase the width of DevTools, and increase the width of the “Name” column ( so I will be able to see the requests ) turn on the “Preserve log” and “Disable cache” options filter for the “Doc” ( Document requests ) copy the URL of your Facebook button and paste it to the Address bar and open the link ( this will redirect you to the OAuth endpoint, or in your case to the user profile page. ) Here I uploaded a screenshot showing where you can find these settings: https://www.dropbox.com/scl/fi/c70ejlpe2qfp5onw7w05t/devtools.jpg?rlkey=dlvzoruh76xbg307cqa0xzwyz&e=1&st=bbdjxong&dl=0 and you can record your screen with a free screen recording software like Bandicam or OBS . Important note: make sure you send the screen record to our ticket system as this is a public forum! ( If the file is too big, feel free to upload it to a file sharing site like Dropbox and send us the link. ) Best regards, Laszlo. @laszloszalvak Hi, thank you for your reply. We’re aware of the potential for security plugin conflicts. As suggested, we disabled all plugins, but unfortunately, that did not resolve the issue. The “Support login restrictions” option is currently disabled. As for the “OAuth redirect URI proxy page,” we’re not looking to set it up at this time, especially since everything was working fine before—and still works correctly for Google and X logins. If there were any plugin conflicts or general issues, we would expect the same behavior across all platforms. So the question remains: why is this issue only occurring with Facebook? Looking forward to your insights. Hi @negotiatoruk As for the conflict: If you still see an error with the Facebook login even after you disabled the security plugin, then could you tell me the error message? Since as I mentioned above, the error message that you received earlier is not coming from us, nor WordPress. So if you disable the plugin that triggered that error ( presumably the security plugin ), then you should: no longer receive an error or if you do, then you should receive another completely different error message ( if you still have configuration problems ) If you receive the same error message, that means the plugin that triggers the error is still enabled on the site, so as we suggested earlier, please do a completely plugin conflict test on the site where you receive the error message. So basically you should: create a backup of your site disable all plugins except Nextend Social Login change your theme to a WordPress default one ( e.g. Twenty Twenty-One ) try the login with Facebook if it works fine, start enabling the plugins one by one and check the login with Facebook again repeat step 5 until the problem starts occuring Why the problem occurs only with Facebook: As I mentioned above, your site / your plugins might handle different user roles in different ways. So e.g. if you tried to connect with a Facebook account that shares the email address of one of your admin accounts, your third party plugins could block the login to that account using social login. This is why I suggested you to try the login with another Facebook account ( with an email address that is not registered on your site ), since when we tested the Facebook login on your site ( with differe...