The usual procedure will start: but, this time, your login data should be kept where they have to, and you should be able to find them again the next time you'll need to use them. Then, try again to log in to Google, or Facebook, or whatever.
But, at any rate, what you need to rebuild is your 'kwallet.kwl' file.
#Chrome not saving login information password#
Do whatever you like, here: if you usually put a password in there, do it or, leave it blank in order to avoid the hassle of having KWallet ask you for your password every time you open Chrome. Inside the Passwords tab, make sure that the toggle associated with Offer to save passwords is checked. Disable Not Secure Warning Under Chrome Flag Settings. Scroll down to the Mark non-secure origins as non-secure setting and change it to Disable to turn off the Not Secure warnings. Inside the Settings screen, go to the Autofill tab and click on Passwords. Type chrome://flags in the address bar, then press Enter. Then, click on Settings from the newly appeared menu. On start-up, it will activate your KWallet application, which will prompt you for a password in order to store your login secrets privately. Open Google Chrome and click the action button in the top-right corner of the screen.
#Chrome not saving login information full#
So I put in the full URL of " ", and this time Chrome offered to save my password. Then when I reloaded my page, I again got the security error, and noticed the URL address bar had a red flag with https X'd out, and realized maybe Chrome is not saving passwords on insecure https sites. But Chrome never prompted me to save my password.Īfter a couple of days of this, I came and found this site, and after trying other things unsuccessfully, reset my Chrome settings to the default ("Settings" / "Show advanced settings." / "Reset settings").
However, I got a warning from Chrome (Chromium, actually) that warned that the https site was not secure I just went into the Advanced settings and told Chrome to ignore the security warning, and was able to log in. When I first connected, I left off most of the URL, just entering "bowser/admin", which worked (because of sufficiently satisfactory name resolution). We have a local server to which I was trying to connect - " ".