# Support.elastic.co has an invalid certificate

**URL:** <https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167>\
**Category:** Meta Elastic\
**Created:** [October 6, 2020, 4:59pm UTC](https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167 "2020-10-06T16:59:15Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![jwasserman](https://avatars.discourse-cdn.com/v4/letter/j/ecc23a/32.png) [@jwasserman](https://discuss.elastic.co/u/jwasserman)\
**Post date:** [October 6, 2020, 4:59pm UTC](https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167/1 "2020-10-06T16:59:15Z")

</div>

[https://support.elastic.co](https://support.elastic.co) is not secure. I do not want enter my credentials because the certificate is invalid.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 6, 2020, 5:38pm UTC](https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167/2 "2020-10-06T17:38:11Z")

</div>

I can see a valid certificate. Are you sure your browser and Os are up to date?

Could you share some screenshots?

---

<div class="post-metadata">

**Author:** ![jwasserman](https://avatars.discourse-cdn.com/v4/letter/j/ecc23a/32.png) [@jwasserman](https://discuss.elastic.co/u/jwasserman)\
**Post date:** [October 6, 2020, 6:29pm UTC](https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167/3 "2020-10-06T18:29:07Z")

</div>

Thanks for the reply, David. I'm on MacOS Catalina 10.15.7. I'm using Chrome Version 85.0.4183.121 (Official Build) (64-bit). I attached a screenshot of the error.

 ![Screen Shot 2020-10-06 at 10.49.33 AM](https://us1.discourse-cdn.com/elastic/original/3X/6/a/6af9c79c72d3202e725ed31285ec4bed3d32db0a.png)

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [October 7, 2020, 2:45am UTC](https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167/4 "2020-10-07T02:45:35Z")

</div>

The cert is valid I just checked I chrome and FFox. I suspect perhaps you have an old cached certificate it was updated in June 2020. Perhaps try with incognito?

---

<div class="post-metadata">

**Author:** ![jwasserman](https://avatars.discourse-cdn.com/v4/letter/j/ecc23a/32.png) [@jwasserman](https://discuss.elastic.co/u/jwasserman)\
**Post date:** [October 7, 2020, 5:38pm UTC](https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167/5 "2020-10-07T17:38:21Z")

</div>

Hi, Stephen, thanks for the reply. I tried removing all cached data from Chrome, and I tried opening [support.elastic.co](http://support.elastic.co) with Incognito. Both attempts failed.

I attached a screenshot showing the cert hasn't expired. ![Screen Shot 2020-10-07 at 10.35.08 AM](https://us1.discourse-cdn.com/elastic/original/3X/3/2/3280dd3184eeb3bd1cf432a998f487ca6d1c52a7.png)

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [October 7, 2020, 5:58pm UTC](https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167/6 "2020-10-07T17:58:59Z")

</div>

On Mac...

BTW I am also on MacOS Catalina 10.15.7

Have you looked into your Keychain Access to see if you have an old cert that needs to be cleaned out.

Do you work at a company that that filters all your traffic through a proxy?

Can you try from another machine?

Try the url from your mobile?

I will check internally with our support but if we had a bad cert we I suspect we would be flooded with calls which we AFAICT we are not as I looked through the internal channel.

Update : I have tried from 2 different macs and a mobile, none are showing a bad cert, I suspect it is something in your ecosystem.

---

<div class="post-metadata">

**Author:** ![jwasserman](https://avatars.discourse-cdn.com/v4/letter/j/ecc23a/32.png) [@jwasserman](https://discuss.elastic.co/u/jwasserman)\
**Post date:** [October 7, 2020, 7:33pm UTC](https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167/7 "2020-10-07T19:33:22Z")

</div>

Thanks, Stephen. I think you're correct about it being specific to my ecosystem. I'm able to access it without cert issues from another machine and on mobile.

I need to double check my Keychain Access and whether there is a proxy I'm unaware of.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [October 22, 2020, 12:22am UTC](https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167/8 "2020-10-22T00:22:39Z")

</div>

@jwasserman BTW got a report of same thing from another user... curious if you have seen again...I am checking internally again...

UPDATE : Turns out there is something down deep / a bit esoteric with our SalesForce integration which we are the process of fixing.

Just thought I would follow up

---

<div class="post-metadata">

**Author:** ![jwasserman](https://avatars.discourse-cdn.com/v4/letter/j/ecc23a/32.png) [@jwasserman](https://discuss.elastic.co/u/jwasserman)\
**Post date:** [October 22, 2020, 12:37am UTC](https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167/9 "2020-10-22T00:37:53Z")

</div>

Hi, Stephen. Thanks for the follow-up. I still see the issue when I check on my work machine behind VPN, and I have not changed anything on it from last time - I just ended up ignoring it and proceeding since the site works OK from elsewhere.

---

<div class="post-metadata">

**Author:** ![jwasserman](https://avatars.discourse-cdn.com/v4/letter/j/ecc23a/32.png) [@jwasserman](https://discuss.elastic.co/u/jwasserman)\
**Post date:** [October 22, 2020, 12:39am UTC](https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167/10 "2020-10-22T00:39:30Z")

</div>

I can confirm it works on the same machine without VPN. So it might be related to that.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 19, 2020, 12:39am UTC](https://discuss.elastic.co/t/support-elastic-co-has-an-invalid-certificate/251167/11 "2020-11-19T00:39:50Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
