Your connection is not private (Google Chrome 57.0.2987.133) [closed] - google-chrome

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I am using google chrome Version 57.0.2987.133 on windows 7 pro 32-bit and after that every tab is showing this message "Your connection is not private". I believe after update into latest release its stop working. Any guidance

In order to resolve this problem, firstly, you need to test the range of this error by using another browser, such as Firefox and load the same website. If you get a similar error message, which is: Your connection is not secure, then definitely something was wrong with your computer, not from Google Chrome.
However, if the problem is only come from Google Chrome, then you can start to diagnose and troubleshoot.
Solution #1: Clean up all cookies and cached files on your browser.
Solution #2: You can add "--ignore-certificate-errors" in the
shortcut of Google Chrome to turn off this annoying warning. This is
for temporary, not real solution to fix it.
Besides, you should also check again your date and time to make sure those settings are correct.
In case this error is appeared in both Google Chrome and Firefox (or any other web browsers), then you should take a look at your antivirus software. A feature called SSL scanning or something similar would be the cause of it.
After trying those solutions but still getting this error, I would recommend using CCleaner to uninstall Google Chrome completely and then download it again into your computer. This will help you to remove all outdated & invalid settings of Google Chrome out of your computer, which could lead to this error. However, make sure to use Google Chrome Sync to backup your sensitive data first (saved passwords).
Source: Fix Your Connection Is Not Private Error In Google Chrome

Related

