Hey all,
So - this is happening on my local environment - so i’m not really concerned about it but would appreciate any advice from anyone on the forum as to what causes this so I can make sure I don’t do something that will have a similar outcome on staging/prod.
I’m assuming it might be because the debug mode is ON?
During my login procedure I have no data being outputted so can’t see what would cause this other than debug mode?
Can you take a screenshot of the error?
Could it be that it is expecting an https connection and your local environment os only http?
Hey Brad, heres a screenshot.
I don’t believe it’s HTTPS related, as I have seen this once before on a HTTPS environment created with Wappler, just not on production as I do keep debugging off - so wondered if that was it.
I doubt it is Wappler related. More likely any antivirus/security app that you may have running. Perhaps a chrome plugin you may be using?
That looks like chromes security notification I don’t know much about it but have heard weak passwords can trigger this by default there will be plenty of info on what causes the notification online.
Adding a link to a google support:
https://support.google.com/chrome/thread/23534509?hl=en
I think you might well be right! I just use generic passwords for local - so this might be it. Il use more secure passwords on local to see if it keeps happening
This is just a new thing Chrome has added.
Chrome added a password manager a long time ago where you save username and passwords for sites you visit.
Then few months ago, it added a security check where it would search your passwords against a huge dataset of leaked passwords. So it would give an occaisional warning about password not being secure when in password manager or in Google account.
A week ago or so, with the latest update, Chrome became even more aggressive with this breached password notification.
That’s all. There is nothing wrong with anything. Just a new feature.
For test site passwords, you can safely ignore this.
