New issue 118706 by b...@kulbertis.org: HTTPS/Certificate websites always
have "Invalid Server Certificate" Error
http://code.google.com/p/chromium/issues/detail?id=118706
Chrome Version : 19.0.1068.1 (Official Build 126852) dev-m
URLs (if applicable) : https://google.com/
https://facebook.com/
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: Untested
Firefox 4.x: Ok
IE 7/8/9: Ok
What steps will reproduce the problem?
1. Request any webpage using https
What is the expected result?
The browser would accept the certificate because it actually is valid and
the page would load normally.
What happens instead?
Chrome displays an error claiming the website's certificate in invalid (see
attached screenshot)
Please provide any additional information below. Attach a screenshot if
possible.
Attachments:
invalidservercertificate.PNG 64.4 KB
Comment #1 on issue 118706 by rsl...@chromium.org: HTTPS/Certificate
websites always have "Invalid Server Certificate" Error
http://code.google.com/p/chromium/issues/detail?id=118706
Hi ben, thanks for filing this report.
The screenshot you provided has the error for google.com, so thanks for
including that. I had a question about the Facebook error you're reporting,
and wanted to see if it's the same as the google.com error or something
different.
Could you see if Issue 117834 /
http://code.google.com/p/chromium/issues/detail?id=117834 matches what
you're seeing? Or are you indeed seeing the "Invalid Server Certificate"
error when you try to access https://facebook.com /
https://www.facebook.com ?
The Facebook error is identical to the Google one. All sites I have tried
so far that use https have the same "Invalid Server Certificate" error.
That issue you linked, Issue 117834, is not the same as the issue I am
experiencing.
Ben, could you please send us details on the certificate chain you're
seeing? Click on the padlock (in the Omnibox/URL bar) that has the red X on
it. That will bring up a pop-up screen that tells you about the certificate
and its problem. You can then click on "Certificate Information" to get
more information. If you could send us that information, it would help.
I'm not sure of the best way to send you this information, but I've
included the certificate files if that helps. The errors I am seeing
throughout this process says things such as:
On the "red x" popup:
- Server's certificate is invalid
- The server certificate contains a weak cryptographic key.
On the the certificate information screen:
General Section:
- The integrity of this certificate cannot be guaranteed. The certificate
may be corrupted or may have been altered.
Certification Path:
- This certificate has an invalid digital signature. (On all three
certificates)
Please let me know if I can provide any more information.
Attachments:
Google.cer 805 bytes
Facebook.cer 976 bytes
Thanks for your continued patience in trying to identify and resolve this
issue, Ben.
While I'm glad to hear that Canary is not demonstrating any problems, I'm
still rather concerned about what you're experiencing with Dev, and that it
consistently happens. I would love to be able to identify the fix and
resolve it for both you and any other affected Chrome/Chromium users.
I was hoping I might try one further step of diagnostics. Unfortunately,
this is a bit of Windows' diagnostics, rather than Chrome, so it's not
exactly pretty or easy.
Microsoft has provided a document describing how to enable CryptoAPI 2.0
diagnostic logging at
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18844 .
If you can enable logging as described on Pages 9 and 10, that would be
fantastic. Please see the note about increasing the log size - I'd suggest
4 - 10 MB.
Even better would be if you could enable Level 5/Verbose debugging
(described on Page 14), but I understand if you don't have sufficient
privileges.
After you enable logging, repeat steps 1, 2, and 7, as agl@ documented in
comment #10. After doing this, save the Windows log as described on Pages 9
and 10 of that document. For size reasons, please feel free to e-mail
directly to rsl...@chromium.org if it ends up being too large to attach -
although I believe up to 10 MB is permitted as a bug attachment.
Again, sorry you're having this issue, and hopefully we'll be able to trace
it down! Thanks!
I just had this issue (with any site over HTTPS). Removing then installing
the Dev channel version again from the web resolved it.
Just a quick answer to your second question. You are right regarding other
browsers not having issues. I used Firefox in parallel without any issues.
Also, everything is fine with current Chrome Beta. Beta required a fresh
user profile, of course. So, I noticed the issue only with upgrade to Dev
1068.1.
As for your first question, I'll answer that a bit later when I get to a PC.
rsleevi, your guess was spot on. Switching user directory (to c:\temp, for
example) does provide a solution. I can open web sites via HTTPS.
Close Chrome, reopen.
Trying to access https://www.google.com results in Invalid Server
Certificate.
Clearing the profile directory (c:\temp) fixes the problem.
This happens on Dev 19.0.1077.3.
When I say that "clearing the profile directory fixes the problem", I mean
that it goes back to the initial state. The issue with 'invalid
certificate' appears again after browser restart.
vdesai: Thanks for your continued help in investigating this. This is a
very strange bug, and it's a bit baffling why chrome_shutdown_ms.txt should
have any effect on how SSL is working.
I'm wondering, with the chrome_shutdown_ms file in place, do the following:
1) Start a new command prompt (on Windows 7, Start then search for "Command
Prompt". On earlier versions, Start -> Run -> "cmd")
2) type "set CHROME_ALLOCATOR=winheap" (without quotes) and press
Enter/Return
3) Launch Chrome by typing in the full command (eg: "C:\Program Files
(x86)\Google\Chrome\Application\chrome.exe" - this time, WITH quotes). You
can determine the path by right clicking on the Chrome shortcut, clicking
Properties, and on the "Shortcut" tab, copying all of the text from
the "Target" - including any quotes or command-line parameters.
With this, please let me know if you still have trouble browsing, if Chrome
crashes, and if deleting the file and repeating Steps 1-3 make any
difference.
I did steps 1-3 and the problem still occurs just as before.
I switched to the canary build in hopes of a quicker fix (19.0.1084.1
canary). Win 7 x64.
It seems the stable build (v18) of chrome does not have this problem. It
happens with the dev and canary channels as far as I can tell. Perhaps
there is some sort of added security check or bug in v19
Hi,
I also did the steps from #35 and can confirm that the browser behavior
after setting the CHROME_ALLOCATOR and running from the same context is the
same as before. The Invalid Server Certificate error pops up when trying to
access https://google.com.
Deleting the chrome_shutdown_ms file and running the browser in the same
manner as earlier (same command prompt) fixes the issue. The site opens
with HTTPS immediately.
Chrome did not crash at any occasion.
vdesai: I noticed the bug right after the update from the previous version
of Dev channel to the one reported in the initial post (1068.1). Literally
after restarting the browser to upgrade I started noticing this behavior.
I am currently on 1077.3. Deleting the chrome_shutdown_ms.txt file prior to
running the browser makes it work ok. The fact that this text file has
anything to do with accessing sites via HTTPS sure is weird. :)
Don't know if this will help but it sure won't hurt. These are the contents
of my console window after running the above test. In between the two
invocations of Chromium, I ran my batch file that deletes the mentioned
text file.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Alen Siljak>set CHROME_ALLOCATOR=winheap
C:\Users\Alen Siljak>"C:\Users\Alen
Siljak\AppData\Local\Google\Chrome\Applicati
on\chrome.exe"
C:\Users\Alen Siljak>"C:\Users\Alen
Siljak\AppData\Local\Google\Chrome\Applicati
on\chrome.exe"
C:\Users\Alen Siljak>
OS Windows 7 x64
Chrome Version 18.0.1025.151
I am getting a similar issue with version 18 of chrome. Following comment
24 has resulted in apparent success and I haven't progressed further.
I have attached my results below.
Attachments:
Comparing --user-data-dir on left.png 249 KB
Chrome Certificate.cer 805 bytes
Chrome Certificate Working.cer 810 bytes
Comment #52 on issue 118706 by pal...@chromium.org: HTTPS/Certificate
websites always have "Invalid Server Certificate" Error
http://code.google.com/p/chromium/issues/detail?id=118706
We suspect that
http://src.chromium.org/viewvc/chrome?view=rev&revision=114740 and
http://src.chromium.org/viewvc/chrome?view=rev&revision=129725 (comment
#40) resolve this bug, but are not yet sure.
For everyone who just started encountering this issue: In order to be able
to identify and quickly resolve, can you please list the following:
1) The contents of chrome://version (you can copy and paste here or attach
a saved copy)
2) What version of Windows you're running (Windows XP? Vista? 7?)
3) If there are any conflicts listed under chrome://conflicts
a) Can you also attach your copy of Chrome conflicts to this bug (Right
Click the page -> Save As / click the Wrench -> Save Page As / Press
Control and S keys at the same time)
4) If removing "chrome_shutdown_ms.txt", as described in comments #28 and
#29 has any effect.
I noticed the same thing. What is the point of the chrome_shutdown_ms.txt
file any way?
I can confirm deleting chrome_shutdown_ms.txt temporally solves the issues.
Google Chrome 18.0.1025.151 (Official Build 130497) m
OS Windows
WebKit 535.19 (@113052)
JavaScript V8 3.8.9.16
Flash 11,2,202,229
User Agent Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML,
like Gecko) Chrome/18.0.1025.151 Safari/535.19
Command
Line "C:\Users\foocampo\AppData\Local\Google\Chrome\Application\chrome.exe"
--flag-switches-begin --flag-switches-end
Executable Path
C:\Users\foocampo\AppData\Local\Google\Chrome\Application\chrome.exe
Profile Path C:\Users\foocampo\AppData\Local\Google\Chrome\User Data\Default
Windows 7 64 bits
No conflicts
Deleting chrome_shutdown_ms.txt fixes the issue, but must be deleted
everytime I want to start chrome.
http://code.google.com/p/chromium/issues/detail?id=118706#makechanges
Ryan,
I also get no conflicts listed. Attached are the conflicts (conflicts.htm)
and version files.
19.0.1084.15 (Official Build 130829) dev-m
Windows 7, Ultimate edition, 64-bit
And, yes, I'm still using the workaround with deleting the ms file and
everything works just fine that way.
I have also tried disabling 3rd party shell extensions. In that case I
get "Error 7 (net::ERR_TIMED_OUT): The operation timed out." Reloading the
page brings back the Invalid Server Certificate. Trying a different site
brings the Invalid Server Certificate the first time.
Attaching conflicts file (conflicts2.htm) when the extensions are disabled.
Just noticed that one extension can't be disabled: Bluewire General
Property Sheet, C:\Windows\system32\BWContextHandler.dll. No idea what that
is or what it belongs to.
Conflicts3 is after enabling the extensions and deleting the ms file.
Attachments:
About Version.htm 7.9 KB
conflicts.htm 278 KB
conflicts2.htm 235 KB
conflicts3.htm 233 KB
Having the same issue as everyone else here:
1)
Google Chrome 19.0.1084.15 (Official Build 130829) dev-m
OS Windows
WebKit 536.5 (@113215)
JavaScript V8 3.9.24.7
Flash 11,2,202,229
User Agent Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.5 (KHTML,
like Gecko) Chrome/19.0.1084.15 Safari/536.5
Command Line "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"
--flag-switches-begin --flag-switches-end
Executable Path C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
Profile Path C:\Users\Matt Materniak\AppData\Local\Google\Chrome\User
Data\Default
2) Win 7 Ultimate x64
3) Modules (119) - No conflicts detected
4) Removing chrome_shutdown_ms.txt fixes
Same issue here...read this hole thread...half of it could't understand but
still made an idea over the bug. I don't know how to use the fix provided
in #40, could you detail that a little, please?
Google Chrome: 18.0.1025.151 (Official Build 130497)
OS: Windows 7 x64
WebKit: 535.19 (@113052)
JavaScript: V8 3.8.9.16
Flash: 11,2,202,229
No conflicts and I have to say that I couldn't find the
chrome_shutdown_ms.txt file anywhere on my hard-drive (all files -
including system files - visible)
I found the file after closing chrome...sorry...didn't see that
explanation...my bad
Same issue here...it started a few hours ago.
Read this hole thread...half of it could't understand but still made an
idea over the bug. I don't know how to use the fix provided in #40, could
you detail that a little, please?
Google Chrome: 18.0.1025.151 (Official Build 130497)
OS: Windows 7 Ultimate x64
WebKit: 535.19 (@113052)
JavaScript: V8 3.8.9.16
Flash: 11,2,202,229
No conflicts
removing the txt file fixes
To all the ideas I might add that I tried to manually export/import all the
trusted certificates from my laptop (which doesn't encounter this problem
(yet)) to my PC and when I tried to install the certificates everything
went OK, it said that import was finished but when I looked in the trusted
certificates tab in Chrome there were NONE. After reinstalling several
times, I noticed that on chrome's first run all trusted certificates are
present, after restarting (Chrome) they're all gone. Using the "deleting
txt file" solution brings them back until next restart when they're gone.
Hey, I came up with an idea. I'm not really good at programming but I
reminded how to create a batch file that deletes any file you point it at
doing so. The tricky part now, is, I don't know how to edit chrome.exe or
to make another batch that runs both my "deleting batch" and chrome after
that. I think this could be an "easy" patch, since deleting that text file
solves the actual problem. The developers should cover the rest. Is there
anybody here that knows how to make my idea work? I tried google-ing it but
I ended up reading smartasses' comments on how dangerous this is...bla bla
While I loathe to recommend this action, I notice that everyone who is
running who has been kind enough to attach their chrome://conflicts (please
follow that step in #3 and attach, it's very helpful in trying to identify
commonalities), would someone be willing to try and upgrade to Windows 7
SP1? You can do this by clicking Start -> All Programs -> Windows Update (
https://www.update.microsoft.com ).
While I continue to investigate the commonality between people reporting
this, and have not yet been able to reproduce under a variety of test
environments running a variety of Windows 7 x64 versions - both flavours
like Home vs Professional and versions like RTM vs SP1, it would be very
useful to eliminate Windows 7 SP1 from the candidate list. Windows 7 SP1
has a number of very important security fixes for Windows, so you're
generally doing yourself a favour by running the free security update.
I appreciate everyone's patience as we try to understand what is affecting
users machines and what can be done to work around it. Please continue to
star this bug for updates, and your continued assistance is most helpful in
identifying the root of this.
having the same issues here with getting onto all web sites its giving me
this security error and it was okay last night here at work but I guess
after you're new upgrade and me just signing on here today for the first
time I'm seeing this problem need fixed cause I need this browser for work
too..thanks
Attachments:
securityissue.bmp 2.3 MB
Google Chrome 18.0.1025.151 (Official Build 130497) m
OS Windows
WebKit 535.19 (@113052)
JavaScript V8 3.8.9.16
Flash 11,2,202,229
User Agent Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.19 (KHTML, like
Gecko) Chrome/18.0.1025.151 Safari/535.19
Command Line "C:\Documents and Settings\tech271\Local Settings\Application
Data\Google\Chrome\Application\chrome.exe" --flag-switches-begin
--flag-switches-end
Executable Path C:\Documents and Settings\tech271\Local
Settings\Application Data\Google\Chrome\Application\chrome.exe
Profile Path C:\Documents and Settings\tech271\Local Settings\Application
Data\Google\Chrome\User Data\Default
windows XP version 5.1 service pack 3
Modules (148) - No conflicts detected
Attachments:
conflicts.htm 217 KB
Hi Darlene, thanks for attaching your details. It's possible that you may
be running into http://code.google.com/p/chromium/issues/detail?id=117834 /
Issue 117834 instead.
To determine if that's the case, can you follow the steps from
http://code.google.com/p/chromium/issues/detail?id=114709#c1 and follow-up
here? Thanks!
rsleevi, I don't know if this has anything to do with this issue, but
there's a chance that it might. Right before this started occuring, I could
not log onto my university's wireless network from my laptop. It always
connected automatically, but suddenly it was not. I checked that it was not
a signal issue and that it was not an issue with the adapter or anything -
I could still log onto my home wireless network and log onto my
university's wireless through my phone. Windows kept asking me for my
username and password, and did not accept it after multiple attempts. I
tried removing and adding the wireless network, which did not solve the
issue. The point I am trying to make is that my school uses a certificate
for authentication for that network so it could actually be related to this
issue with Chrome. I am running on Windows 7 and IE is having no issues. My
school's network is called Purdue University's airlink or PAL 2.0 so you
can look up the specifics of the certificate. If these turn out to be
related, then the issue may not affect only Chrome but wireless network
authentication too.
Just an addition to my previous post, my university's wireless uses a
Thawte Premium Server CA as a trusted root certification authority to
validate the server certificate.
okay here are my screen prints for what you asked but i did not do that
enable logging thing since this is my work computer n not home
Attachments:
certpath.bmp 2.3 MB
here's the 2nd one
Attachments:
certinfo.p7b 659 bytes
Hi Darlene,
What you're encountering appears to be
http://code.google.com/p/chromium/issues/detail?id=120715 / Issue 120715 .
While I can understand the similarity to this issue, you're in luck, as
Issue 120715 is a well understood issue. Please see that bug and post any
questions you may have to it, but the summary is that the location you're
at appears to have an SSL filter in place that does things insecurely. The
systems/network administrator should upgrade the proxy to a secure version
to resolve this.
Cheers!
well then i may be shit out of luck here then with that..lol
Hi I am also facing the same issue as mentioned in above posts. meanwhile
am not able to find that "chrome_shutdown_ms.txt" file also in user data.
so not even getting the temporary resolution. could anyone please help!!!1
I'm having this exact issue also. Working fine last night when I shut
down, now can't get to anything https including all Google sites, Facebook,
Twitter, etc.
- Version: 18.0.1025.151
- OS: Windows 7 64bit
- No conflicts listed in "chrome://conflicts"
- "chrome_shutdown_ms.txt" does not exist in user profile
- cleared cache and cookies did not help
- other browsers running just fine
I have also tried disabling all Extensions (AdBlock and AVG Safe Search) to
no avail. I have another computer, same OS, same network, same browser
version, working fine with Chrome on the same sites.
Hi.I'm also having the same issue.
Deleting of the "chrome_shutdown_ms.txt" fixes it.
So I created a tiny batch file. If someone needs it, you should just put it
into the "c:\Users\%USERNAME%\AppData\Local\Google\Chrome SxS\Application\"
and start it instead of chrome.exe.
It will remove txt at first and then launch chrome.
Attachments:
del_bug.bat 59 bytes
I think I might be the first to report into this thread using Mac OSX
(unless I searched this thread using bad keywords)- I was sent here by
https://groups.google.com/a/googleproductforums.com/forum/#!msg/chrome/_GXgRj0b56g/gPOn5gCijwEJ
To answer rsleevi's questions (comment #53):
1) Google Chrome 18.0.1025.151 (Official Build 130497)
OS Mac OS X
WebKit 535.19 (@113052)
JavaScript V8 3.8.9.16
Flash 11.2.202.229
User Agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8)
AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.151 Safari/535.19
Command Line /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
-psn_0_7288563 --flag-switches-begin --enable-experimental-extension-apis
--flag-switches-end
Executable Path /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Profile Path /Users/craigflannagan/Library/Application
Support/Google/Chrome/Default
2) System Version: Mac OS X 10.6.8 (10K549)
Kernel Version: Darwin 10.8.0
3) chrome://conflicts does not seem to do anything for me, I only
get "Error 300 (net::ERR_INVALID_URL): Unknown error."
4) I don't think I actually have that text file on Mac OSX (I tried
spotlight search, nothing turned up)
Additional Notes:
This issue only happens for me when visiting http://penfed.org.
UNLIKE OTHERS, I'm able to visit https://www.facebook.com and
https://www.google.com with NO issues.
Attachments:
Screen shot 2012-04-07 at 7.30.20 AM.png 58.6 KB
Screen shot 2012-04-07 at 7.30.51 AM.png 105 KB
Forgot to mention that the issue when visiting penfed.org occurs only with
Chrome. No issue if using Firefox.
I have found that this can be temporarily fixed if, after opening Chrome
and getting the errors, open Task Manager. On the Processes tab, find the
Chrome.exe process using the highest amount of memory. Right-click that
process and choose End Process TREE. Confirm and wait for all Chrome.exe
processes to disappear, then open Chrome and it works fine. Sadly, if you
close and reopen it again, the error returns, but can be fixed again with
that same trick.
@rockto: This is merely killing Chrome and therefore preventing the
creation of the mentioned ms text file.
Quick workaround for those who just want Chrome to work (until a proper fix
has been found) - put the next two line in a batch file (.cmd) and run when
you want to run Chrome. Or download the attached file.
del "%LOCALAPPDATA%\Google\Chrome\User Data\chrome_shutdown_ms.txt"
start "" "%LOCALAPPDATA%\Google\Chrome\Application\chrome.exe"
Attachments:
run_chrome.cmd 145 bytes
I have found the same thing as rockto, it's a fairly easy temporary fix as
i could not find the txt. file that was specified earlier on.
I was trying to contribute to this discussion prior to my discovery of
the "end process tree" method, however i had to access it in incognito and
as a result i was signed out. I could then not sign in due to the Invalid
server certificate, it was frustrating.
I'm curious to see what is found to be the problem as it seems to be a very
random select few who have experienced it, though all roughly at the same
time by the looks of things so far.
@rockto, @jamie: are you saying that there is no chrome_shutdown_ms.txt
file in your profile directory once you *close* Chrome?
My profile (the default, I guess) is listed at the location specified in
#96 so yours might be the same.
I also have the same problem, it seems to affect Twitter.com, google.com
and us.army.mil. Pretty much any https site.
Can someone post a simple easy to understand fix for the error to correct
the "Invalid Server Certificate" Error. I have downloaded the security
certificate file which fixes the problem to run one session of Chrome, but
needs to be run again next time I open it.
coronabeach25, as far as I know this is a open, live issue being worked on.
Google Chrome 18.0.1025.151 (Official Build 130497) m
OS Windows
WebKit 535.19 (@113052)
JavaScript V8 3.8.9.16
Flash 11,2,202,229
User Agent Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML,
like Gecko) Chrome/18.0.1025.151 Safari/535.19
Command
Line "C:\Users\CP\AppData\Local\Google\Chrome\Application\chrome.exe"
--flag-switches-begin --flag-switches-end
Executable Path
C:\Users\CP\AppData\Local\Google\Chrome\Application\chrome.exe
Profile Path C:\Users\CP\AppData\Local\Google\Chrome\User Data\Default
Windows Version: Windows 7
3) No conflicts
4) Oddly I this file didn't exist when I looked.
Attachments:
Chrome Conflicts.htm 281 KB
Issue 122539 has been merged into this issue.
Having same issues since yesterday..
Has anyone consider this a symptom of re-direct virus, or is this just a
sure thing chrome issue?
I as with most only experienced the issue with google sites, but only in
chrome, not firefox.
I uninstalled Chrome, including all my data.. rebooted and reinstalled..
seems to be working fine now.. fingers crossed
1. Windows 7 ultimate (64bit)
2.
Google Chrome 18.0.1025.151 (Official Build 130497) m
OS Windows
WebKit 535.19 (@113052)
JavaScript V8 3.8.9.16
Flash 11,2,202,229
User Agent Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML,
like Gecko) Chrome/18.0.1025.151 Safari/535.19
Command
Line "C:\Users\Jonathan\AppData\Local\Google\Chrome\Application\chrome.exe"
--flag-switches-begin --flag-switches-end
Executable Path
C:\Users\Jonathan\AppData\Local\Google\Chrome\Application\chrome.exe
Profile Path C:\Users\Jonathan\AppData\Local\Google\Chrome\User Data\Default
3. Modules (109) - No conflicts detected
4. the File was not there
5. I would like to Point out that if you Uninstall chrome and reinstall
it.. it will fix the problem untell you close it out completly then you're
back where you started... also I don't know if this will help at all but if
you download something thought an SSL Connection thats over 150 MB it sends
Chrome into a Loop after a Reinstall although I don't know if this was an
app problem seeing as I was useing Internel SSL certificet Between my
android cellphone and chrome.
6.I get all the sites to work just fine In firefox, IE, Opra, and Deadfuly
enuff the AOL Browser (I found it on one of my backup Hard Drive). It seems
to be with almost anysite that using HTTPS or SSL
@alen.siljak: sad to say it but it worked. by Deleting the txt file after
Chrome closes fixed the problem
Odd part is the txt file only had the numbers 1434 nothing ells in the
chrome_shutdown_ms.txt file at all
I have this issue too. I reset windows7 64 to an earlier time, Chrome
opened google sites fine for a few hours before the bug resurfaced. As with
others, IE Firefox etc work fine.
happened to me as well it wouldnt even let me go to the google support page
1. windows 7
2. google chrome 18.o.1025.151
3. invalid server certificate you attempted to reach www.google.com but the
server presented an invalid certificate. you cannot proceed because the
website operator has requested heightened security for this domain
4. the identity of this website could not be verified, Server Certificate
can not be checked, Server Certificate is invalid, the Server Certificate
contains a weak cryptographic key
5. modules (98) no conflicts detected
6. looked but cannot see a file named chrome_shutdown_ms.txt
Everyone: In order to assist in resolving this, please attach your
chrome://conflicts, as described in 3a from comment 53 -
http://code.google.com/p/chromium/issues/detail?id=118706#c53
This is vital to be able to determine commonalities between the systems of
affected users.
cflannigan/comment #92/93: Your issue is completely different than this
one. Please star http://code.google.com/p/chromium/issues/detail?id=122500
/ Issue 122500 for your issues with penfed.org.
Please explain how to get to chrome conflicts to report/paste issues
Google Chrome: 18.0.1025.151 (Official Build 130497)
OS: Windows 7 Ultimate x64
WebKit: 535.19 (@113052)
JavaScript: V8 3.8.9.16
Flash: 11,2,202,229
Removing txt file helps.
I actually used the batch uploaded by alen.siljak, and I'd like to thank
him for that. I'm 80% satisfied on how that works...I recommend using that
solution until a real one comes out.
Attachments:
conflicts.htm 258 KB
just upgrade chrome from V 17 to 18 and got the same errors for goole.com &
Gmail.
chrome - V 18.0.1025.151 m
W7 Ent. 64 bit.
Attachments:
81983ee9-5d64-48e2-8579-a27405428a5a 703 KB
About Version.htm 7.9 KB
conflicts.htm 198 KB
chrome-google_8-4-2012.cer 688 bytes
I encountered this a few days ago and would just like to point a few things
out:
-For users with this issue, it is impossible to comment on this thread
using Chrome
-Once you switch to another browser, it is impossible to comment on this
thread without a Google account
-Even if you switch browsers and have a Google account, you quickly assess
that you are being asked to put in, say, 30 minutes, reading this thread
and figuring out how to provide helpful information
-Meanwhile, EVEN if you do all this, you are going to spend the entire time
this issue is unresolved trying to figure out how to make Firefox and/or
Internet Explorer become the browser you are most comfortable with. Do you
realize how indifferent many people are between browsers? For many people,
this sort of thing is easier than figuring out how to provide the conflicts
info!
I can't tell you what percentage of Chrome users are on Windows 7 or what
percentage of them are afflicted by this bug, but it is dramatically higher
than the number of people who find this thread and comment on it. I can
tell you that every single one of us with this bug is FORCED to use your
competitor's product; anybody who has this bug, and who possibly could be
swayed to like Firefox or Internet Explorer as much as Chrome (or almost as
much, but feel comfortable that at least they won't have to worry about
this kind of bug), WILL be swayed. As this bug stays open, more and more of
us who have found this bug but not bothered to comment will lose interest
in checking this thread for a solution.
rsleevi, do a quick assessment on the number of Windows 7 Chrome users. If
you can measure it, look at how their use has changed recently; if you
can't, be pessimistic. If this is an important number of users to you,
rsleevi, do not try to fix this issue on your own; escalate this to the
highest priority you can and get a team on it
us who have found this thread but not bothered to comment will even lose
Do a quick assessment on the number of Windows 7 Chrome users. If you can
measure it, look at how their use has changed recently; if you can't, be
pessimistic. If this is an important number of users to you, you should
escalate this issue to the highest priority you can
escalate this issue to the highest priority you can. You also might worry
that posting a solution in this thread isn't going to be a message that
reaches everyone this bug hit, and if this solution is anything more
difficult than download the newest version of Chrome, many of us won't
bother
I've started getting "The site's security certificate is not trusted!" for
https://twitter.com , but only when using chrome.
Chromes : vsn 18.0.1025.151 m
OS :Windows XP service pack 3.
chrome://conflicts reports : Modules (157) - No conflicts detected
it was working yesterday, and the site works fine in firefox.
With IE I get :
The security certificate presented by this website was not issued by a
trusted certificate authority.
but at least with IE I get the option to continue on to the site.
so it must be something to do with the certificate issued to twitter.com
I attache an export of the certificate.
other https sites DO seem to work including gmail , my work connection,
facebook
I cannot find the chrome_shutdown_ms.txt file anywhere.
is there anyway to check what version of Google chrome I was running
yesterday ?
Attachments:
twitter.cer 2.3 KB
One extra comment I just tried to login to my Lloyds bank online account
https://www.golloyds.com/index/en
and I get the same error :
The site's security certificate is not trusted!
BUT, for this site I get :
You should not proceed, especially if you have never seen this warning
before for this site.
with two buttons :
'Proceed anyway' 'Back to safety'
and I see the same issue with IE : 'the certificate is not valid', but it
lets you proceed to the site successfully.
Also get the same the for Lonely Planet thorn tree website:
https://secure.lonelyplanet.com
certificate attached.
At least with these 2 sites the you can get around the error, but with
twitter.com you are not able to proceed further.
Attachments:
lloyds.cer 1.9 KB
thorntree.cer 1.2 KB
I don't understand how these forums work. This morning on here:
http://groups.google.com/a/googleproductforums.com/forum/#!msg/chrome/1alZsHEeprc/fCeAmA9WOrQJ
someone explained a workaround. But now the latest posts on that thread
have disappeared. The workaround is as follows. Open chrome, then close it
using the tab on the upper left, NOT the browser x on the upper right. Then
reopen it. When I tried this, several times, then the bug went away. But of
course it is not gone, just lurking. Where are all the chrome techs, eating
blood of the lamb?
Google Chrome 18.0.1025.151 (Official Build 130497) m
OS Windows
WebKit 535.19 (@113052)
JavaScript V8 3.8.9.16
Flash 11,2,202,229
User Agent Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML,
like Gecko) Chrome/18.0.1025.151 Safari/535.19
Command Line "C:\Users\The Belanger
Family\AppData\Local\Google\Chrome\Application\chrome.exe"
--flag-switches-begin --flag-switches-end
Executable Path C:\Users\The Belanger
Family\AppData\Local\Google\Chrome\Application\chrome.exe
Profile Path C:\Users\The Belanger Family\AppData\Local\Google\Chrome\User
Data\Default
Windows 7 Home Premium Build 7600, 64-bit.
chrome://conflicts show no conflicts.
Removing chrome_shutdown_ms.txt works initially, but on shutdown/restart,
the issue re-appears.
PS - to all of you people crapping on Google for this issue - can I ask how
much you paid for this product? Oh, you got it for free. I see. How much
are you paying the G team to troubleshoot this issue over a holiday
weekend? Oh, nothing again? I see. So please quit your complaining about a
bug in a free product that is also being supported for free. I'm using
Firefox for the duration of this bug, and when it's resolved, I'll switch
back to the Chrome that I love and adore. First world problems, right? Go
bite the ears off a few chocolate bunnies to make yourself feel better.
Attachments:
conflicts.htm 243 KB
My browser fixed itself I guess. For some reason I am not having this issue
anymore.
@1900geek: Which version of Chrome are you running?
Comment # 123 by dmitry.m is an incredibly simple fix and it does work for
me. Thanks
What happens with #123 could be another bug in Chrome. :)
When the last window is closed the ms file is not created in the user's
profile directory. Hence starting Chrome the next time works OK.
Which is the same as if you delete the file prior to starting the browser.
I can confirm that Comment 123 resolves the issue for me as well
Control - W worked for me too.
I had had this problem off and on very infrequently since the end of 2011.
Earlier it was just a matter of closing, rebooting, reopening, etc.
Since April 6th, the problem was intractable except for the
chrome_shutdown_ms.txt fix. Now the Control - W fix works.
What is really going on here?
Deleting "chrome_shutdown_ms.txt" after shutting down Chrome nor shutting
down with Ctrl+W doesn't fix the problem for me, I still can't
found "Proceed anyway" button when I open Twitter.
Currently I'm switching to Opera until this problem resolved.
Google Chrome 18.0.1025.151 m
Windows XP Professional SP3
IE / Firefox / Opera : no problem opening twitter, no warning appeared
about rejected certificate
Attachments:
certificate-no-proceed.jpg 47.4 KB
Another way to solve the problem, although temporarily (each time you close
it you have do repeat the setp), is one posted on other forum:
1. Open Task Manager
2. Select each Chrome.exe process and end it until Chrome closes
3. Open Chrome once again, it shows the message of restore last session,
clic on restore and pages open normally.
Google Chrome 18.0.1025.151 m
Windows 7 Home 64 bit
99 Modules no conflicts detected
Cannot find chrome_shutdown_ms.txt in user data or anywhere else
Ctrl+w does not do anything
Attachments:
conflicts.htm 224 KB
Hi there.
I am having the same problem. It started 06 APR 2012 and It's just with
Chrome. I am now using chrome after deleting the _ms.txt file each time
before I open. Thanks to you all guys who are working on solving this
problem. As far as I know a lot of ppl are issuing this and not many of
them aren't competent enough to look for solving it in google or anywhere.
They just prioritize IE or Mozilla to be their main internet browser.
Whatever... I'm posting all the info for my issue:
- Machine: HP Pavillion Dv6-3010US
- OS: 64bit Win 7 Home Premium
- Chrome version: 18.0.1025.151 m
- Chrome://conflicts - NO CONFLICTS (attachment with screenshots below
- deleting the chrome_shutdown_ms.txt - WORKS
- closing with Ctrl+W - WORKS
If you need any additional information I will provide it.
Attachments:
chrome bug.rar 774 KB
Comment #141 on issue 118706 by kar...@google.com: HTTPS/Certificate
websites always have "Invalid Server Certificate" Error
http://code.google.com/p/chromium/issues/detail?id=118706
(No comment was entered for this change.)
(No comment was entered for this change.)
Attachments:
chrome gpu.htm 72.8 KB
@ram...
I also have many CAPI2 errors in the event viewer.
My corporate security policy does not allow me to do updates.
I tried getting the authrootstl.cab file and installing it manually per MS'
instructions, but that had no effect.
J.Cl... (and everyone who has commented so far): Was this record from
chrome://gpu before or after you deleted the text file?
Sorry, it completely slipped my mind to indicate both states; a
chrome://gpu log when the error happens (eg: chrome_shutdown_ms.txt is
present) and a chrome://gpu log when the error is "fixed" (eg:
chrome_shutdown_ms.txt isn't created / is manually deleted)
If it would help, I can abstain from installing SP1 for the moment to do
some more prodding if needed.
J.Cl...: At the risk of punishing the helpful users, it would be rather
helpful if you could abstain, just so we have a control.
I've spent quite a bit of time this past week/weekend/day trying to
synthesize the failure, based on the information coming from
chrome://conflicts and chrome://gpu, and have been unable to do so
successfully so far. Having one or two controls will help us resolve this
issue much quicker.
That said, once this issue is resolved, you definitely should consider
upgrading to SP1. Lots of quality security fixes in there from Microsoft
that you wouldn't want to be without =)
Thank you, update worked for me.
I'm good after update...thanks.
@rsleevi: will the update be pushed to the dev branch as well? I'm on 19.0
and having the same issue.
netman85am: We're currently looking at a different fix for the Dev branch,
so I can't give a concrete ETA.
One thing that would be helpful would be trying the current Google Chrome
Canary ( http://tools.google.com/dlpage/chromesxs ). This can run
side-by-side with your existing (Stable/Beta/Dev) version, with a
completely separate profile and settings. If you were to install the canary
right now, you will likely find the issue exists there as well. However, as
soon as the next canary is released (typically, nightly), you should
hopefully find the issue resolved, without regressing Issue 117371.
If you (or anyone else currently running Dev) would give that a try, we'd
love to hear your results and if you still continue to see the issue over
the next day or two.
@rsleevi
Just installed canary 20.0.1096.1 and have no issues so far. Will keep you
updated if it reappears in canary.
c186: Note, because Canary operates with a separate profile directory, you
will need to exit and relaunch Chrome at least one (so that
chrome_shutdown_ms.txt is created). Note that you will need to do the
/opposite/ of the previous workaround, which is, make sure you close it via
the red x in the top-right corner of the window, and NOT by pressing
Control-W.
Certainly though, if you have any issues, please let us know.
Right. So far still happening, will let you know if next update fixes.
I'm working fine again after update to 152....thanks guys !
18.0.1025.152 did NOT fix the issue. Exact same SSL message still appear.
I'm on Windows XP.
In reply to #149
http://code.google.com/p/chromium/issues/detail?id=118706#c149
Unrelated to topic but your Windows product key is visible in that
screenshot. Just thought I'll have you know...
I just updated and the issue appears to be resolved for me as well.
Thank you for all your hard work Chrome Team!
alen: If you can hold out a little bit longer, that'd be great.
My tentative fix just missed the cut-off window for the latest Dev.
However, if you try the canary version (See comment #185), you shouldn't
see the problem (after restarting Chrome appropriately to ensure
chrome_shutdown_ms.txt is created)