It seems to happen most often if KeePass exits then restarts without Firefox restarting.
When KeePass starts, the OFF icon will change from red to amber, so the plugin knows that KeePass is running, it just can’t tell that the database is unlocked.
Closing Firefox completely and reopening will usually clear the problem. I have also found that disabling/enabling the plugin will sometimes clear the problem without having to close Firefox.
Firefox 57.0.2 (64bit)
Kee doesn’t work, just showing “OFF” logo and message “You are not logged in to your password database”, but I am logged. KeePass enabled, connection between keepass and kee established.
Firefox: 57.0 (64 bit)
since the upgrade to the newest firefox (57) my kee / keefox is not working. Keepass is startet and the database is loaded. Now I get a big red OFF with the message, that I didn’t opened a database.
My System: Windows 10 64Bit, Firefox 57
There was nothing in my troubleshooting guide (v2.38) about this issue I checked. Issue remains kee reports “Big Red OFF” despite being logged into keepass Any assistance with this would be appreciated.
And even though I read all the troubleshooting tips which mention to whitelist things in other addons, which I did in every possible addon I have.
Whitelisting it in the outdated RequestPolicy wouldnt help at all .
Installing “RequestPolicy Continued” (https://addons.mozilla.org/en-US/firefox/addon/requestpolicy-continued/) would simply resolve the issue.
Think the new RequestPolicy did read the whitelisted items from the old version, so whitelisting might also be needed.
(Whitelist: Allow 127.0.0.1:12546)
Anyways I first had to find out if its actually addon causing this, and if yes then which one.
Good way (IMO) seems to be simply disabling all addons and trying Kee.
If it works, enable some of your disabled addons and check again. If it works, enable more and check again, until it stops working, then you have much narrower choice of problematic addons.
If it doesnt work with addons disabled, its most definitely not an addon causing it.
I know those are pretty basic troubleshooting steps, but maybe it would be nice to mention such way in troubleshooting info.
I can see you guys here seem to all have Firefox 57.x so you might have another issue and this might be completely useless.
But thought I throw this out there, especially because RequestPolicy is mentioned in troubleshooting along with what to do, yet I still stumbled into such situation, which might make you first assume that RequestPolicy is not at fault after whitelisting. ( surprise, surprise xD )
I’m using Kee on Windows 10 with Comodo Internet Security Premium 10. I’ve had a number of issues using Kee to access a different password database within the Virtual Desktop sandbox. As a result I now run two separate instances: one a normal installation and one a portable version for use in the sandbox.
But when there is an upgrade, despite carefully clearing the sandbox, updating both versions and checking that all the ports are correct, I still sometimes encounter this red OFF logo problem. When all else fails to clear it, I usually find that what works is to close Firefox, open the tray on Kee, select Tools/KeePassRPC (Keefox) Options/Authorised Clients and revoke all existing authorisations. Next time I try to connect, I’m asked for the authorisation code. I then have to find this (sometimes the window is hidden by other stuff), and enter it. After that, all seems to work well till the next update. I find it very time-consuming and annoying, though, and would love to find an easier way of doing this.
Update, to mine running windows 10 pro 64 bit in firefox 58.0.1 64 bit and any previous version of same the RPC plugin was missing in my INSTALL directory in the plugins folder a simple download later and voila’ works perfect.
Special thanks to Luckyrat fur bein awsome and all the community, much appreciated
Moving from Windows 7 to Feren Linux (an ubuntu variant). Installed Kee with Firefox and Keepass 2 with terminal. Kee does not see keepass2 and only gives me the ability to open the Kee vault. When I open keepass2 with terminal then kee suddenly shows it is connected to keepass2 and it all works just fine (after entering the code for the connection). Even the kee firefox popup displays the open keepass button. Then when I exit terminal Keepass is terminated and the kee logo turns to the big red off and the open keepass button disappears from the popup. Please tell me what or where to complete the connection between the two programs. I really do not want to have to recreate all those passwords.
Well I had the same problem.
Kee would open the keepass database, but not load passwords and show a yellow or red off.
Inside Keepass2 I somewhere had an option “set as Kee homegroup”.
After I did that, everything was fine.