curl error 35 on OAuth Flow

  • Resolved crystalhq

    (@crystalhq)


    2 years, 4 months ago

    Hello,

    I’m attempting to create a plugin for WooCommerce to sync data between my application and WooCommerce. I had setup the plugin to follow the OAuth flow documented on the WooCommerce documentation for retrieving a Rest API key. This all functioned locally using a wp-scripts based local WordPress environment with a ngrok proxy for the HTTPS requirement.

    After deploying the server to AWS and testing again (on both a locally ran wp-scripts based WordPress environment and a cloud based one), I’ve received the following error at the last step of the OAuth flow (after hitting “Approve” to the scopes):

    
Error: cURL error 35: error:1408F10B:SSL routines:ssl3_get_record:wrong version number.

    The site is reachable via PostMan requests on both HTTP and HTTPS endpoints. I can also curl the endpoint from my local machine and receive a response without issue.

    I tried deploying the server to another hosting provider (Google Cloud) to see if that was causing the issue and received the same error there. I found something suggesting that a TLSv1.3 was necessary and had setup the AWS configuration to have a Network Load Balancer that terminated TLS connections for v1.3 and still received the same error.

Viewing 1 replies (of 1 total)

  • Hi @crystalhq

    Thanks for reaching out!

    Firstly, I apologized for the delayed response.

    The cURL error 35 can appear when the cURL function cannot connect to your website using SSL. Curl often uses a different set of certificates, shipped with PHP. There are several things that can cause this problem, in most cases updating both cURL and PHP to a newer version will resolve this issue.

    I did some research and found this article could be a good starting point: How to fix localhost error – cURL error 35 (SSL connect error)

    Meanwhile, these forums are meant for general support with the core functionality of WooCommerce itself. What you want to achieve is a bit complex and would require customization to do it. Since custom coding is outside our scope of support, I am leaving this thread open for a bit to see if anyone can chime in to help you out.

    For questions related to development and custom coding, your best bet is to ask on any of these channels for support. We’re lucky to have a great community of open-source developers for WooCommerce, and many of our developers hang out there, too.

    – WooCommerce Developer Resources Portal
    – WooCommerce Advanced Facebook group
    – WooCommerce Community Forum
    – WooCommerce Developer Slack Channel.
    – Hire a WooCommerce Expert

    Hope this helps!

Viewing 1 replies (of 1 total)
  • The topic ‘curl error 35 on OAuth Flow’ is closed to new replies.

Tags