FTP link to PDF not downloading [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
Within my companies Intranet, we have FTP links to certain files. This morning, a few of my PCs stopped downloading the files and instead prompted me to open them with IE (I was using Chrome). The versions of Chrome on each PC are updated to the most recent (Version 87.0.4280.66). I changed the default app for opening FTP files to Chrome, which only alleviated the IE message, but still refuses to download. I have compared settings with a few PCs that are working as intended and cannot find a difference that would cause this. Is there perhaps something I am overlooking? How can I fix this issue?
FTP support in Chrome is deprecated.
The current FTP implementation in Google Chrome has no support for
encrypted connections (FTPS), nor proxies. Usage of FTP in the browser
is sufficiently low that it is no longer viable to invest in improving
the existing FTP client. In addition more capable FTP clients are
available on all affected platforms.
It is disabled by default in Chrome 87.
It will be removed completely in Chrome 88.

Why does Google say I need chrome to use my Yubico security key? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
Not sure if this is the right place to ask, but here goes.
When I'm trying to sign into google, and it asks for my security key, it says that it can only be used in Chrome. This is a problem because my school only has internet explorer on the computers (bad, I know) and this makes it more annoying to sign in.
Is there a workaround, and does anyone know why this is?
(p.s. I have tried to find some info about this but nothing explains why it needs chrome, especially since when I trigger the key in microsoft word all it does it print some text)
Yubico Security Key is a very new technology. Microssoft will support Yubico Security in Windows 10. But Internet explorer was discontinued in January 21, 2015. So any of the new technologies released after that is not supported. I am afraid there is no work around at the moment.
So which browsers support U2F?
You must be running Google Chrome version 38 or later, or Opera version 40 or later. Both browsers include support for the U2F protocol.
Firefox Quantum now natively supports U2F. FIDO U2F is not turned on by default in the Firefox browser.To see how to turn it on check the link1 below.
But there is a workaround. For now, you can use backup codes from Google Authenticator or Yubico Authenticator, for two-factor authentication if your browser doesn’t support U2F. You need to install an Android application or Desktop which will generate an one time password for you to use in IE. Check link2.
link1: https://support.yubico.com/support/solutions/articles/15000006417-getting-started-with-your-yubikey
link2: https://support.yubico.com/support/solutions/articles/15000006419

Google Chrome losing cookies after Ubuntu reboot [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
From few days I am experiencing weird issue. When I reboot system or even relogin, then I am logged out on sites on which I was logged or clicked 'remember me'. Problem appears only in Google Chrome (Firefox and opera are working well), for example:
log in to stackoverflow
log out from system
log in to system
unlogged on stackoverflow!
I do not know when exactly problem appeared, remember I was executing localStorage.clear(); in console, but I think it should not be connected with this.
I am using latest Ubuntu 16.04, latest Chrome 53.0.2785.101 (64-bit). I also tried reinstalling and using different versions like google-chrome-beta, google-chrome-unstable but without effects.
What can be the problem causing this?
Edit: I asked this question on StackOverflow, because I thought it may be related with localStorage.clear()
Fianlly fixed in 53.0.2785.143: https://chromium.googlesource.com/chromium/src.git/+/fc6f304827896fb27397fc2a27f9f5717eff319c
Exactly same issue since last few days running Chrome 53.0.2785.101 (64-bit) on Centos 7. Since I don't log out from centos I can open and close chrome ad It will keep reading cookies saved but when I logout, at the next login it can't read cookies at all. Uninstalling e completely removing personal chrome settings directory (/home/myuser/.config/google-chrome/ )didn't solve.
I made another test: saved new cookies in a chrome session, closed the browser, moved away the file /home/myuser/.config/google-chrome/Default/Cookies, opened again the browser and, as expected, it couldn't find previously saved cookies. After restoring the file in its original path, chrome read the saved cookies again. After logoff-logon from Centos, no cookies again, but the file is still there and unchanged.

Manage exceptions for camera and microphone in Chrome [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am trying to make an exception for a site to access my microphone and camera:
chrome://settings/contentExceptions#media-stream is not editable, is it normal?
How do I add a rule?
It's not possible as you would expect. Reported as a bug here and closed as Status: WontFix. Details below.
#14 freshst...#renuval.com Version: Version 28.0.1500.95 m OS: Windows 7 64 bit
We've read on an earlier Issue from 2011 that it's intended behavior
as well, but some people on the same Issue weren't sure:
https://code.google.com/p/chromium/issues/detail?id=71179
Chrome Help sites discuss the topic here:
https://support.google.com/chrome/answer/2693767?hl=en
Note that the Media Exceptions page doesn't explicitly say that you
can add exceptions, it only says you can deny. It does, however, point
you to the Manage Exceptions page on this topic which does say that
you can add using a button. This looks like it's just unintentionally
misleading.
After re-reading everything carefully, we assumed based on the help
article that the only way to de facto allow an exception is to click
"Allow" on a site requesting an exception that is running on HTTPS
as Chrome will only remember your preference for Media Exceptions on
HTTPS sites. It seems a bit restrictive for users who are savvy enough
to edit their own security settings deep down in the menu tree, but
security is security.
#15 ser...#chromium.org
Thank you freshstart. This is exactly it. Https
means that "allow" can stick.
Your question was also already answered on Super User:
You add a rule by going to the site in question and then, if Media
setting is "Ask when a site wants to use a plug-in to access your
computer", it should prompt you for what to do - that will then get
set as a specific exception.
You only use Manage Exceptions to remove existing exceptions.
See
Allow sites to access your camera and microphone and Manage
exceptions
Another Stack Overflow answer had a workaround, but it reportedly does not work any more. Via How to allow Chrome to access my camera on localhost?.

How to fix "Google Chrome did not shutdown properly" in Windows 8.1 [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
When shutting down Windows 8.1, Google Chrome produces the error message "Google Chrome did not shutdown properly". How can I get Chrome to shut down without giving me that error message?
I don't have to be logged in as a Google user.
There is another alternative, you just need to go to:
Settings
Advanced Settings
System
And uncheck the Continue running background apps when Google Chrome is closed option.
For now that is the best solution I have found that does not require you to delete your profile.
Received this error and found that the %LOCALAPPDATA%\Google\Chrome\User Data\Default\Preferences file had the System, Hidden and Read-only bits set. Used attrib to remove them. The first opening of Google Chrome after stated the same message, but subsequent opening the issue was resolved.
On this system, it appears to have been caused by the installation of the Audible Manager from Audible.com.
In the section Users there is an option to "Delete this user", click the button, confirm that you want to delete the user and presto, Chrome stops producing the error message when you start it.
This is a fix for people who wants to use the browser without a user profile. As a little note I have noticed that Chrome seems to be slightly slower booting, but for me it's well worth it to get rid of the error message.