KeePassHTTP - Update check failed. Version information file cannot be downloaded

[ntman1]

The KeePassHTTP.plgx plugin running using the current version of KeePass 2.49 has the following error consistently showing during update checking with "Update check failed. Version information file cannot be downloaded." appearing.

It would seem that the developer is not following the guidance provided by the developer of KeePass: "Plugin Development (2.x) - How to develop plugins for KeePass 2.x. - Update Checking" at https://keepass.info/help/v2_dev/plg_index.html#upd

[adrslaw]

i have the same issue in my organization.

[abelcheung]

Duplicate of #403 . BTW KeePassHTTP is unmaintained, it is recommended to migrate away from it as bugs won't be fixed anymore.

[O-Palda]

Duplicate of #403 . BTW KeePassHTTP is unmaintained, it is recommended to migrate away from it as bugs won't be fixed anymore.

Can you please advice, to what solution we should migrate to?

[abelcheung]

@O-Palda I guess the most stable long-term solution is to move to keepassxc, if user is willing to spend some time on migration, due to good maintenance of its browser extensions.

Personally I'm tightly coupled with another 3rd party KeePass plugin and can't migrate, so I opted for KeePass + KeePassNatMsg + KeePassXC browser extension combo.

If using KeePassHTTP is a must for anyone who have very specific reason, probably this unofficial fix can help them. Haven't tried, YMMV.

[adpe]

Thanks @abelcheung

The change works well!

[EdgarSedov]

@O-Palda I guess the most stable long-term solution is to move to keepassxc, if user is willing to spend some time on migration, due to good maintenance of its browser extensions.

Personally I'm tightly coupled with another 3rd party KeePass plugin and can't migrate, so I opted for KeePass + KeePassNatMsg + KeePassXC browser extension combo.

If using KeePassHTTP is a must for anyone who have very specific reason, probably this unofficial fix can help them. Haven't tried, YMMV.

Thank you!

[aadmiral]

Duplicate of #403 . BTW KeePassHTTP is unmaintained, it is recommended to migrate away from it as bugs won't be fixed anymore.

I'm a little new to github maintenance but it seems like there should be notice somewhere on here that the project is dead, especially for how long it's been.

[MarkCanada]

I'm a little new to github maintenance but it seems like there should be notice somewhere on here that the project is dead, especially for how long it's been.

Some projects get notes, but some maintainers just abandon their projects without notices - and other projects get abandoned because the maintainers die. It does happen.
A good indicator can be the last time there was a commit (this one had the last 5 years ago if you look at it) combined with the numbers of open issues (close to 200 here).
There can always be evergreen projects that don't need changing - some of my private programs haven't been changed in many years, but they still do what they were supposed to - but programs that interface with others need frequently more updates.

[mcarbonneaux]

@MarkCanada he may also have had problems in his life, or new jobs that leave no more time to maintain...

mayby be it's time to add new(s) maintainer ? or fork (it's GPL Licence no problem) ? depend on what the autor whant to do....

[rmcgee1]

I no longer need to use this plugin, so I deleted it from the plugins directory and restarted KeePass. However, it appears to still be "compiled in" with my application, as the "Check for Updates" continues to display it. How do I force a rescan/rebuild of the KeePass plugins?

[rjt]

There are many forks of this project, but most of them seem rather old as well. A recommended fork?