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.
Related
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 1 year ago.
Improve this question
I have a few websites, and everything was running perfectly for the past months, but all of a sudden, they don't work anymore on Chrome for computers with Windows 7.
It works fine on Mozilla for these computers, and on all browsers with Windows version higher than 7.
Up at this point I've tried different solutions found online in articles like this:
https://kinsta.com/knowledgebase/net-err_cert_date_invalid/
But nothing seems to work. On these computers, there are websites (other than mine) that have the same issue. The only common thing between these computers is the Windows version and the browser used.
If it helps, here is one of the websites https://suplimentenaturiste.ro/
I am thinking there must be an issue with the SSL itself, that was generated using Let's Encrypt.
Maybe here can help you.
https://support.google.com/chrome/thread/128686072/net-err-cert-date-invalid-error
From this answer :
If you're on Win7 SP1 x64, try installing this update ("Support for urgent Trusted Root updates for Windows Root Certificate Program in Windows") - this worked for me:
https://www.microsoft.com/en-us/download/details.aspx?id=45633
I have the same problem, but this answer can fix it my problem!
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.
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
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
When I open Google Chrome I constantly get the error "A PROFILE ERROR OCCURRED: Something went wrong when opening your profile. Some features may be unavailable". Further, when I close Chrome, it will then refuse to open again unless I log out and log back in. This problem has survived logging out and back in to Chrome, uninstalling and reinstalling, and persists even if I am signed out of my Google account. This is occurring on my desktop PC but does not occur on my work PC, and so appears to be a problem with chrome on my PC.
Please help!
Try deleting the file "web data" in :
C:/Users/Username/AppData/Local/Google/Chrome/UserData/Default
And if it doesn't work then also "Local State" File in:
C:/Users/Username/AppData/Local/Google/Chrome/UserData
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.