Resolving an SSL Connect Error | Community
Skip to main content
A
Anonymous
December 13, 2016
Question

Resolving an SSL Connect Error

  • December 13, 2016
  • 2 replies
  • 4681 views

We have been receiving an SSL Connect Error when using a webhook to POST to a third party database. We identified the problem as our domain not having an SSL certificate. This has now been purchased and our domain is now secure, but our POST is still receiving the SSL Connect error. When I look at our domain name in our Landin Page section, the domain still appears as rather than

Is there something else we need to update/change within our Marketo instance for the system to recognize the secure domain, or do I just need to wait for it to automatically update? If the latter, do you know how long we need to wait?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

SanfordWhiteman
SanfordWhiteman
Level 10
December 13, 2016

The server hosting the Landing Page domain and the server hosting a webhook endpoint have no inherent relationship with each other.

That is, if you have uploaded your SSL cert to Marketo, that merely enables inbound secure connections to lp.example.com.  It has nothing to do with outbound connections from your Marketo pod to webhook.example.com.  That they both are subdomains of example.com is a distraction from your underlying problem.

A
Anonymous
December 13, 2016

Ok, great. Thank Sanford, that makes sense. So if the SSL certificate on my domain doesn't impact my ability to make a secure POST do you know what the issue would be? You're right, this isn't about collecting information is a secure fashion, my problem is posting data securely to another database.

SanfordWhiteman
SanfordWhiteman
Level 10
December 13, 2016

For clarity, better to stop thinking in terms of "the SSL certificate on my domain" as this will become ambiguous. SSL certs do secure one or more domains, but they never go on a domain, they go on a server, one server at a time.

Anyway... we're clear that the cert installed on the Marketo server hosting your LP domain doesn't have anything to do with outbound .

What does have to do with outbound https: is whether the cert on your webhook endpoint is signed by a CA (certificate authority) that Marketo includes in its CA bundle. (To put this somewhat closer to English, it means that Marketo must recognize the endpoint's cert as coming from a trusted SSL provider.) Can you provide a sample endpoint URL?

Kenny_Elkington
Adobe Employee
Kenny_ElkingtonAdobe Employee
Adobe Employee
December 13, 2016

Do you have a specific error message that you're seeing?

SanfordWhiteman
SanfordWhiteman
Level 10
December 13, 2016

Kenny, it's

This reminds me of a convo we had some time ago about TLS 1.2. I had an OpenSSL test server and was able to force webhooks to fail even though I was supporting all TLS 1.x protos.

Kenny_Elkington
Adobe Employee
Kenny_ElkingtonAdobe Employee
Adobe Employee
December 14, 2016

Just trying to be certain what the message is for this case.

Terms & ConditionsAccessibility statement

Loading footer...