SSL certificate doesn't match circleci.com


#1

When I visit circleci.com, I get a “Your connection is not private” error in Chrome. The SSL certificate details list a *.enbrite.ly as the certificate’s host name. I get a similar error in Chrome.

I realize that others aren’t necessarily experiencing this and that it may be a problem with my upstream internet provider, but I wanted to post here in case you have suggestions or others encounter it as well.


#2

I’m thinking that it’s an upstream issue.

Do you happen to have an example url that others can check?

Also, are you running an ad blocker, just in case it’s an issue with a weird ad or tracker?


#3

Sure. I have this problem when I visit the home page: https://circleci.com/

I’m not running any ad-blocker. Furthermore my Safari is usually unused and has a completely default set-up, but encounters the same problem.


#4

Here’s what my chrome says:

Can you take a look at yours and see what it says? You can get this by clicking on the padlock.


#5


#6

Right.

Well, that’s not good.

Do a ping for me please and tell us what ip it’s trying for circleci.com?

It should be one of these 4:

circleci.com. 16 IN A 54.173.216.204
circleci.com. 16 IN A 52.3.180.143
circleci.com. 16 IN A 54.210.65.233
circleci.com. 16 IN A 54.86.168.154


#7

Thanks for helping me narrow this down. I got the correct response from nslookup and dig, but a ping hit the wrong IP:

$ nslookup circleci.com
Server:		192.168.1.1
Address:	192.168.1.1#53

Non-authoritative answer:
Name:	circleci.com
Address: 52.3.180.143
Name:	circleci.com
Address: 54.210.65.233
Name:	circleci.com
Address: 54.173.216.204
Name:	circleci.com
Address: 54.86.168.154
$ ping circleci.com
PING circleci.com (52.21.178.223): 56 data bytes
...

I reset my local DNS cache and started to resolve to the right IP:

$ sudo killall -HUP mDNSResponder
$ ping circleci.com
PING circleci.com (54.210.65.233): 56 data bytes
...

In Chrome, I had to go to net-internals and hit the Clear host cache button, after which I started to reach the site correctly.

Thanks again!


#8

Awesome! Glad to hear you got it sorted!


#9