Google Uses an Invalid Security Certificate. Thanks Firefox!

New things are not necessarily the best things. What they say is an improvement of a previous version can be the worst version. This is what happened to Firefox Beta 3.

Here I am documenting how Firefox Beta 3 Murdered Google Adsense. When you type google.com/adsense, which will transport you to your Google Adsense account, this is what you get, (thank you Firefox for wasting my time).

google.com uses an invalid security certificate.

The certificate is only valid for www.google.com.

(Error code: ssl_error_bad_cert_domain)

On a dead Firefox window, the explanation follows:

This could be a problem with the server's configuration, or it could be someone trying to impersonate the server.

If you have connected to this server successfully in the past, the error may be temporary, and you can try again later.

The next blunder is that Firefox asked you if you would accept Google's certification.

Or you can add an exception…(color blue, clickable). . .Next message

You should not add an exception if you are using an internet connection that you do not trust completely or if you are not used to seeing a warning for this server. (just click next) and here's the moment of truth.

Firefox says Google could be a fake web site.
Announcement: Learn how to make a website with Thinkhost, go to ThinkHost Here.

Comments :

8 comments to “Google Uses an Invalid Security Certificate. Thanks Firefox!”
Anonymous said...
on 

you're pretty dumb, the certificate does not become active until the 27th, and this generates an error.

Anonymous said...
on 

This is the dumbest article I have ever read... The correct URL for Google Adsense is http://www.google.com/adsense/

It has absolutely nothing to do with Firefox.

bronius said...
on 

I think there are too many opinions flying around here, both in the heated post and the followup comments-- the fact is, the ff3 invalid certificate message is a little misleading. We all came here looking for a solution, and this article matched our queries.

My interest is _how_ to make https://somedomain.com redirect to https://www.somedomain.com without first throwing an invalid ssl certificate warning on the first domain and without having to purchase two ssl certs or a wildcard certificate. Can it be done?

Anonymous said...
on 

I bet that your clock on your computer is off.

Anonymous said...
on 

ummm, it was a beta. Heaven forbid that a piece of software that is in "beta" display an error of any kind.

dude, you wasted your own time bot only in using a beta browser as your main browser, but in bitching about it in this post.

Anonymous said...
on 

your computer clock is off. Happened to me as well.

Anonymous said...
on 

"I bet that your clock on your computer is off."

I agree with this! I had a power failure, now (October 2, 2009 03:08 PM) the date and time of my windows xp system was (August 19, 2008 02:13 AM)

Thanks.

Anonymous said...
on 

its your windows clock or it could be that your Anivirus Scanning port 443,or any other SSL port and then you get invalid certificate(Tons of em annoying ),
i has nothing to do with FireFox or Google(Domains). its a problem on your end