"Connection is not private" warnings

One of the recipients of emails sent through IS is getting error messages that the connection to the infusionsoft link isn’t private. This is the first red flag warning that has been reported to us, and it doesn’t happen when we’re testing the emails or when we receive the final emails in our account.

This is today’s link, which generated the error for this user: https://sb380.infusionsoft.app/app/linkClick/11914/032f06b0243f018c/5923400/929fdf842f43e784

Hi, @Jennifer_Roland. If the problem were on Infusionsoft’s end, it would be an SSL issue that would impact everyone. This is more likely due to the user’s web browser settings or local firewall. Here are some things to check:

https://www.quora.com/How-do-you-fix-Your-connections-isn’t-private-problem-when-opening-with-the-Google-Chrome-browser

Thank you. I’ve sent these troubleshooting tips on to the user reporting the issue.

1 Like

I find the most frequent cause of this is an incorrect date/time on the computer. I just checked this certificate real quick using a tool, and it looks good. (P.S. I have no special access, I just used some certificate tools to verify this)…

openssl s_client -showcerts -servername sb380.infusionsoft.com -connect sb380.infusionsoft.com:443 </dev/null

-----BEGIN CERTIFICATE-----
MIIHWDCCBkCgAwIBAgIQBh9VgzlTo/oSCxr1Q7R+kDANBgkqhkiG9w0BAQsFADBN
MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMScwJQYDVQQDEx5E
aWdpQ2VydCBTSEEyIFNlY3VyZSBTZXJ2ZXIgQ0EwHhcNMTcxMDI2MDAwMDAwWhcN
MjAwNTEwMTIwMDAwWjCBmTELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3Ju
aWExFDASBgNVBAcTC0xvcyBBbmdlbGVzMS0wKwYDVQQKEyRWZXJpem9uIERpZ2l0
YWwgTWVkaWEgU2VydmljZXMsIEluYy4xEzARBgNVBAsTClRlY2hub2xvZ3kxGzAZ
BgNVBAMMEiouaW5mdXNpb25zb2Z0LmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBAJyfurcRpoeCmMMbttFBRFJBAYst4b/UTIKGBe9H43WXkiEjgF7i
Hh1i6HKJahtskjek6B9k3DYZqnpuvq712943FixLKclXvCDrx8WeP93K5N7l3oh6
V4r14vGf99nPD2M/1KBCSJkfXwe0i0Yt7ja3N/Gu/Bqugb3/kB4PhrQGPZUMJiCC
LRbcs4fSdHybhdiAvhdWjFnj1Pe1oq/0N5zhR9J0mfQ/y2Qd0fFI04omjWPKXP7X
2BDS94Cag1+IheMrtcM2iwd1+BXNZ3NA85G/y2JlanAk/DGP5hyQeZwzUXojVgPS
pBtY4bc7Z9UDom7PCU3iDuhw6A0Fk9pbiWsCAwEAAaOCA+UwggPhMB8GA1UdIwQY
MBaAFA+AYRyCMWHVLyjnjUY4tCzhxtniMB0GA1UdDgQWBBTarXzfZ9sSicq978w4
xAapmb1G+DAvBgNVHREEKDAmghIqLmluZnVzaW9uc29mdC5jb22CEGluZnVzaW9u
c29mdC5jb20wDgYDVR0PAQH/BAQDAgWgMB0GA1UdJQQWMBQGCCsGAQUFBwMBBggr
BgEFBQcDAjBrBgNVHR8EZDBiMC+gLaArhilodHRwOi8vY3JsMy5kaWdpY2VydC5j
b20vc3NjYS1zaGEyLWcxLmNybDAvoC2gK4YpaHR0cDovL2NybDQuZGlnaWNlcnQu
Y29tL3NzY2Etc2hhMi1nMS5jcmwwTAYDVR0gBEUwQzA3BglghkgBhv1sAQEwKjAo
BggrBgEFBQcCARYcaHR0cHM6Ly93d3cuZGlnaWNlcnQuY29tL0NQUzAIBgZngQwB
AgIwfAYIKwYBBQUHAQEEcDBuMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5kaWdp
Y2VydC5jb20wRgYIKwYBBQUHMAKGOmh0dHA6Ly9jYWNlcnRzLmRpZ2ljZXJ0LmNv
bS9EaWdpQ2VydFNIQTJTZWN1cmVTZXJ2ZXJDQS5jcnQwDAYDVR0TAQH/BAIwADCC
AfYGCisGAQQB1nkCBAIEggHmBIIB4gHgAHYApLkJkLQYWBSHuxOizGdwCjw1mAT5
G9+443fNDsgN3BAAAAFfWgbiPQAABAMARzBFAiEAkRN00h41PPFMgDv7JwB785sC
hVJS4O80MtaiL8sv8kkCICohTKK5YpFi1e8kMd7kSlnA5j847rlQfv+6cRb1w0D/
AHcAVhQGmi/XwuzT9eG9RLI+x0Z2ubyZEVzA75SYVdaJ0N0AAAFfWgbjXgAABAMA
SDBGAiEAjlwau2SDfYJ43tCFYgCTeVhM3XxgLqazwerfUGf1G1gCIQC3NrTOqMgt
0JkgKqlUPtdl+6jk9iMGqLVCLQPTR+da6gB1AO5Lvbd1zmC64UJpH6vhnmajD35f
sHLYgwDEe4l6qP3LAAABX1oG5TUAAAQDAEYwRAIgJPSjFqi6K/t91iNiB0PAU8It
8StjrEUxuNOWow5VjvwCIHsacPW6zgYzji3yUXH7Q5mEOJQMCWzsIYvmDqPwENF7
AHYAu9nfvB+KcbWTlCOXqpJ7RzhXlQqrUugakJZkNo4e0YUAAAFfWgbjDwAABAMA
RzBFAiEApLOLpm81mkcUTLrjxgYNeNNCetA+f6y2u0T8XMLNNbwCIAZjskDmFFZq
FBvtO0rvd4jk8l8hSfB9KrpTrqznkaTnMA0GCSqGSIb3DQEBCwUAA4IBAQCODGld
UoDJKCApejaAROqTTZXrIGbnuccwPbbhHYYHwNUnplY9w7m+yZ1+sN9F0UtymPtW
V9tfZGngYh4/x1FJG53h/riPM2cktdQ7YIIEjblLiJQB4/E0A2KFYBquWH5BbIxe
EEBjLuJXAtbiwpGMsVCkSYQL97l72fzaiyl4hCtNh41HCbsCQxuAJT8kbGKmQgMF
itSiiYR+JJktm3piYCvdYs97VrTligj3oWITy16Jp94YKI0leZkisIeXFpOiMgQK
a45T52aT3pWLkra7xzdWTw2l2fWyU/KfuL74Py/G3aprPaEGKGe/Ty2NBV0FhYWr
lVCSixqN8iQ2hYvO
-----END CERTIFICATE-----

And then if you decode it here: Certificate Decoder - Decode certificates to view their contents it shows it’s good.

1 Like

The most common cause of connection is not private is an incorrect date & time set on your PC. Chrome makes sure that your computer’s clock matches the clock in a Google server farm, and if it doesn’t, will block the connection to HTTPS sites for security reasons.

To fix your issue, set your computer’s clock to the correct current time.

Go to System Preferences
Choose Date & Time
Navigate to the Date & Time tab
Change the current time to the correct time (accurate to the nearest minute will do).
Edit: If it’s not your computer’s fault, it’s just a Chrome security feature. Chrome detects malicious activity going on with the site (like malware-laced ads, breach by hackers, etc.) and automatically warns you to protect you if it believes your security or safety might be at risk. If you want to override the warning, just hit Advanced → Continue to site.