digits + nextend + cloudfront issue

  • Resolved futureyoon

    (@futureyoon)


    4 years, 1 month ago

    Hi

    I am using digits + nextend social login (free version) and have recently moved the site to cloudfront environment.
    Realize that digits is not reacting to the google social login at all on cloudfront.

    When I point back to my IP directly, it’s working fine.
    Here I attached a quick video of the symptom. I am not sure if this is issue from digits or cloudfront or nextend…

    So I am contacting each.. Do you mind sharing some insights on this issue? Have you seen this kind of issue?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Ramona

    (@nextend_ramona)

    4 years, 1 month ago

    Hi @futureyoon

    Let’s try to narrow down which parties actually conflict.

    1. Turn off both Cloudflare and Digits and see if you can log in.
    2. Turn on Cloudflare but keep Digits turned off and see if you can log in.
    3. Turn off Cloudflare and turn on Digits and see if you can log in.

    Test #1 should work fine (unless something else is conflicting, and the other two plugins are actually unrelated). The other two tests should tell whether a Cloudflare setting or the Digits plugin is preventing the registration to go through.

    Let me know which test was unsuccessful and we can try to find a solution from there.

    Plugin Support Laszlo

    (@laszloszalvak)

    4 years, 1 month ago

    Hi @futureyoon

    Have you managed to fix the problem?

    Since I checked the site that appeared in your video, and the login with Google worked fine for me now.

    Thread Starter futureyoon

    (@futureyoon)

    4 years, 1 month ago

    Hahaha thank you for the check!
    Yes I managed to fix it with some workaround by accepting all requests coming in.
    Initially I controled the orginin request cookies as below (which are quite common)

    comment_author_*
    comment_author_email_*
    wordpress_test_cookie
    comment_author_url_*
    wordpress_*
    wordpress_logged_in_*
    PHPSESSID
    wordpress_sec_*
    wp-settings-*

    but i removed them and accept all cookies in origin request temporariliy.
    but AWS engineer and I wish to know more from you what cookie or string that you use to pass the value? so that I can include the value into the list of origin request.(insteand of accepting all)

    Can you share little more info about this?

    Thank you

    • This reply was modified 4 years, 1 month ago by futureyoon.
    Plugin Support Laszlo

    (@laszloszalvak)

    4 years, 1 month ago

    Hi @futureyoon

    For the authentication we also use a cookie, so in this case the problem was probably caused by that we couldn’t set it because of the controlled environment.

    The name of our cookie is

    • SESSnsl

    so you could try adding it to your list as well, and hopefully that will fix the problem.

    Tip: I would also suggest keeping the WordPress default login cookies as well:

    • wordpress_logged_in_*
    • wordpress_sec_*

    Since after the authentication with social login, we will make the users login the same way as WordPress does.

    Thread Starter futureyoon

    (@futureyoon)

    4 years, 1 month ago

    Yes it works fine by adding SESSnsl. 🙂
    Thank you for the info! Case resolved. Maybe you can document this out somewhere for other users like me.

    LULU

    (@a2000102000)

    3 years, 11 months ago

    @futureyoon

    Hi, after watching your demonstration video, I think the plug-in connection is so beautiful!

    I’m not a developer and don’t know programming languages at all. Is it possible to do the plug-in series connection of digits + nextend?
    If you want, can you teach me how to do it?
    I would be very grateful 😭🙏

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘digits + nextend + cloudfront issue’ is closed to new replies.