pfn
chromeipass is unable to connect to keepasshttp
Alright, so to start this off, I am pretty sure I have done absolutely everything right. I am not sure where this is failing.
Steps taken:
- Disable Firewall (Domain, Private, and Public) on Windows Machine
- Configure Keepasshttp to bind to all interfaces
- Configure netsh http urlacl to allow the default Keepasshttp port as explained here
- Configured chromeipass to use a static IP address versus localhost (due to the above being changed)
Below are all the photos I think are relevant:
Proof that Keepass is open:
Keepasshttp Advanced Option (I have also tried setting the private IP address):
netstat -an output (showing that keepass is indeed listening)
Chrome unable to find keepass on the same machine:
Relevant netsh urlacl rule:
Attempt to telnet into ip and port:
At this point, I am not sure what is going on, as it should be publicly available. I use keepasshttp a lot for work (but unfortunately, I have a Mac) so this is why I need to set it to bind to all IPs, however, even if I specify an IP address it still fails to listen and it can't be reached.
Would really appreciate some insight into this, because as far as I am aware, this should be working.
EDIT: If I reset the Keepasshttp advanced option back to default (IE: localhost) the internal connection still fails, and I am unable to access it in Chrome.
EDIT2:
In the below pictures, I blew away my VM and tried again.
Also want to calrify that the connection is received after telnet'ing:
But chromeipass will not connect.
EDIT3: This should be my last edit. Chromeipass does recognize the difference when keepass is not running, and it is. It just appears to not be able to pass the status of the database being open.
Running Versions: Keepass 2.34 Keepasshttp 1.8.4.1 ChromeIpass 2.7.2
Bump, ran into this problem again - and I can't recall what I did to fix it last time. :/
Just an FYI - I just ran into this and it left me scratching my head for a few minutes too. Thing is - the plugin uses the same proxy settings as everything else in Chrome. After doing a quick check, I found I hadn't ticked the "bypass proxy server for local addresses" - which meant that the plugin is trying to connect to the local keepass database via the proxy server - which in my case at least, wasn't ever going to work. Maybe that's what you did to fix it?
I had this same problem and the reason was because all my browsers were redirecting http://localhost:19445 to httpS://localhost:19445. When I deleted "localhost" domain from the HSTS browser cache the connection from the plugin to keepass was restored. (more technical details: the reason to have localhost in hsts was I have local apache and a site using hsts.)
