• Resolved Matt

    (@rococodigital)


    I am receiving an error upon trying to connect RCP to stripe via settings.

    Here is the log, each error corresponds with attempting to connect stripe:

    2025-9-08 17:13:40 – Starting rcp_mark_abandoned_payments() cron job.
    2025-9-09 10:45:13 – {“errors”:{“http_request_failed”:[“cURL error 60: SSL certificate problem: self signed certificate”]},”error_data”:[]}
    2025-9-09 10:46:30 – {“errors”:{“http_request_failed”:[“cURL error 60: SSL certificate problem: self signed certificate”]},”error_data”:[]}
    2025-9-09 10:52:46 – {“errors”:{“http_request_failed”:[“cURL error 60: SSL certificate problem: self signed certificate”]},”error_data”:[]}
    2025-9-09 11:44:18 – {“errors”:{“http_request_failed”:[“cURL error 60: SSL certificate problem: self signed certificate”]},”error_data”:[]}
    2025-9-09 11:48:37 – {“errors”:{“http_request_failed”:[“cURL error 60: SSL certificate problem: self signed certificate”]},”error_data”:[]}
    2025-9-09 11:53:40 – RCP upgraded from version 3.5.45.1 to 3.5.47.
    2025-9-09 11:54:14 – {“errors”:{“http_request_failed”:[“cURL error 60: SSL certificate problem: self signed certificate”]},”error_data”:[]}

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support ramilbatoy

    (@ramilbatoy)

    Hi @rococodigital

    Apologies for the delayed response.

    The error message:
    cURL error 60: SSL certificate problem: self signed certificate
    indicates that your site’s SSL certificate isn’t being recognized as valid by Stripe’s API. This usually means your web server is using a self-signed or improperly configured SSL certificate, which prevents secure communication between your site and Stripe.

    Could you please confirm the following so we can narrow it down:

    1. Sandbox Mode Test:
      Try connecting your Stripe account in Sandbox (test) mode under Restrict Content → Settings → Payments → Stripe.
      • If the connection works in Sandbox mode, the issue is likely with your live site’s SSL configuration.
      • If it still fails, it may be a local cURL or PHP configuration issue on your hosting server.
    2. SSL Certificate Validation:
      • Visit your website using https:// and check for any SSL warnings in your browser.
      • If the certificate shows as self-signed or incomplete, please contact your hosting provider.

    So far, we haven’t received other reports of this issue, so it appears to be specific to your site’s server configuration rather than the Restrict Content plugin itself.

    Once you’ve verified your SSL setup or tested Sandbox mode, please let me know what you find.

    Best,
    Ramil

    Thread Starter Matt

    (@rococodigital)

    Hi, thanks for the response. I actually solved the issue. Another plugin which was also loading the stripe JS files on RCP pages which was causing a conflict. I’m not sure why it flagged it as an SSL issue but preventing the duplicate loading of Stripe fixed the issue.

    Thanks again

    Plugin Support ramilbatoy

    (@ramilbatoy)

    Hi @rococodigital ,

    That’s great to hear, I’m glad you were able to track down the cause and resolve it. Conflicts like that can sometimes produce misleading logs.

    I’ll go ahead and close this ticket, but if you run into any other issues or questions, feel free to reach out anytime.

    Have a great day!

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

You must be logged in to reply to this topic.