Chrome KeePass: " Something went wrong" about chromekeepass HOT 15 CLOSED

I assume you've checked if KeePassHttp is installed and you're connecting to the correct port?

You could you try this:

• Put your browser into developer mode (chrome://extensions -> "developermode" toggle at the top)
• Open the "backgroundpage" for ChromeKeePass
• Try to connect CKP again
• Check the "Network" tab of the backgroundpage
• The request to http://localhost:19455/ could shows some additional information
• If you want you could "Export to HAR" (last icon below the tabbar) and share it here

from chromekeepass.

I am having the same message in Edge. However in Chrome the addon is connecting just fine.
What du you mean by "backgroundpage"? If I open the DevTools for the Plugin under Network it shows me this:

Also I am not sure what you mean with "export to HAR". Where do I find this?

from chromekeepass.

@SAMUD
That's the correct DevTools. This is the export icon:

What version of Edge are you on? I don't have any issue on version 124.0.2478.80.

from chromekeepass.

I'm on 124.0.2478.80 too....

Here is the HAR:

jnhjknbfnclancjpknceboifoegiompf.zip

from chromekeepass.

@SAMUD
Thanks you for the file.

It seems that something or some setting forces ChromeKeePass to use HTTPS. KeePassHttp doesn't support HTTPS, it sends encrypted data over HTTP.
Do you maybe have another extension installed that forces websites to use HTTPS?

from chromekeepass.

@SAMUD
Can you check open this page in Edge edge://net-internals/#hsts and see if localhost is listed there? That could cause the issue.

from chromekeepass.

I have the same problem, and I just did low level troubleshooting with WireShark, and it was indeed trying to do a TLSv1 handshake before. And this only worked on ONE profile (my other profile was fine).

localhost was indeed found in the hsts/pkp domains, and after deleting it (I didn't think to record the result of the query though), it started working again!

I believe this all was a result of Visual Studio running a site on https://localhost/

from chromekeepass.

@gschizas Thank you for letting us know.
I'm going to assume it's the same for the others here and close this issue.

from chromekeepass.

I was just thinking. Changing the "Hostname / IP address" in the ChomeKeePass settings to 127.0.0.1 will probably also resolve this issue.

from chromekeepass.

@RoelVB there is nothing listed in edge://net-internals/#hsts

I have multiple softwares installed which runs websites on localhost (thanks Siemens...) and uses https.

I fixed it by switching to 127.0.0.1...

Thanks for your help!

from chromekeepass.

@SAMUD, you need to go to the "Query HSTS/PKP domain" section, type "localhost" and press "Query"

from chromekeepass.

@gschizas i dont want to delete the entry. Siemens stuff is sometimes very picky... And I don't want to break it. So changing to 127... ist the easier method :)

from chromekeepass.

@SAMUD you don't need to delete the entry, I just said to press "query", to provide info for this bug.

In any case, this won't stop any program from running on localhost. This setting is that Edge (specifically) auto redirects http://localhost to https://localhost. Your Siemens stuff will probably be fine.

from chromekeepass.

@gschizas

from chromekeepass.

Yeap, this looks like what I saw. I think you'll be ok to delete this; this is not only Edge specific, it's specific to the profile of Edge you're using. But if you got a different workaround, that's ok too. The point is that we found the cause of the error, and it was the same, and it was correctly closed.

from chromekeepass.