I'll probably update the wiki to provide a full troubleshooting of the native message system, sometime for some advanced setup, the manifest under the user location is not enough (like my case)Īlso during the debugging you may keep the task manager open to see if the browser run keepassxc-proxy binary. The liked documentations describe different locations for the different policies, different browsers and os. Then (and here is where my config/mistake got me stucked) the native messaging system have several location where it can be edited and or limited/denied for instance for chromium+linux a manifest json policy under /etc/chromium/policies/managed/manifest.json that contains "NativeMessagingUserLevelHosts": false, will completely block the system and will result in giving Key exchange was not successful error in that case just change the value to true or just remove that line and voila :) also under details button you may select collect errors.īefore going further the first thing to do is to follow the KeepassXC-Browser Troubleshooting Wiki and update/fix the json manifest file like described there this may help some one with a similar issue.įirst thing first here is the detailed documentation (reading it is what lead me to the solution.)Īlso under chromium an easy way to debug is to open chrome://extensions/ select developer mode at the top right then click Inspect views background.
but i'll post the solution according to Firefox and other systems as well. i am using chromium, (ungoogle-chromium) + Linux. was going nut with this issue since a long time and have just find the time to do some debugging and figure it out.
0 kommentar(er)
