Not connecting at all

  • Resolved clerihanboy

    (@clerihanboy)


    9 years, 4 months ago

    Hi,

    I hope that someone can help.

    Our website has a number of WP2L forms on the site and, tow days ago, all of them stopped working and displaying a Salesforce connection problem.

    I have deactivated and reactivated every plugin possible to check for conflicts. Furthermore, there were no changes made to Salesforce.

    It has happened all of a sudden.

    Has anyone got any ideas what I could try to do?

    CB

    • This topic was modified 9 years, 4 months ago by clerihanboy.
Viewing 15 replies - 1 through 15 (of 16 total)
1 2
  • Plugin Author Nick Ciske

    (@nickciske)

    9 years, 4 months ago

    What’s the site URL?

    Thread Starter clerihanboy

    (@clerihanboy)

    9 years, 4 months ago

    Hi Nick.

    It’s Acornregulatory.com

    Plugin Author Nick Ciske

    (@nickciske)

    9 years, 4 months ago

    Hmmm.

    There’s a SSL verification checkbox in settings: try toggling that to see if it helps.

    Can you turn on WP_DEBUG & WP_DEBUG_LOG, do a form submission, and post the results?

    Thread Starter clerihanboy

    (@clerihanboy)

    9 years, 4 months ago

    Okay Nick,

    This is going to sound silly -but how do I do that?

    CB

    Thread Starter clerihanboy

    (@clerihanboy)

    9 years, 4 months ago

    Nick,

    I debugged (found out how to do it) and got no errors showing just the ‘Salesforce can’t connect’ or similar term.

    Plugin Author Nick Ciske

    (@nickciske)

    9 years, 4 months ago

    Not silly at all. One of these days I’ll add a debug log to the plugin itself… but today is likely not that day…

    https://codex.wordpress.org/Debugging_in_WordPress

    Thread Starter clerihanboy

    (@clerihanboy)

    9 years, 4 months ago

    [26-Jan-2017 16:21:33] Salesforce response error: Array
    (
    [headers] => Requests_Utility_CaseInsensitiveDictionary Object
    (
    [data:protected] => Array
    (
    [date] => Thu, 26 Jan 2017 16:21:33 GMT
    [content-type] => text/html; charset=UTF-8
    [cache-control] => no-cache, must-revalidate, max-age=0, no-store, private
    [pragma] => no-cache
    [expires] => Thu, 01 Jan 1970 00:00:00 GMT
    )

    )

    Is this enough info from the debug log?

    Plugin Author Nick Ciske

    (@nickciske)

    9 years, 4 months ago

    Nope, that’s essentially an empty response from Salesforce — the Web to Lead API goes out of it’s way to be unhelpful when things go wrong…

    Thread Starter clerihanboy

    (@clerihanboy)

    9 years, 4 months ago

    This forum is not allowing me to post the entire log. What do you suggest? Thanks for your help on this to date Nick

    Plugin Author Nick Ciske

    (@nickciske)

    9 years, 4 months ago

    You can email it to nick [at] cimbura [dot] com

    Thread Starter clerihanboy

    (@clerihanboy)

    9 years, 4 months ago

    thanks Nick – that’s on the way to you now.

    Plugin Author Nick Ciske

    (@nickciske)

    9 years, 4 months ago

    This is the key bit:

    To access this website, update your web browser or upgrade your operating system to support TLS 1.1 or TLS 1.2.

    https://help.salesforce.com/articleView?amp;language=en_US&id=000221207&type=1

    So something changed at Salesforce, it was just way under the hood.

    Your host needs to upgrade their OpenSSL package so it supports newer versions of TLS, or you need to find a host with a clue – TLS 1.0 has been deprecated for ages…

    Thread Starter clerihanboy

    (@clerihanboy)

    9 years, 4 months ago

    So, let me get this right – my site host needs to upgrade to TLS 1.1/1.2?

    Plugin Author Nick Ciske

    (@nickciske)

    9 years, 4 months ago

    I believe curl and fopen use OpenSSL under the hood so that’s lrionaly what’s out of date here.

    Basically tour server is telling Salesforce it only supports TLS 1.0 and Salesforce is saying it no longer supports that.

    tthorp

    (@tthorp)

    9 years, 3 months ago

    Hi all. I’ve been dealing with this issue as well and this forum has been helpful. I’ve resolved the issue and have some info for people with the same difficulties – especially those on RedHat Linux hosting with NSS (instead of OpenSSL).
    If you want to test and see what TLS version and ciphers your curl is sending to a server, you can ssh into your sending server and run this command curl https://www.howsmyssl.com/a/check This is useful for testing. Note that you can also try specifying some secure options to see if your server can send secure options, like this curl https://www.howsmyssl.com/a/check --tlsv1.2 --ciphers rsa_aes_128_sha
    This seems particularly relevant for RedHat with multiple ciphers and TLS versions. It seems RedHat sends the least secure or oldest options by default.
    If specifying options helps you pass the test at howsmyssl.com then you are close to a solution. You have two options:
    1) figure out how to configure your server to pass the strongest TLS and ciphers by default or
    2) use a plugin to inject the options into wordpress’ curl calls. The following plugin does just that.
    https://wordpress.org/plugins/reid-plugins-curl-options/
    this is how I set it up:
    https://snag.gy/23oGSd.jpg

    Hope this helps!
    -Tim

Viewing 15 replies - 1 through 15 (of 16 total)
1 2

The topic ‘Not connecting at all’ is closed to new replies.