Closed sergiocasero closed 1 year ago
gz83
commented
1 year ago Hi folks! Just trying to use KeePass with Thorium with no luck, I always get:
I've tested on chrome and chromium and it works as expected. I've also removed all the keys in keepass (because maybe there were conflicts or something) but no luck, it doesn't work.
@sergiocasero Hello, the KeepassXC extension can be used with Keepass or KeepassXC, which software is installed on your computer? Keepass or KeepassXC?
sergiocasero
commented
1 year ago @gz83 keepassXC.
I see this in the keepass extension logs:
[Error client.js:337] KeePassXC-Browser - Failed to connect: Specified native messaging host not found.
2 [Error page.js:233] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist.I think it's related to the browser name or something, I can't enable "thorium" in the options. (But as I said, chromium and chrome work)
gz83
commented
1 year ago @gz83 keepassXC.
I see this in the keepass extension logs:
[Error client.js:337] KeePassXC-Browser - Failed to connect: Specified native messaging host not found. 2 [Error page.js:233] KeePassXC-Browser - Cannot send activated_tab message: Could not establish connection. Receiving end does not exist.I think it's related to the browser name or something, I can't enable "thorium" in the options. (But as I said, chromium and chrome work)
@sergiocasero I also use the KeepassXC+KeepassXC extension, the browser can read the password library normally, and the filling function can also be used normally. The following is my browser integration settings for your reference.
Since the KeepassXC software prohibits screenshots, I am sorry to show you the content of the settings in this way.
In addition, you can refer to the official troubleshooting guide.
https://github.com/keepassxreboot/keepassxc-browser/wiki/Troubleshooting-guide
sergiocasero
commented
1 year ago @gz83 finally found the solution!!
I'll post here if anyone needs this in the future:
The problem is that Thorium and Chromium are "the same browser" so keepass is detecting the NativeMessagingHosts for chromium, so in Browser integration -> Advanced we need to override the location of the proxy.
Enable "use custom proxy", select browser type: "Chrome", and for the location, put this
/Users/sergio/Library/Application Support/Thorium/NativeMessagingHosts
instead of
/Users/sergio/Library/Application Support/Chromium/NativeMessagingHosts
And that's it!
devgizzo
commented
1 year ago On MacOS the /Users/youruser/Library/Application Support/Thorium/NativeMessagingHosts folder is empty if you install it next to some other chromium browser, copying the json file over to this folder solves the issue.
aldobelus0
commented
1 year ago I adapted to GNU/Linux the solution exposed further up and has given result. The path in my operating system is
/home/usuario/.config/thorium/NativeMessagingHostsNow, you only have to substitute the explained before to this place and you got it.
At first, it has occurred to me that the extension didn't adopted the change. I had to uninstall everything, to include the modification in the browsers integration of the application (next image) and to install again the extension. Then yes, it has produced the change.
Good Luck!
NOTE: Don't be surprised when you discover that there is not archive in the route to NativeMessagingHosts. It will create itself automatically when the extension loads.
ANOTHER NOTE: I left this area like that (next image). Chromium only. It wasn't needed to check Google Chrome too.
If you find any problem ask for more information. I have doubts about my explanations... xD
And thank you very much, @sergiocasero!!
Hi folks! Just trying to use KeePass with Thorium with no luck, I always get:
I've tested on chrome and chromium and it works as expected. I've also removed all the keys in keepass (because maybe there were conflicts or something) but no luck, it doesn't work.