I have already logged into the windows 10 office app. And when I try to access office.com via the browser (Edge) I am already logged in (which is good). However, when I tried to do the same in Chrome, then I have to re-enter my credentials. I tried to change the default browser to Chrome and re-logged into the windows office app and still, Chrome is not automatically logging me in.
Additionally, I installed this chrome plugin which was offered by Microsoft. But still not working.
https://chrome.google.com/webstore/detail/windows-accounts/ppnbnpeolgkicgegkbkbjmhlideopiji
Does anyone encounter this problem and resolve it?
Related
I am trying to access a site that requires an SSL key. I am using Chrome (latest) on Mac OSX 10.14.4.
Browsing the site I get the following error:
This site can’t provide a secure connection site.com didn’t accept
your login certificate, or one may not have been provided. Try
contacting the system admin.
ERR_BAD_SSL_CLIENT_AUTH_CERT
I can access the site on Safari, Firefox, and Chrome for Windows (using a VM). It is only Chrome for Mac that gives me an error.
When I access the SSL keys in the Chrome Preferences, I am taken to the OSX Keychain app.
The key exists in the keychain, and the permissions are set to allow use from any app (I have also tried setting this to manual and specifically setting allow with Chrome).
When I browse to the site in chrome, I am asked to pick the SSL key to use - the key is detected and I select it from the list (it is the only one available anyway).
I am completely out of ideas. Any thoughts on what I can do to fix this?
I'm running Google Chrome on Windows 10, latest editions. Chrome refuses to open any pages, returning "Aw snap" error messages. To resolve this I've:
Removed all extensions.
Uninstalled and reinstalled Chrome.
Tried Chrome on a different user.
Ran Chrome Cleanup Tool.
Deleted my Google folder in Appdata.
Incognito pages don't work either.
None of these worked. Firefox at all times is working perfectly so its not an internet problem.
Anyone have any ideas on how to fix this?
Please follow below steps, to resolve "Aw snap" error messages with Chrome browser.
Steps To Resolve:
Go to Chrome shortcut in the Desktop (If not exists create one)
Right click -> Properties
In the target field, At the end add a space followed by the below -no-sandbox
Apply-Ok
Launch chrome using the shortcut
Follow the below steps
Go to windows task manager
go to details tab
kill all the chrome process
run the chrome it will open
It is likely that malware is trying (and failing) to modify the page that is loading. I've also seen this as a symptom of machines that had nasty redirect malware removed, as the redirects that the malware creates no longer have anywhere to resolve.
I highly recommend a fresh Windows 10 install, only way to be sure you're fully free of whatever may have infected your current Windows installation.
I have a problem getting a chrome extension to work on Windows 10 Technical Preview. I have this extension hosted in Chrome Web store. However when my i run the .exe on my pc, which is supposed to install a client on the pc and an extension on chrome, i cannot see the extension in the chrome extensions.
But when i use the developer version of chrome, i can see the browser prompting me to accept/disable the extension.
What am i missing here? I am pretty new to chrome plugins. Any suggestion/help would be greatly appreciated.
Thanks
Google Chrome (unfortunately) no longer allows private or local crx files to be installed as extensions. You must host it on the Google Chrome app store. From within the store you can make it private to a specific domain, or limit the app to only those within a Google group (they must use their Google account for access to the install).
Deployment of plugins that work within our intranet has suddenly become a major pain. I'm really surprised they couldn't come up with a better solution for this.
https://support.google.com/chrome/a/answer/2663860?hl=en
I have been having an issue lately with Google Chrome. Some sites, seems to be completely random, are returning a 503 Service Unavailable error message. The last one I received was from my hosting provider when trying to access my CPanel. I can access the same URL completely fine in Firefox or IE. It seems to be isolated to Chrome.
I have tried the following:
Disabled all extensions
Logged in/out of my Google account
Cleared all cache and history
So far, nothing seems to correct the issue. It's becoming more and more aggravating from what was once a pretty reliable browser.
I am running:
Windows 7
Chrome Version 36.0.1985.143 m
I was hitting the same issue. Mostly, it would occur on intranet sites at work, but it happened with a few exterior sites. Loading in IE Tab would work fine.
I was able to solve the issue by upgrading to 64-bit Chrome. I'm not sure why that fixed it, but I think it had something to do with a conflict between Java and Chrome (It looks like I have both 64bit and 32bit Java installed side-by-side).
My solution:
Uninstall Chrome with clear personal data option selected
Install Chrome again but without admin right (install for your personal
user)
Use Chrome as normal
I've got a web site that uses SSL Client certificate authorization.
All client certificates are generated using OpenSSL and are self-signed. Everything worked with all web-browsers, but the recommended one was Google Chrome, because it uses same SSL warehouse as IE, so certificate installation was pretty easy (click-click-password-done!).
After last update of Google "Chrome 29.0.1547.57 m", noone can access my web-server, even me.
Google chrome error only! IE and FF working fine.
Error is: ERR_SSL_CLIENT_AUTH_SIGNATURE_FAILED.
Same in server error log.
Do you have any suggestions?
The problem is that most part of clients are non familiar with PC's and they got very frightened about that situation. So phone support guys are under the wave of calls.
We are experiencing the same problem. As Sean has reported, it seems that Chrome on Windows XP
negotiates TLSv1.2 even though the operating system does not support SHA-2 (say, SHA-256 or SHA-384)
hash function.
We found that Chrome fails when it receives "client certificate request" following SERVER HELLO.
SERVER HELLO itself negotiates RC4-SHA1 (in our environment) which should succeeds. The problematic
packet seems the "client certificate request" that includes SHA-2 (as well as SHA1) functions for hashes.
Invoking Chrome with "--enable-logging --log-level=0" outputs the following message:
ERROR:nss_ssl_util.cc(193)] ERR_SSL_CLIENT_AUTH_SIGNATURE_FAILED: NSS error -12222, OS error -2146893816
This is an Operating system error corresponding "NTE_BAD_ALGID" for CryptSignHash function:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa380280(v=vs.85).aspx
Disabling TLSv1.2 on the server should fix the problem. But I think Chrome should prefer SHA1 on Windows XP.
I'm experiencing the same thing here with Windows7 client systems unable to authenticate with client certificates against some of our systems, but not others. The affected servers are running Apache Tomcat while the unaffected are running IIS7, though I'm hesitant to identify that difference as the culprit.
Anyone else seeing this?
EDIT:
I'm able to eliminate the problem by disabling TLSv1.2 on the server. Is anyone else able to replicate this experience?
I would also be interested to know whether anyone else is seeing this on anything but the Windows platform, as it's the only place it's happening here (same version OSX has no issues).
EDIT2:
Chrome Bug Report here: https://code.google.com/p/chromium/issues/detail?id=278370
EDIT3:
Should be working again in latest Chrome stable. Chrome 30 will have a more robust fix, but 29.x should also work now.
I recently had a similar issue in Chrome on Mac OS. It worked fine with Firefox, but started failing in Chrome and Safari after changing my corporate (AD) credentials -- I guess the issue was a mismatch between system creds and the keychain creds.
The solution for me was a reset of the private key(s) access permissions in the Keychain Access app.
To do the reset:
In Keychain Access app right-click each private key that fails and select "Get Info".
Go to "Access Control" tab and set "Allow all applications to access this item" -- click on that option even if it's already set. Then click Save Changes.
Refresh the website that fails and you should be prompted to enter keychain password -- enter it and select Allow Always.
It is combination of Win XP and Google Chrome 29.0.1547.57 m
On Win 7/8 this problem doesn't occur.
You could install older working version 28.0.1500.95
http://www.filehippo.com/download_google_chrome/15657/
But settings for disabling updating are not so easy.
http://dev.chromium.org/administrators/turning-off-auto-updates
The problem is caused by Chrome running TLSv1.2 on Windows XP.
This can be disabled on the server side but also on the client side.
To run Chrome with a lower version of TLS, start it with the command-line option --ssl-version-max=tls1.1
I had this problem Connecting Chrome with WebSockets to apache throw proxy_wstunnel_module.
My solution was configuring httpd.conf
ProxyPass /wss2/ ws://127.0.0.1:8080/ retry=0 keepalive=On
ProxyPassReverse /wss2/ ws://127.0.0.1:8080/ retry=0
<Location /wss2/>
SSLRequireSSL On
SSLVerifyClient none
SSLVerifyDepth 1
SSLOptions +StdEnvVars +StrictRequire
SSLRenegBufferSize 10486000
</Location>
Chrome WebSockets does not like the parameter SSLVerifyClient optional
I hope this helps.