• Resolved brock40

    (@brock40)


    Hello,

    I’m receiving SSL certificate errors although my SSL certificate is valid and not an issue.

    Here is the debug log:

    2021-10-02 15:39:25.5406 MyCryptoCheckout: Scheduled for October 2, 2021 11:28 am
    2021-10-02 15:40:04.4064 MyCryptoCheckout: Action mycryptocheckout_retrieve_account called!
    2021-10-02 15:40:04.7678 MyCryptoCheckout: WARNING: Unable to retrieve our account details: cURL error 60: SSL certificate problem: certificate has expired
    2021-10-02 15:41:32.4554 MyCryptoCheckout: Action mycryptocheckout_retrieve_account called!
    2021-10-02 15:41:32.7452 MyCryptoCheckout: WARNING: Unable to retrieve our account details: cURL error 60: SSL certificate problem: certificate has expired
    2021-10-02 15:41:57.0869 MyCryptoCheckout: Scheduled for October 2, 2021 10:48 am
    2021-10-02 15:43:12.2006 MyCryptoCheckout: Action mycryptocheckout_retrieve_account called!
    2021-10-02 15:43:12.5293 MyCryptoCheckout: WARNING: Unable to retrieve our account details: cURL error 60: SSL certificate problem: certificate has expired

    Please advise

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter brock40

    (@brock40)

    Payment option doesn’t even show up at checkout cart. It has just disappeared although it is enabled for a payment. Didn’t have any issues with your plugin until yesterday when Bitcoin pumped 10%.

    Thread Starter brock40

    (@brock40)

    Now I’m seeing this:

    Payments using MyCryptoCheckout are currently not available: The account is locked, probably due to a payment not being able to be send to the API server. The account will unlock upon next contact with the API server.

    Thread Starter brock40

    (@brock40)

    Fixed, not sure what the issue was but I removed plugin, cleaned database, rebooted server and reinstalled plugin.

    • This reply was modified 3 years, 1 month ago by brock40.
    Plugin Author edward_plainview

    (@edward_plainview)

    The problem was that your server’s root certificates needed to be updated.

    It’s related to the stupid LetsEncrypt expiration problem that occurred yesterday. Completely out of our hands.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Curl Error SSL certificate’ is closed to new replies.