Plugins Not Connecting with Keepasshttp #20
Comments
|
Have you installed new security, scanning, filtering or proxy software? Others have experienced problems with misconfiguration or blocking when they've been installed. johantheolive reply@reply.github.com wrote: For some time I had no problem, then all of a sudden within the past week or so I can't get it to work. I use Chrome+Chromeipass (see below) or Firefox+keefox and both worked fine, but now neither of them seem to connect with the plugin. I've tried redownloading the plugin, reinstalled keepass, deleted the entry in keepass for the associations but nothing seems to work. The message Chromeipass gives me is: Thanks! Reply to this email directly or view it on GitHub: |
|
I've been running avast + comodo for months without a problem but i had tried disabling both yesterday and still couldn't get it to work. |
|
Forgot to mention that I tried using the portable version of passkey with passkeyhttp and the same database I always use. That didn't work either. I've also tried removing and reinstalling the chrome and Firefox plugins. Also tried a different Firefox plugin all to no avail. |
|
Does KeePassHttp still show up in the KeePass plugin list? johantheolive reply@reply.github.com wrote: Forgot to mention that I tried using the portable version of passkey with passkeyhttp and the same database I always use. That didn't work either. I've also tried removing and reinstalling the chrome and Firefox plugins. Also tried a different Firefox plugin all to no avail. Reply to this email directly or view it on GitHub: |
|
I had copied keepasshttp into the directory for keepass. It did show in the plugin list although it didn't have the rpc plugin that the full keepass shows. |
|
I don't know about the rpc plugin since that isn't mine, but if keepasshttp shows up in the list then it should connect fine. In chrome go to chrome://extensions click developer mode and click on the background page for chromeipass, there you'll see a console for it. You might be able to find more info there. johantheolive reply@reply.github.com wrote: I had copied keepasshttp into the directory for keepass. It did show in the plugin list although it didn't have the rpc plugin that the full keepass shows. Reply to this email directly or view it on GitHub: |
|
Appreciate your help. I've got the console open, and when I hit the button to reconnect to keypass I get: KeePassHttp: Error: NETWORK_ERR: XMLHttpRequest Exception 101 |
|
I just reinstalled Keefox and it's now working with Firefox. Seems to be a problem with chromeipass/chrome? |
|
I encountered a similar issue this morning that I was able to resolve. I believe it boils down to a mono library that got hung up. The simplest resolution would be to reboot the computer but I'll do my best to detail my observations in case they're useful to others. I have KeePass2 version 2.16 that I installed from the following repository: http://ppa.launchpad.net/jtaylor/keepass/ubuntu. I'm running on a Ubuntu platform with KDE. This morning I noticed that KeePass had closed by itself, presumably having crashed. I've also seen numerous crashes of Nepomuk recently, which may or may not be related. When I restarted KeePass I got a popup message alerting me that I had a plugin that was incompatible with the current version of KeePass. I thought that was odd since I hadn't updated KeePass since I installed it a week or so ago. I also noticed that the popup message referenced a cached plugin rather than identifying the plugin's installation folder or name. I tried to delete the cached plugin but it recreated the same folder and produced the same error message when I restarted KeePass. I then noticed that a new version was available from the repository. Hoping that new version would fix the problem I installed it. No luck there. Same error message on starting KeePass. I then tried to roll back by forcing the version through Synaptic Package Manager. No luck there. Same error. Next step was to check to see if KeePass was still running as a process. I didn't initially find it because KeePass somehow runs through mono. It shows in KDE as a kwin application, which wasn't very helpful. I was eventually able to find it running as a subprocess of "cli". In fact there were two "cli" processes, one of which did not close out when I shut down KeePass. I terminated the remaining "cli" process and was then able to start KeePass properly. I confirmed it was running first by checking for it in KeePass under the tools>plugins menu. Second confirmation was that I was able to add a new login to KeePass from Firefox (I registered for github) I hope this information is helpful for anyone who might be trying to resolve a similar issue. Derek Cooper |
|
@johan what happens if you go to http://localhost:19455 in chrome? |
|
@pfn Chrome can't find the page. Same happens with Firefox, although it times out the connection. Granted, Firefox is still able to access my keepass entries. tI just Tried disabling avast and comodo but still can't find the page. |
|
If it is unable to connect, you either have bad proxy settings, security software or keepasshttp is not installed PS, keefox is unrelated to passifox and chromeipass. johantheolive reply@reply.github.com wrote: @pfn Chrome can't find the page. Same happens with Firefox, although it times out the connection. Granted, Firefox is still able to access my keepass entries. Reply to this email directly or view it on GitHub: |
|
@pfn So I've uninstalled comodo and avast. Disabled windows firewall. Right now running windows with minimal startup items. Removed keepassrpc plugin. I still can't get it to work. I copied my keepass database to another computer and was able to get an association request from passifox on there. And I don't use a proxy. |
|
Is the KeePassHttp plugin in the keepass list on the machine that doesn't work? ----- Original Message ----- @pfn So I've uninstalled comodo and avast. Disabled windows firewall. Right now running windows with minimal startup items. Removed keepassrpc plugin. I still can't get it to work. I copied my keepass database to another computer and was able to get an association request from passifox on there. Reply to this email directly or view it on GitHub: |
|
Yes. I'm pouring over the running services and killing anything that aren't standard windows stuff and still not getting anywhere. |
|
So when you start KeePass you are able to see KeePassHttp in the plugin list? Then you should be able to go to http://localhost:19455 just fine from Chrome or any browser at all, IE, Safari, Firefox -- are you able to do so in any browser? You can also try to do telnet localhost 19455 from a command prompt (assuming you have telnet installed, win7 doesn't seem to include it by default). It should connect successfully ----- Original Message ----- Yes. I'm pouring over the running services and killing anything that aren't standard windows stuff and still not getting anywhere. Reply to this email directly or view it on GitHub: |
|
Wow I just figured it out. My hosts file no longer had 127.0.0.1 associated with localhost in it. Talk about lame. Thanks for all your help. I figured it was something stupid. |
|
Wow, that was an annoying find... what removed localhost? ----- Original Message ----- Wow I just figured it out. My hosts file no longer had 127.0.0.1 associated with localhost in it. Talk about lame. Reply to this email directly or view it on GitHub: |
|
Not sure, but I'd like to wring it's neck out |
For some time I had no problem, then all of a sudden within the past week or so I can't get it to work. I use Chrome+Chromeipass (see below) or Firefox+keefox and both worked fine, but now neither of them seem to connect with the plugin. I've tried redownloading the plugin, reinstalled keepass, deleted the entry in keepass for the associations but nothing seems to work.
Is there anything else I can try or a log somewhere that has some information?
The message Chromeipass gives me is:
"ChromeIPass has been disconnected from KeePassHttp.Is KeePassHttp installed and/or is KeePass running? Press the reconnect button to establish a new connection."
Of course, pressing reconnect doesn't help.
Thanks!
The text was updated successfully, but these errors were encountered: