Ok it works in Safari and Firefox. Why must it be chromium that doesnt
work...
sorry, but i am on a mac, with mac os x.
i know 'how' my problem could be solved
when i go to a page like this (encrypted, but with a minor error) for the
first time, i get asked on a red warning screen if i want to proceed or
not. when i click proceed i can connect to the page with https crossed out.
whenever i reconnect it just works.
now i should 'only' be able to get this red warning window again where i
can accept the connection.
I also have this problem, apparently the problem only on Chrome.
I think it has to do with proxy settings ? I'm behind a proxy and get this
error too...
i dont use proxy but i have this problem on several google pages.
Comment #12 on issue 82807 by rsl...@chromium.org: Error 202
(net::ERR_CERT_AUTHORITY_INVALID): Unknown error.
http://code.google.com/p/chromium/issues/detail?id=82807
(No comment was entered for this change.)
I was using a rather old Ubuntu (9.10) and the invalid cert error appeared
only using chrome but not using firefox or seamonkey. Updating Ubuntu to a
more recent version (11.04) solved the problem with chrome. It seems, that
the self-signed certificates have been handled wrong by the older Ubuntu.
No errors occurred at all using Win 7 64bit.
So, I think the problem is mainly related to the certificate manager used
by the OS rather than a problem of chrome itself.
I updated my os to 10.7. Now everything works fine again.
I'm on 10.5 and 14.0.835.8 dev and still getting this for
https://chatenabled.mail.google.com . However, every now and then one will
go through. Note that mail.google.com ssl works fine.
rsleevi: Do I need to open a new bug?
If anyone's searching for bugs about gmail chat breaking, not working or
loading in recent versions of Chrome dev with the "Unable to reach Gmail"
error this is the cause.
davidgil...: I think this is the correct bug (You're on a Mac, you're
getting the error on Google properties).
A couple follow-up questions:
1) Are you behind a proxy or running any local proxy servers?
2) Are you running any anti-virus on your Mac?
3) Can you confirm it's ERR_CERT_AUTHORITY_INVALID and not ERR_CERT_INVALID
that you're receiving?
https://github.com/ gives me SSL Error: http://i.imgur.com/pnzc9.png
I have no proxy.
I have no anti-virus.
14.0.835.8 (dev channel).
bwhiteh...@ Can you click on the lock icon (with the red X), then click
Certificate Information, and attach a screenshot?
Also, does this site work in Safari?
Actualy, bwhiteh...@, this appears to be a different issue. Can you please
file a new issue?
Re: comment 20:
Nope, nope and yes. http://i.imgur.com/6XLfJ.png
davidgil...: Thanks for confirming. Can you follow-up with the checks from
comment #22 as well?
In addition, can you enable logging as detailed at
http://www.chromium.org/for-testers/enable-logging and attach a log? Please
see also the note "What personal information does the log file contain?" at
the bottom of that page, and review the log for any personal information
before submitting.
I have yet to be able to reproduce this in a 10.5.8 VM or 10.6.8 machine
with the URLs specified, so I apologize for the amount of follow-up
information I keep requesting.
Re: comment 25:
Google doesn't show a lock or red line through the https.
http://i.imgur.com/xQscT.png Safari 5.0.5 works. I've sent the log in an
email.
rayanna: I've marked this back as Unconfirmed, because I don't believe any
of the recent SSL fixes should have addressed this. This is apparently an
issue that only manifests for some users, so the absence of a repro
unfortunately doesn't necessary mean an absence of an issue.
Given that my current suspicion is the problem may be related to one or
more intermediate certificates present on the system affecting the chain
that Chrome builds, I'd like to leave this as "Unconfirmed" until we can
get more information. I've marked it "Action-FeedbackNeeded" to indicate
that as well.
Comment #28 on issue 82807 by rsl...@chromium.org: Error 202
Windows 7 Professional. Installed a new version of Google Chrome
13.0.782.107, thought the error that was described previously fixed. But
there again when you open the service Google / Documents. An error (web
page at https://docs.google.com/?hl=ru&tab=wo, may be temporarily down or
moved permanently to a new address. Error 202 (net::
ERR_CERT_AUTHORITY_INVALID): Unknown error.)
europapl...: This issue is being used to triage a Mac-specific issue. Could
you please file a new bug report for the Windows issue?
Just to confirm this still occurs for me now on 14.0.835.15 dev on OS X
10.5.8.
I'm not sure if it's an intermediate certificate issue as this issue is
sporadic: the sites will work, then they will stop (e.g. Google+ works for
a while, then later half of the images stop loading on the site).
I'll try again to get a verbose log of it, but every time I enabled it, the
problem didn't happen (in the first few minutes I tried).
chris@: that sounds possibly like Issue 91400. To make sure this bug is the
right bug, at any point do you get the error page shown in the screenshot
of the original bug report?
I get a 202 error page, as shown in the screenshot in the original bug
description above.
I have also seen the certificate error as shown in comment 21 (on a Google
site).
Here's what I'm seeing:
http://minus.com/md4w3RD - Untrusted Security Cert - this is for Picasa,
but it happens at *every* google.com. site.
http://minus.com/md4w3RD - Can't access google docs. Some sites simply
refuse access. What makes it even worse is that Chrome doesn't seem to
give direct access to the certificate so that it can be uploaded into the
proper cert store to grant access.
Sorry about the delay in responding - I haven't been co-located with this
particular PC for awhile.
I get this same problem (Error 202 (net::ERR_CERT_AUTHORITY_INVALID):
Unknown error.) every time I close my computer and open it again. Running
Mac OS 10.6.8. And it does ONLY happen in Chrome; Safari and others work
fine.
To get around it I toggle the setting in preferences->under the
bonnet->HTTPS/SSL->Check for server certificate revocation (i.e. I'll to
try connect to gmail, won't work (Error 202), uncheck said box in prefs if
it's checked or vice-versa, try to connect again and it works).
Rather strange it has to be said.