• Home
  • WordPress Themes
    • eCommerce
    • Corporate
    • Multipurpose
    • Blog
  • Support
    • WoodMart support
    • Basel support
    • Space support
    • Feature requests
  • Documentation
    • WoodMart
    • Basel
    • Hitek, Luman, Antares
  • Demo
    • WoodMart
    • Basel
    • Hitek
Login / Register
Checkout
Checkout
Menu

Home / Forums / WoodMart support forum / Google and Facebook Login Error after Woodmart update

Home › Forums › WoodMart support forum › Google and Facebook Login Error after Woodmart update

Google and Facebook Login Error after Woodmart update

  • This topic has 16 replies, 5 voices, and was last updated 2 years, 1 month ago by grafiman.
Viewing 17 posts - 1 through 17 (of 17 total)
  • Author
    Posts
  • April 7, 2022 at 5:12 am #366750

    robertpurnomo
    Participant

    Google and Facebook login was working until I update Woodmart. There are 3 type of errors:

    1) PC Chrome Incognito Mode, when click login with FB, we got “Error Accessing App We’re sorry, but the application you’re trying to use doesn’t exist or has been disabled.”

    2) On Android Chrome Incognito Mode, FB login result in Error 502 Bad Gateway

    3) On Android Chrome Incognito Mode, Google login result in Error 502 Bad Gateway

    Attached are screenshot for your reference. We use Bitnami NGINX WordPress on AWS EC2.

    Please let us know if you need admin access login & password to our website, AWS, Google Dev and Facebook Dev.

    Thank you for yoru kind attention.

    Sincerely,
    Robert

    Attachments:
    You must be logged in to view attached files.
    April 7, 2022 at 5:53 am #366754

    robertpurnomo
    Participant

    We have same social login error in the past and we notice the issue is with / and ?
    https://healthfullcare.com/my-account?opauth=XXXXXXXXXX
    https://healthfullcare.com/my-account/?opauth=XXXXXXXXXX

    So on Authorized redirect URIs and valide Valid OAuth Redirect URIs, we add as many possibility as possible and it was working. But now after updates, they don’t work again.

    https://healthfullcare.com/my-account/google/oauth2callback
    https://healthfullcare.com/zh-hant/my-account/google/oauth2callback
    https://healthfullcare.com/my-account?google/oauth2callback
    https://healthfullcare.com/zh-hant/my-account?google/oauth2callback
    https://healthfullcare.com/my-account/?google/oauth2callback
    https://healthfullcare.com/zh-hant/my-account/?google/oauth2callback

    April 7, 2022 at 6:17 am #366770

    Artem Temos
    Keymaster

    Hello,

    We just tested the Google login on your website and were able to log in without errors. Here is a screenshot https://gyazo.com/49be0bcedeede451eb13fac85deb9b8e
    Could you please clarify how to reproduce the problem?

    Kind Regards

    April 7, 2022 at 7:21 am #366783

    robertpurnomo
    Participant

    Hi Artem Temos,

    Thank you for your reply. Attached are screenshot of 3 errors
    1) Fabecook Error Accessing App
    2) Facebook login Error 502 / Bad Gateway
    3) Google login Error 502 / Bad Gateway

    Below are URL of 3 errors

    Facebook Social Login
    Error Accessing App
    https://www.facebook.com/login.php?skip_api_login=1&api_key=667925607390712&kid_directed_site=0&app_id=667925607390712&signed_next=1&next=https%3A%2F%2Fwww.facebook.com%2Fv2.8%2Fdialog%2Foauth%3Fclient_id%3D667925607390712%26redirect_uri%3Dhttps%253A%252F%252Fhealthfullcare.com%252Fmy-account%252Ffacebook%252Fint_callback%26scope%3Demail%26ret%3Dlogin%26fbapp_pres%3D0%26logger_id%3Db70864be-972d-40df-8735-5701c493a082%26tp%3Dunspecified&cancel_url=https%3A%2F%2Fhealthfullcare.com%2Fmy-account%2Ffacebook%2Fint_callback%3Ferror%3Daccess_denied%26error_code%3D200%26error_description%3DPermissions%2Berror%26error_reason%3Duser_denied%23_%3D_&display=page&locale=en_GB&pl_dbl=0

    Facebook login Error 502 / Bad Gateway
    https://healthfullcare.com/my-account?opauth=YTozOntzOjQ6ImF1dGgiO2E6NTp7czo4OiJwcm92aWRlciI7czo4OiJGYWNlYm9vayI7czozOiJ1aWQiO3M6MTY6IjMyNDA4OTI4NzU5NzAzNTkiO3M6NDoiaW5mbyI7YTo0OntzOjQ6Im5hbWUiO3M6MTQ6IlJvYmVydCBQdXJub21vIjtzOjU6ImltYWdlIjtzOjY3OiJodHRwczovL2dyYXBoLmZhY2Vib29rLmNvbS92Mi44LzMyNDA4OTI4NzU5NzAzNTkvcGljdHVyZT90eXBlPWxhcmdlIjtzOjU6ImVtYWlsIjtzOjIzOiJyb2JlcnRwdXJub21vQGdtYWlsLmNvbSI7czo4OiJuaWNrbmFtZSI7czoxNDoiUm9iZXJ0IFB1cm5vbW8iO31zOjExOiJjcmVkZW50aWFscyI7YToyOntzOjU6InRva2VuIjtzOjI0MToiRUFBSmZlWXlRbmZnQkFDNXZoVjlSeldNWWdZYUY0d2JUdVBhTEgwS2lZdWZqdXpHS1QwbVZZQVJvR1kwaVd2b24yRkNDeW9YNHFpQjlxMGR5WkJCUERzWkI1YlROYjVJMktjRkJqVGo3RHFkS1FSUTZXSkVGdlFEYjYwanV2SDhJM1BSMXQyUUFOQUNLaDU1Vmd4MDc5bnhCQ212OFFPSGRJVlBCb3hRWkF4YlFNUlpDMkp6Z0RDRlpCM3lpd01UNTVISmVwUlpDQWhGazNISURtV0lzdVcyWHNTVWljbnFXQ2pDeWZTRkQ3ZWlnWkRaRCI7czo3OiJleHBpcmVzIjtzOjI1OiIyMDIyLTA2LTA2VDA0OjI5OjE3KzAwOjAwIjt9czozOiJyYXciO2E6Mzp7czoyOiJpZCI7czoxNjoiMzI0MDg5Mjg3NTk3MDM1OSI7czo0OiJuYW1lIjtzOjE0OiJSb2JlcnQgUHVybm9tbyI7czo1OiJlbWFpbCI7czoyMzoicm9iZXJ0cHVybm9tb0BnbWFpbC5jb20iO319czo5OiJ0aW1lc3RhbXAiO3M6MjU6IjIwMjItMDQtMDdUMDc6MTE6MTkrMDA6MDAiO3M6OToic2lnbmF0dXJlIjtzOjMxOiI2bjkydWw4bGw3b2tnODAwdzBvOGNnOHNvYzgwazBzIjt9#_=_

    Google login Error 502 / Bad Gateway
    https://healthfullcare.com/my-account?opauth=YTozOntzOjQ6ImF1dGgiO2E6NTp7czozOiJ1aWQiO3M6MjE6IjExMTQwNTI3MjA4MzMxNTYwMzE1MCI7czo0OiJpbmZvIjthOjU6e3M6NDoibmFtZSI7czoxNDoiUm9iZXJ0IFB1cm5vbW8iO3M6NToiZW1haWwiO3M6MjM6InJvYmVydHB1cm5vbW9AZ21haWwuY29tIjtzOjEwOiJmaXJzdF9uYW1lIjtzOjY6IlJvYmVydCI7czo5OiJsYXN0X25hbWUiO3M6NzoiUHVybm9tbyI7czo1OiJpbWFnZSI7czo5MDoiaHR0cHM6Ly9saDMuZ29vZ2xldXNlcmNvbnRlbnQuY29tL2EtL0FPaDE0R2gxbWdjd1BUcWtsWGRpcURzbHpUbjZOZ2ZUQm9kWm9OZF9uVTA0VXFBPXM5Ni1jIjt9czoxMToiY3JlZGVudGlhbHMiO2E6Mjp7czo1OiJ0b2tlbiI7czoxNjY6InlhMjkuQTBBUnJkYU04Rkk0OVNjaUhkQjBZR0IzMEZCUUNXSVlqbUVOOXJ0Z2E3dXZzRnpYUTVLS2JMMkxabTFLblExanJpa3NLNVQ2ZjJ4eXVqcmc1QUM4dmFWbjdlVk1CUFhySHhGRmhRTDZuSGNjam5JdnAtZnl3aWU3aTM4MTItUVRaZFgzNWRESHNXa2wzSTJyN1FvNTloR0tZa3VkVnpMekkiO3M6NzoiZXhwaXJlcyI7czoyNToiMjAyMi0wNC0wN1QwODoxMjo1NCswMDowMCI7fXM6MzoicmF3IjthOjg6e3M6MjoiaWQiO3M6MjE6IjExMTQwNTI3MjA4MzMxNTYwMzE1MCI7czo1OiJlbWFpbCI7czoyMzoicm9iZXJ0cHVybm9tb0BnbWFpbC5jb20iO3M6MTQ6InZlcmlmaWVkX2VtYWlsIjtpOjE7czo0OiJuYW1lIjtzOjE0OiJSb2JlcnQgUHVybm9tbyI7czoxMDoiZ2l2ZW5fbmFtZSI7czo2OiJSb2JlcnQiO3M6MTE6ImZhbWlseV9uYW1lIjtzOjc6IlB1cm5vbW8iO3M6NzoicGljdHVyZSI7czo5MDoiaHR0cHM6Ly9saDMuZ29vZ2xldXNlcmNvbnRlbnQuY29tL2EtL0FPaDE0R2gxbWdjd1BUcWtsWGRpcURzbHpUbjZOZ2ZUQm9kWm9OZF9uVTA0VXFBPXM5Ni1jIjtzOjY6ImxvY2FsZSI7czoyOiJlbiI7fXM6ODoicHJvdmlkZXIiO3M6NjoiR29vZ2xlIjt9czo5OiJ0aW1lc3RhbXAiO3M6MjU6IjIwMjItMDQtMDdUMDc6MTI6NTUrMDA6MDAiO3M6OToic2lnbmF0dXJlIjtzOjMxOiJxbXFid290b3pqNGtrOGc4bzg4NHN3MGc4ODRzczB3Ijt9

    Thank you for your kind attention.

    Sincerely,
    Robert

    Attachments:
    You must be logged in to view attached files.
    April 7, 2022 at 7:38 am #366787

    robertpurnomo
    Participant

    Hi Artem Temos,

    Here is screenshot of Google and Facebook Login 502 Error.

    FYI, we have same social login 502 error issue before and we hire Fiverr freelancer. He said the previous errors are caused by below:

    1) https://healthfullcare.com/my-account/?opauth=
    the problem is with slash ( / )

    2) no slash = error 502

    3) with slash = OK

    4) It’s php code. i tried already from nginx block but failed. and it’s better to check the code from the theme

    5) tell them to ask theme developer

    6) https://healthfullcare.com/my-account?opauth=XXXXXXXXXX

    https://healthfullcare.com/my-account/?opauth=XXXXXXXXXX

    7) make the redirection like this

    8) a single slash

    Yours sincerely,
    Robert

    Attachments:
    You must be logged in to view attached files.
    April 7, 2022 at 8:42 am #366800

    robertpurnomo
    Participant

    Hi Artem Temos,

    We have fixed “Error Accessing App” issue in Facebook Social Login. We just delete the old Facebook login apps and create a new one on Meta for Developers.

    for Valid OAuth Redirect URIs, we add below but still getting 502 error

    https://healthfullcare.com/my-account/

    https://healthfullcare.com/zh-hant/my-account/facebook/int_callback

    https://healthfullcare.com/my-account/?facebook/int_callback

    https://healthfullcare.com/zh-hant/my-account/?facebook/int_callback

    https://healthfullcare.com/my-account?facebook/int_callback

    https://healthfullcare.com/zh-hant/my-account?facebook/int_callback

    Hope you can help fixed 502 error issue on Facebook and Google login.

    Yours sincerely,
    Robert

    Attachments:
    You must be logged in to view attached files.
    April 7, 2022 at 9:49 am #366812

    robertpurnomo
    Participant

    Hi Xtemos support team,

    We really need this social login issue fixed ASAP. We don’t mind to pay a bit fee for fixing this issue. If there is fee to fix this social login issue, please just let us know how much and how to pay. We’re waiting for your reply. Thank you very much.

    Note: the social login error is Error 502 Bad Gateway (Cloudflare). If we stop Cloudflare CDN will this solve the social login error 502 bad gateway issue?

    Yours sincerely,
    Robert

    April 7, 2022 at 11:04 am #366827

    Artem Temos
    Keymaster

    Hello,

    The Facebook error seems to be different and it is thrown by Facebook itself. It says that something is wrong with your APP, not with the website.
    As for the 502 error, it seems to be generated by your server. Maybe it blocks the request when you are redirected from the social platform back to your website.

    Kind Regards

    April 8, 2022 at 2:27 am #366918

    robertpurnomo
    Participant

    Hi Artem Temos,

    Thanks for your reply. Both Facebook and Google Social Login results in Error 502 Bad Gateway.

    You mentioned “502 error, it seems to be generated by your server. Maybe it blocks the request when you are redirected from the social platform back to your website.”

    Can you show me how to solve above issue? and also if you have other easier solutions? Sorry and thanks for your kind help. I appreciate your help.

    Yours sincerely,
    Robert

    April 8, 2022 at 6:04 am #366931

    Artem Temos
    Keymaster

    502 is a generic error generated by the server. We don’t know exactly how to solve it. You need to check server logs or consult with your hosting provider on this matter.

    Kind Regards

    July 12, 2022 at 9:00 pm #390567

    burak
    Participant

    I have same problem with google. Did you solve the problem with google ?

    July 12, 2022 at 9:01 pm #390568

    burak
    Participant

    I have same problem with google. Did you solve the problem with google ?

    edit: https://healthfullcare.com/my-account/?opauth=xxxxx

    it’s ok now. how did you fix this ?

    July 13, 2022 at 5:16 am #390612

    robertpurnomo
    Participant

    Yes, I finally solve the issue. Cloudflare CDN and caching was causing Woodmart Google and Facebook login to not work.

    After I disable Cloudflare CDN and caching, no more 502 error on Woodmart Google and Facebook login

    November 21, 2022 at 4:12 am #422369

    bhare1985
    Participant

    Hello, I just came across the same issue where Google Login doesnt work.

    https://website.com/account?opauth=YTozOntzOjQ6Im fails
    but
    https://website.com/account/?opauth=YTozOntzOjQ6Im works

    What was the solution ?

    November 21, 2022 at 5:40 am #422375

    bhare1985
    Participant

    It seems the callback_url being given to the OAuth classes uses “account” when it should be “account/”, rather than modify woodmart core until this bug of theirs is fixed I was able to add this to my nginx rules and it works without having to turn off cloudflare:

    rewrite ^/account$ https://$host$uri/ permanent;

    November 21, 2022 at 7:30 am #422392

    bhare1985
    Participant

    Welp it’s breaking again despite it using an ending slash. What is more weird is that it only breaks for certain logins, so its intermittent and makes sense why woodmart support wasn’t able to reproduce it. It seems the common issue is cloudflare but it could be caching in general. What’s confusing is that no errors show up in the php log

    March 22, 2023 at 9:56 pm #453478

    grafiman
    Participant

    SOLUTION
    The source of the problem is on NGINX: upstream sent too big header while reading response header from upstream

    Solution is: Add this additional nginx directives:

    fastcgi_buffers         16  16k;
    fastcgi_buffer_size         32k;
    proxy_buffer_size          128k;
    proxy_buffers            4 256k;
    proxy_busy_buffers_size    256k;

    (Tested on plesk panel)

  • Author
    Posts

Tagged: Facebook login, google login, Social login

Viewing 17 posts - 1 through 17 (of 17 total)
  • You must be logged in to create new topics. Login / Register

Your request can't be resolved for a long time? Contact our general support manager.

Contact form
WoodMart Facebook Group
Create your WordPress website.
  • Resources
    • Video tutorials
    • Blog
    • Contact us
    • Refund Policy
    • Terms of Service
  • Social links
    • Facebook
    • Twitter
    • Instagram
    • YouTube
@ XTemos studio. 2025 WordPress development from 2015.

Privacy Policy

  • Home
  • WordPress Themes
    • eCommerce
    • Corporate
    • Multipurpose
    • Blog
  • Support
    • WoodMart support
    • Basel support
    • Space support
    • Feature requests
  • Documentation
    • WoodMart
    • Basel
    • Hitek, Luman, Antares
  • Demo
    • WoodMart
    • Basel
    • Hitek
  • Login / Register
Sign in
Close

Lost your password?

No account yet?

Create an Account