Open Mark-Booth opened 8 years ago
This could be as simple as updating the notification in KeePassFox.jsm to be something like:
this._showNotification("Unknown KeePassHttp error: " + s
+ " connecting to " + this._keepassHttpUrl, null,
"kpf-error-note");`
But I'm not very familiar with javascript.
While in that areas of code, it might be worth adding the same text to the "KeePassHttp is not running" error too.
Yesterday I finally got around to installing mono, libgdiplus, KeePass and PassIFox on my work Linux machine (RHEL 6.7 Santiago, no root access). Although I followed the PassIFox instructions to the letter, I could not connect it to KeePass.
At the "KeePass has not been configured" banner when I clicked "Connect" it just returned "Unknown KeePassHttp error: 400", which was the same as I got if KeePass was not running. The fact that I didn't get a "KeePassHttp is not running" error should have been my first clue, but I didn't recognise it as significant.
I confirmed that the port was being opened by telnetting to "localhost 19455" both before and after starting KeePass, getting "Connection refused" and "Connected..." respectively.
Eventually, I decided to check about:config and searching for passifox I found a non default extensions.passifix.keepasshttp_url set. Before getting KeePass to work on my Linux machine, I had been trying to get it to connect to my KeePass install on my WIndows machine.
Resetting the url back to localhost:19455 git everything working, but the generic nature of the error didn't help me very much.
Although this is rather an edge case, It would be nice if passifox added the keepasshttp_url value to the error message when it is non standard.