Support » Plugin: Brilliant Web-to-Lead for Salesforce » Form Not Working After Update

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Nick Ciske

    (@nickciske)

    Failed to connect to Salesforce.com.

    This could be an SSL verification issue, or a TLS version issue. It’s hard to say without a debug log.

    You can download v2.7 here and replace the plugin in your install to revert to the older version.

    The only change in this release was the Salesforce Web-to-Lead API endpoints, which are supposed to be active now…

    As the new endpoint URL is already available, customers are strongly encouraged to complete these updates as soon as possible to take advantage of the improved functionality performance.

    Source:
    https://help.salesforce.com/articleView?eid=ss-tc&id=Updating-the-Web-to-Case-and-Web-to-Lead-Endpoint-URL&language=en_US&type=1

    Thread Starter dwang1109

    (@dwang1109)

    I just reverted back to the old version you mentioned but the issue is still there. Anything else it may be?

    Plugin Author Nick Ciske

    (@nickciske)

    I only changed 2 lines in 2.7.1, so if going back to 2.7 didn’t fix it, it’s unlikely to be code related.

    As I said above, it’s usually related to SSL: there is a plugin option to validate (or not) the SSL certificate before connecting to Salesforce. Try toggling that and seeing if that helps.

    Also, it can be related to Salesforce dropping support for insecure versions of SSL/TLS — but that happened months ago. Unless your host changed the version of OpenSSL or what encryption methods it supports, it’s not likely the culprit.

    I can say that both endpoints work fine on my development environment, so it’s something unique to your server/host (e.g. version or config of OpenSSL, PHP, CURL, etc) that’s causing this issue.

    Thread Starter dwang1109

    (@dwang1109)

    Here is the error I see. Is this what you’re referring to in terms of the SSL? If so, where would I fix this?

    = Addditional Information =

    WP_Error Object
    (
    [errors] => Array
    (
    [http_request_failed] => Array
    (
    [0] => cURL error 51: SSL: no alternative certificate subject name matches target host name ‘webto.salesforce.com’
    )

    )

    [error_data] => Array
    (
    )

    )

    Plugin Author Nick Ciske

    (@nickciske)

    Curl is trying to validate the SSL cert… and it looks like Salesforce may have a configuration issue there.

    Verification should be off by default… let me verify that.

    Like I said it works fine in my testing so it may be a curl config setting on your host.

    Plugin Author Nick Ciske

    (@nickciske)

    Thee’s something up with your CURL install, possibly an out of data ca.pem file (that’s the list of trusted root certificates)?

    Qualys SSL Score is A-.

    WhyNoPadlock says:

    Domain Name: webto.salesforce.com

    URL Tested: https://webto.salesforce.com/servlet/servlet.WebToLead
    Number of items downloaded on page: 0

    *** NOTE ***: 0 items means no images were downloaded or existed on the page. It’s likely the URL you submitted was not a valid secure URL, or the page being tested only has text on it. Try copying and pasting the secure URL into a new browser window to make sure it displays as you’d expect.

    Valid Certificate found.

    Certificate valid through: Jul 1 23:59:59 2018 GMT
    Certificate Issuer: Symantec Corporat
    SSL Protocols Supported: TLSv1 TLSv1.1 TLSv1.2

    Thread Starter dwang1109

    (@dwang1109)

    Hi Nick is this something you can fix with the premium support? Our hosting provider is saying it’s not on their end and they have no idea what is going on.

    Plugin Author Nick Ciske

    (@nickciske)

    I’d be surprised if I couldn’t find a fix / workaround if I was able to test/debug on your server. Any fix should be able to be rolled into the next minor release.

    So yeah, if you want to do a premium support incident I could look at it Monday.

    Plugin Author Nick Ciske

    (@nickciske)

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Form Not Working After Update’ is closed to new replies.