• Resolved mfdale

    (@mfdale)


    Hi there and Merry Christmas ??

    I’ve downloaded and installed the WordPress plug-in version of Speed Kit to my https://www.adventure-sports.co.uk website.

    It downloads fine via the WordPress control panel. However, when I click “activate” I get the following error:

    Plugin could not be activated because it triggered a fatal error.
    RuntimeException thrown
    Cannot send request because of Baqend\SDK\Exception\RequestException: Error sending GET /speed-kit/1.X.X/sw.js: cURL error 35: SSL connect error

    My website is hosted on easyspace, using Plesk control panel, WordPress 5.2 and php version 5.6.49

    Thanks!
    Matt

    • This topic was modified 6 years, 2 months ago by mfdale.

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author baqend

    (@baqend)

    Hello, Matt,

    I hope you also had a merry Christmas and wish you a happy new year! I apologise for not answering until after the holidays.

    The SSL error you see is triggered by your server, as we are establishing an encrypted HTTPS connection from your to our server to load the latest component for the Speed Kit plugin. For this you need the OpenSSL PHP extension. Do you have root access to your server and could you install it?

    Many greetings,
    Konstantin from Baqend

    Thread Starter mfdale

    (@mfdale)

    Hi Konstantin,

    Thank you for the reply.

    I do not have root access to my server, so have contacted my hosting tech support.

    I ran a phpinfo file and found the following info:

    Registered Stream Socket Transports tcp, udp, unix, udg, ssl, sslv3, tls, tlsv1.0, tlsv1.1, tlsv1.2

    openssl
    OpenSSL support enabled
    OpenSSL Library Version OpenSSL 1.0.1e-fips 11 Feb 2013
    OpenSSL Header Version OpenSSL 1.0.1e 11 Feb 2013
    Openssl default config /etc/pki/tls/openssl.cnf

    Thanks
    Matt

    Plugin Author baqend

    (@baqend)

    Hi again, Matt,

    it seems that your OpenSSL configuration is fine and the request should work.

    According to this Stack Overflow question, it also may be a firewall issue… do you know if your hoster allows requests to 3rd party domains? If you can whitelist IPs on your own, these are ours:

    • 151.101.1.132
    • 151.101.65.132
    • 151.101.129.132
    • 151.101.193.132

    Otherwise, maybe it was just a temporary issue. It could be possible that the problem simply resolves on its own.

    I am sorry for all the circumstances, I hope we can get it to work!

    Kind regards,
    Konstantin

    Thread Starter mfdale

    (@mfdale)

    Hi Konstantin, thanks.

    I tried the above suggestions and it didn’t make a difference, so reversed the changes. Tried again for a few days and received the same errors. Then suddenly, it just started working… No idea how/why, but all good now ??

    All installed and set up.

    Thanks for trying to get it working.
    Matt

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal error: Error sending GET / SSL connect error’ is closed to new replies.