Support » Plugin: WooCommerce Stripe Payment Gateway » Apple Pay Closing

  • Resolved TCR

    (@theconnectedrider)


    Hi there, all was well until I updated to the latest version of the plug-in yesterday. I tried rolling back to 4.06, that didn’t work and then rolled back to 4.0.5 I could finally get credit cards working again. Woocommerce stripe logs were throwing this every few minutes:

    03-02-2018 @ 11:16:45 – ====Start Log====
    Stripe requires SSL.
    ====End Log====

    I also got an email from stripe saying they were unable to reach my endpoint. I looked at the end point is an exact match (I haven’t made any manual changes to it)

    By rolling back the log error stopped, but now my Apple Pay just keeps blanking out. It will show on the screen, you click the icon but then it just closes out the address screen to fast to do anything.

    I literally made NO other changes yesterday other than updating Stripe and things have been fine with it. I contacted Stripe which was seriously something I don’t wish on any human being as they were absolutely useless. Soooo, my KEYS have been checked, they are good, my endpoint is fine, my security certificate is TLS 1.2 let’s encrypt all that is the same as it has been the ONLY thing I did was upgrade to the latest version of your plug-in. But back rolling isn’t working. Amazon Pay and PayPal is working perfect on the same site.
    Please help!

    • This topic was modified 1 year, 8 months ago by TCR.

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author royho

    (@royho)

    This is the error I see on your site http://cld.wthms.co/xtuNpD

    TCR

    (@theconnectedrider)

    The problem is, it is registered and was working fine yesterday. So somehow the update and then rolling back is syncing back up. What do you advise? Delete the domain and try again?

    Plugin Author royho

    (@royho)

    TCR

    (@theconnectedrider)

    Ok so that didn’t work. But what did work was manually placing the verification file in the well-known file under the public_html. It’s working now. That is buggy though that shouldn’t be happening on updates.

    Plugin Author royho

    (@royho)

    That is not something the plugin does. It must be something else on your server that is removing that file.

    TCR

    (@theconnectedrider)

    The file was still there, I literally deleted and replaced the exact same file. I have complete access to my server with the only log-in no one tinkered with it. I will firmly state there is a resync issue between your plug-in and stripe. There are enough threads on google with this same issue to know it’s not unique to me. Although I figured it out on my own someone actually wrote an article on this exact issue with plenty of comments of people thanking him for writing it.It’s a known issue and the common issue is stripe wants to blame woo, you want to blame my server. But here is the fast facts the ONLY change I made was upgrading to the latest version of your plug-in. THE ONLY CHANGE. That threw it off. It’s a bug I would look in to it instead of pointing fingers where they don’t belong.

    • This reply was modified 1 year, 8 months ago by TCR.
    Plugin Author royho

    (@royho)

    Can you please show me these Google threads you mentioned? I would like to take a read. What on our plugin is causing this?

    TCR

    (@theconnectedrider)

    Isn’t that your job to troubleshoot?

    Plugin Author royho

    (@royho)

    There are enough threads on google with this same issue to know it’s not unique to me.

    Sure I will troubleshoot. Please provide me the threads you mentioned and I will have a read.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Apple Pay Closing’ is closed to new replies.