.kdbx file in nextcloud don't open in keeweb

[derjohannes19]

When I click on a .kdbx file the file will get downloaded, and it don't get open in keeweb.

Also: Webdav is not working, i get http 401 error.

[aalaesar]

+1
tested on nextcloud 11.0.0 & 10.0.2

[aalaesar]

+1
tested on nextcloud 11.0.0 & 10.0.2

[jackxb]

+1
tested on nextcloud 11.0.0

[jackxb]

+1
tested on nextcloud 11.0.0

[xamindar]

Same issue here. Just installed it in nextcloud 11 and nothing has changed regarding clicking on kdbx files. Click on them, and they are downloaded. They do not open in keeweb.

[xamindar]

Same issue here. Just installed it in nextcloud 11 and nothing has changed regarding clicking on kdbx files. Click on them, and they are downloaded. They do not open in keeweb.

[geiseri]

Same here on 11.

[geiseri]

Same here on 11.

[scottharwell]

I don't intend to add another "me too", but I have some other details. I have found that if I disable the app on Nextcloud 11, and then restart it, then I am able to select a keepass db for about 30 mins. After that, the webdav connection seems to "break" and keeweb seems to move the open DB to a managed db outside of the Nextcloud integration. I then get the download behavior that others describe. Deleting the connection from keeweb, disabling keeweb, enabling keeweb, and reopening the ldbx file then allows me to use it again. Maybe this behaviour description will help.

[scottharwell]

I don't intend to add another "me too", but I have some other details. I have found that if I disable the app on Nextcloud 11, and then restart it, then I am able to select a keepass db for about 30 mins. After that, the webdav connection seems to "break" and keeweb seems to move the open DB to a managed db outside of the Nextcloud integration. I then get the download behavior that others describe. Deleting the connection from keeweb, disabling keeweb, enabling keeweb, and reopening the ldbx file then allows me to use it again. Maybe this behaviour description will help.

[Echse27]

After install the KeeWeb App inside NC11.0.0, you can choose a .kdbx file only one time by klicking the file itself.
When you edit a entry or add one, there is no sync back to the main .kdbx database.
Error: HTTP status 401
So now i cant found a way to drop the file from the WebApp...

[Echse27]

After install the KeeWeb App inside NC11.0.0, you can choose a .kdbx file only one time by klicking the file itself.
When you edit a entry or add one, there is no sync back to the main .kdbx database.
Error: HTTP status 401
So now i cant found a way to drop the file from the WebApp...

[Yamakasi]

Opening in Keeweb worked for me but just stopped without updating anything, only my browser (Chromium) is updated.

[Yamakasi]

Opening in Keeweb worked for me but just stopped without updating anything, only my browser (Chromium) is updated.

[Huster-at-github]

Same here. Does it need to be registered as a mimetype?

[Huster-at-github]

Same here. Does it need to be registered as a mimetype?

[Yamakasi]

I'm not sure, when I had a browsercache issue when upgraded to NC11 it just worked like that after I fixed that (cleared more hours of cache) and now it just stopped.

I thought I needed Webdav so was kinda surprised that clicking on it just worked!

I hope @jhass that he can give us some idea.

[Yamakasi]

I'm not sure, when I had a browsercache issue when upgraded to NC11 it just worked like that after I fixed that (cleared more hours of cache) and now it just stopped.

I thought I needed Webdav so was kinda surprised that clicking on it just worked!

I hope @jhass that he can give us some idea.

[nschiwy]

I've now been able to "fix" this twice by disabling and then re-enabling the app. For the time being I'm probably just going to use a URL shortener to open the URL, which tells it the nextcloud location of the database. (ex. https://your-url.com/nextcloud/index.php/apps/keeweb/?open=%2Fpath%2Fto%2Fdatabase.kdbx) though I can't be sure whether this will allow it to save correctly...

[nschiwy]

I've now been able to "fix" this twice by disabling and then re-enabling the app. For the time being I'm probably just going to use a URL shortener to open the URL, which tells it the nextcloud location of the database. (ex. https://your-url.com/nextcloud/index.php/apps/keeweb/?open=%2Fpath%2Fto%2Fdatabase.kdbx) though I can't be sure whether this will allow it to save correctly...

[Yamakasi]

Re-enabeling is a very good tip, this works indeed and happened also at my side when I had caching issues and re-enabled the app after emptying my cache. Maybe some mimetype magic happens in the browsercache when you enable it ?

[Yamakasi]

Re-enabeling is a very good tip, this works indeed and happened also at my side when I had caching issues and re-enabled the app after emptying my cache. Maybe some mimetype magic happens in the browsercache when you enable it ?

[rocky4546]

[updated] I have some info that may help. First, I found the command to update the database indexes that will cause files located in the data area to launch KeeWeb. This command is
sudo -u www-data php [nextcloud home]/occ -vvv files:scan --all

I still have issues, but this is very close. If the file in the data area is updated, either from KeeWeb or externally updated by KeePass, it will break versioning and sharing. Running the occ command will fix launching KeyWeb, but the bugs for versioning and sharing still exist. This is not an option for me since I would like multiple people to access the password file.

The solution I found is to put the file in an external storage area. Uploading the file and then running the occ command seems to make it work. Any updates and running the occ command will also make it work. I plan to run multiple cronjobs with this command. One every so often that does the entire system and others that run very often for places that KeePass files are kept. The command to run only on a specific folder is
sudo -u www-data php [nextcloud home]/occ -vvv --path=/[admin]/files/[external path] files:scan

At some point in the future, it would be nice to not have to have these workarounds in place, but I think I am good for now. Good Luck

[rocky4546]

[updated] I have some info that may help. First, I found the command to update the database indexes that will cause files located in the data area to launch KeeWeb. This command is
sudo -u www-data php [nextcloud home]/occ -vvv files:scan --all

I still have issues, but this is very close. If the file in the data area is updated, either from KeeWeb or externally updated by KeePass, it will break versioning and sharing. Running the occ command will fix launching KeyWeb, but the bugs for versioning and sharing still exist. This is not an option for me since I would like multiple people to access the password file.

The solution I found is to put the file in an external storage area. Uploading the file and then running the occ command seems to make it work. Any updates and running the occ command will also make it work. I plan to run multiple cronjobs with this command. One every so often that does the entire system and others that run very often for places that KeePass files are kept. The command to run only on a specific folder is
sudo -u www-data php [nextcloud home]/occ -vvv --path=/[admin]/files/[external path] files:scan

At some point in the future, it would be nice to not have to have these workarounds in place, but I think I am good for now. Good Luck

[juanjux]

As a tip, you don't need to disable and reenable the app to use the file from Keeweb: if you open the Keeweb app from the initial app menu the file will show in the list and opening it from there will work even if Keeweb doesn't open from the Files app.

[juanjux]

As a tip, you don't need to disable and reenable the app to use the file from Keeweb: if you open the Keeweb app from the initial app menu the file will show in the list and opening it from there will work even if Keeweb doesn't open from the Files app.

[Yamakasi]

I will not always display there, I think this is due to sessions which are not there anymore. 2016-12-31 20:26 GMT+01:00 juanjux <notifications@github.com>:

…

As a tip, you don't need to disable and reenable the app to use the file from Keeweb: if you open the Keeweb app from the initial app menu the file will show in the list and opening it from there will work even if Keeweb doesn't open from the Files app. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#34 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEpNZ60GttF07HJDxdkwfn8o3Xk9-lMFks5rNqxNgaJpZM4LQLOL> .

[Yamakasi]

I will not always display there, I think this is due to sessions which are not there anymore. 2016-12-31 20:26 GMT+01:00 juanjux <notifications@github.com>:

…

As a tip, you don't need to disable and reenable the app to use the file from Keeweb: if you open the Keeweb app from the initial app menu the file will show in the list and opening it from there will work even if Keeweb doesn't open from the Files app. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#34 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEpNZ60GttF07HJDxdkwfn8o3Xk9-lMFks5rNqxNgaJpZM4LQLOL> .

[dnauck]

For me the workaround with disable/enable the app or scan all files does not help.

I' ve the following message in my java script console:

Resource interpreted as Document but transferred with MIME type application/octet-stream

Looks like the mime type is not registered.

[dnauck]

For me the workaround with disable/enable the app or scan all files does not help.

I' ve the following message in my java script console:

Resource interpreted as Document but transferred with MIME type application/octet-stream

Looks like the mime type is not registered.

[gadolithium]

+1 tested on NC 11.0.0.

[gadolithium]

+1 tested on NC 11.0.0.

[dennisheitmann]

+1 does not work (click on file in NC 11)

[dennisheitmann]

+1 does not work (click on file in NC 11)

[juanjux]

@Yamakasi it's true, a little later I lost the session and it dissapeared from the "recent files" list. But maybe I found another workaround? Tested with several different browsers, computers, networks and incognito mode so the session shouldn't exist. If you go directly to the keeweb + file URL like:

https://mydomain.com/apps/keeweb/?open=/mifile.kdbx

It seems to work.

[juanjux]

@Yamakasi it's true, a little later I lost the session and it dissapeared from the "recent files" list. But maybe I found another workaround? Tested with several different browsers, computers, networks and incognito mode so the session shouldn't exist. If you go directly to the keeweb + file URL like:

https://mydomain.com/apps/keeweb/?open=/mifile.kdbx

It seems to work.

[grojas7]

+1
Tested on Nextcloud 11.0.0

[grojas7]

+1
Tested on Nextcloud 11.0.0

[juanjux]

Yes, this is still happening on 11.0.1.

[juanjux]

Yes, this is still happening on 11.0.1.

[SonireolxXx]

Same problem here on NC 11.0.1
I'm using WebDAV to sync with other devices, once the file is updated by other clients this problem occurs.

[SonireolxXx]

Same problem here on NC 11.0.1
I'm using WebDAV to sync with other devices, once the file is updated by other clients this problem occurs.

[mwalbeck]

I think I've nailed down the issue. When you edit and save a file, keeweb saves it in a new file with a unix timestamp after the name then proceeds to delete the old file and rename the new one to remove the timestamp. Nextcloud registers the file with the unix timestamp as the extension and caches that information, so the cached mimetype is wrong. It's saved as a hidden file.

Also the way the kdbx mimetype is registered, if you upload a keepass file after you've enabled the app it will be cached with a generic mimetype instead of the kdbx mimetype. I don't really know the details on this one.

You shouldn't use the fix below. It has had serious performance issues for some people. Rather look at the fix here #34 (comment)

---

I've created a small fix for the above. It's not the best solution but It works. It simply changes the mimetype of any .kdbx file in the filecache everytime you reload a page in nextcloud, so it might effect performance depending on your setup.

If you add

$mimetypeId = $mimeTypeLoader->getId('x-application/kdbx');
$mimeTypeLoader->updateFilecache('%.kdbx', $mimetypeId);

Below

// Register custom mimetype we can hook in the frontend
$mimeTypeDetector->getAllMappings();
$mimeTypeDetector->registerType('kdbx', 'x-application/kdbx', 'x-application/kdbx');

In your appinfo/app.php file you should be good. (It's at the bottom)

I can make a pull request if there is interest for this, but none the less I'll try to find a more elegant solution and make a pull request with that instead.

[mwalbeck]

I think I've nailed down the issue. When you edit and save a file, keeweb saves it in a new file with a unix timestamp after the name then proceeds to delete the old file and rename the new one to remove the timestamp. Nextcloud registers the file with the unix timestamp as the extension and caches that information, so the cached mimetype is wrong. It's saved as a hidden file.

Also the way the kdbx mimetype is registered, if you upload a keepass file after you've enabled the app it will be cached with a generic mimetype instead of the kdbx mimetype. I don't really know the details on this one.

You shouldn't use the fix below. It has had serious performance issues for some people. Rather look at the fix here #34 (comment)

---

I've created a small fix for the above. It's not the best solution but It works. It simply changes the mimetype of any .kdbx file in the filecache everytime you reload a page in nextcloud, so it might effect performance depending on your setup.

If you add

$mimetypeId = $mimeTypeLoader->getId('x-application/kdbx');
$mimeTypeLoader->updateFilecache('%.kdbx', $mimetypeId);

Below

// Register custom mimetype we can hook in the frontend
$mimeTypeDetector->getAllMappings();
$mimeTypeDetector->registerType('kdbx', 'x-application/kdbx', 'x-application/kdbx');

In your appinfo/app.php file you should be good. (It's at the bottom)

I can make a pull request if there is interest for this, but none the less I'll try to find a more elegant solution and make a pull request with that instead.

[SonireolxXx]

@mwalbeck Thank you for the solution, I just tried it on NC 11.0.1 and it works, didn't notice any significant impact on performance.

I think this is the best approach for the issue so far.

[SonireolxXx]

@mwalbeck Thank you for the solution, I just tried it on NC 11.0.1 and it works, didn't notice any significant impact on performance.

I think this is the best approach for the issue so far.

[Yamakasi]

Magnus, good idea, create a PR for it I would say. 2017-01-18 22:37 GMT+01:00 SonireolxXx <notifications@github.com>:

…

@mwalbeck <https://github.com/mwalbeck> Thank you for the solution, I just tried it on NC 11.0.1 and it works, didn't notice any significant impact on performance. I think this is the best approach for the issue so far. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#34 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEpNZ7oVoyHhBQPSlssKkXrF3iWVkEh5ks5rToYVgaJpZM4LQLOL> .

[Yamakasi]

Magnus, good idea, create a PR for it I would say. 2017-01-18 22:37 GMT+01:00 SonireolxXx <notifications@github.com>:

…

@mwalbeck <https://github.com/mwalbeck> Thank you for the solution, I just tried it on NC 11.0.1 and it works, didn't notice any significant impact on performance. I think this is the best approach for the issue so far. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#34 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEpNZ7oVoyHhBQPSlssKkXrF3iWVkEh5ks5rToYVgaJpZM4LQLOL> .

[mwalbeck]

@jhass I've send a pull request to upstream nextcloud to fix the issue with mimetype detection on hidden files I talked about here #38. This is only half the problem though. From what I've found the mimetype detection doesn't utilize the oc_mimetypes database tables to look up mimetypes. So the only proper way to currently register the mimetype is in the mimetypemapping file in nextcloud server. So if the mimetype is registered with upstream nextcloud this issue would be resolved with the release of nextcloud 12.

Thoughts?

[mwalbeck]

@jhass I've send a pull request to upstream nextcloud to fix the issue with mimetype detection on hidden files I talked about here #38. This is only half the problem though. From what I've found the mimetype detection doesn't utilize the oc_mimetypes database tables to look up mimetypes. So the only proper way to currently register the mimetype is in the mimetypemapping file in nextcloud server. So if the mimetype is registered with upstream nextcloud this issue would be resolved with the release of nextcloud 12.

Thoughts?

[jhass]

Well, registering the mimetype upstream would certainly work, but that feels like a band-aid to a missing feature in the app API, so I'd prefer to either have the detection use the database or have an API to ship a mimetype used for detection with an app, for example by shipping another json file that's aggregated with the default one.

[jhass]

Well, registering the mimetype upstream would certainly work, but that feels like a band-aid to a missing feature in the app API, so I'd prefer to either have the detection use the database or have an API to ship a mimetype used for detection with an app, for example by shipping another json file that's aggregated with the default one.

[guddl]

I had this problem when I resticted the app to be available for a special group only.
After removing the group from "Enable only for specific groups" everything works fine again.

[guddl]

I had this problem when I resticted the app to be available for a special group only.
After removing the group from "Enable only for specific groups" everything works fine again.

[dedero1985]

Hi guys,

I tried the solution from mwalbeck and works great (thanks a lot!). I see no performance impacts under Nextcloud 11.0.1 using Keeweb v1.3.3 (52701af, 2016-12-17)

Cheers,
Bruno.

[dedero1985]

Hi guys,

I tried the solution from mwalbeck and works great (thanks a lot!). I see no performance impacts under Nextcloud 11.0.1 using Keeweb v1.3.3 (52701af, 2016-12-17)

Cheers,
Bruno.

[ds4a]

The temporary fix offered by @nschiwy of

I've now been able to "fix" this twice by disabling and then re-enabling the app.

works for me also.

[ds4a]

The temporary fix offered by @nschiwy of

I've now been able to "fix" this twice by disabling and then re-enabling the app.

works for me also.

[Sanookmakmak]

Same here. Nextcloud 11.0.1 and Keeweb 0.3.0

Disabling and re-enabling the Keeweb app helps, but after a while it is no more possible to open the kdbx file. I just can be downloaded.

So the admin needs to disable and re-enable the app again (and again and again...)

:-(

[Sanookmakmak]

Same here. Nextcloud 11.0.1 and Keeweb 0.3.0

Disabling and re-enabling the Keeweb app helps, but after a while it is no more possible to open the kdbx file. I just can be downloaded.

So the admin needs to disable and re-enable the app again (and again and again...)

:-(

[mwalbeck]

With the release of Nextcloud 12, you can fix this by adding a mimetypemapping.json file to your nextcloud/config folder. In the file you add the mimetype "kdbx": ["x-application/kdbx"]

For easy copy paste:

{
    "kdbx": ["x-application/kdbx"]
}

There is a little more info in the nextcloud admin docs here, https://docs.nextcloud.com/server/11/admin_manual/configuration_mimetypes/index.html

This will survive both app and system updates and should be the best solution until it can be done through the app itself.

[mwalbeck]

With the release of Nextcloud 12, you can fix this by adding a mimetypemapping.json file to your nextcloud/config folder. In the file you add the mimetype "kdbx": ["x-application/kdbx"]

For easy copy paste:

{
    "kdbx": ["x-application/kdbx"]
}

There is a little more info in the nextcloud admin docs here, https://docs.nextcloud.com/server/11/admin_manual/configuration_mimetypes/index.html

This will survive both app and system updates and should be the best solution until it can be done through the app itself.

[ds4a]

@mwalbeck I have read the documentation you referred to at https://docs.nextcloud.com/server/11/admin_manual/configuration_mimetypes/index.html.
I'm a little confused as this doesn't seem to present a solution to this issue. The documentation refers to the mimetypealiases and mimetypemapping json files that allow NC to display the correct icon for a specified mimetype. The icon files are placed in the relevant theme directory. Am I missing something?
I directly edited the mimetypealiases.dist.json and mimetypemapping.dist.json files located in resources/config in my NC installation and ran the maintenance:mimetype:update-js command, and the reported issue still persists.

[ds4a]

@mwalbeck I have read the documentation you referred to at https://docs.nextcloud.com/server/11/admin_manual/configuration_mimetypes/index.html.
I'm a little confused as this doesn't seem to present a solution to this issue. The documentation refers to the mimetypealiases and mimetypemapping json files that allow NC to display the correct icon for a specified mimetype. The icon files are placed in the relevant theme directory. Am I missing something?
I directly edited the mimetypealiases.dist.json and mimetypemapping.dist.json files located in resources/config in my NC installation and ran the maintenance:mimetype:update-js command, and the reported issue still persists.

[mwalbeck]

@ds4a I should probably have been a bit more specific, but if you only focus on the mimetypemapping aspect, which is a way to register a mimetype in nextcloud. Since this issue is a mimetype issue we can use the mimetypemapping file to register a mimetype in nextcloud. This is needed as there currently is no proper way for an app to register a new mimetype.

So we don't need to edit the mimetypealiases file or run the maintenance:mimetype:update-js command, as they are purely for matching icons and mimetypes.

Also, as I noted above, this will only work with Nextcloud 12 and onwards, because of a small change to the mimetype detection in Nextcloud.

[mwalbeck]

@ds4a I should probably have been a bit more specific, but if you only focus on the mimetypemapping aspect, which is a way to register a mimetype in nextcloud. Since this issue is a mimetype issue we can use the mimetypemapping file to register a mimetype in nextcloud. This is needed as there currently is no proper way for an app to register a new mimetype.

So we don't need to edit the mimetypealiases file or run the maintenance:mimetype:update-js command, as they are purely for matching icons and mimetypes.

Also, as I noted above, this will only work with Nextcloud 12 and onwards, because of a small change to the mimetype detection in Nextcloud.

[ds4a]

@mwalbeck Thanks for the explanation and clarification.

[ds4a]

@mwalbeck Thanks for the explanation and clarification.

[Darkitty]

"I've now been able to "fix" this twice by disabling and then re-enabling the app."

Fix the issue with Nextcloud 11.0.1 and version 0.3.0 :D

[Darkitty]

"I've now been able to "fix" this twice by disabling and then re-enabling the app."

Fix the issue with Nextcloud 11.0.1 and version 0.3.0 :D

[proehlen]

@mwalbeck 's code fix didn't fix the issue for me unfortunately. Upgrading to NextCloud 12 also isn't an option. I can't really disable/enable the app repeatedly either since the files change a lot. Anyone got any other ideas on this?

[proehlen]

@mwalbeck 's code fix didn't fix the issue for me unfortunately. Upgrading to NextCloud 12 also isn't an option. I can't really disable/enable the app repeatedly either since the files change a lot. Anyone got any other ideas on this?

[yp6128]

The enable/disable "fix" worked for me, but How to also open the *.key file ? 💃 :)

[yp6128]

The enable/disable "fix" worked for me, but How to also open the *.key file ? 💃 :)

[jthomasdewald]

@mwalbeck Thanks for the correct command. Worked on my NC 12.0.0 only after adding the mimetype, updating the db AND disabling/enabling keepass

[jthomasdewald]

@mwalbeck Thanks for the correct command. Worked on my NC 12.0.0 only after adding the mimetype, updating the db AND disabling/enabling keepass

[patschi]

Had the same reported issue as described here, with latest Nextcloud 12.0.0.29 (fresh install). Without any manually editing the mimetypemapping.json, just the mimetype:update-db command fixed it. I'm not that fimilar with the possibilities of the NC-plugin-development, but wouldn't it be possible to just trigger that command automatically when enabling this plugin?

[patschi]

Had the same reported issue as described here, with latest Nextcloud 12.0.0.29 (fresh install). Without any manually editing the mimetypemapping.json, just the mimetype:update-db command fixed it. I'm not that fimilar with the possibilities of the NC-plugin-development, but wouldn't it be possible to just trigger that command automatically when enabling this plugin?

[AgenturVS]

Thanks, juanjux. I'm using your URL and it is working perfect for me.

[AgenturVS]

Thanks, juanjux. I'm using your URL and it is working perfect for me.

[stratacast]

I did what @JSoko suggested and ran the command that @mwalbeck said to do and that fixed my problem with opening my .kdbx file on NC 12.0.0 with keeweb version 0.4. Thank you!

[stratacast]

I did what @JSoko suggested and ran the command that @mwalbeck said to do and that fixed my problem with opening my .kdbx file on NC 12.0.0 with keeweb version 0.4. Thank you!

[ghost]

Was having the same issue myself in 12.0.0, but using the correct command from both @JSoko and @mwalbeck has fixed it for now. Just to clarify, the command is:

sudo -u www-data php /var/www/**NEXTCLOUD FOLDER**/occ maintenance:mimetype:update-db --repair-filecache

[ghost]

Was having the same issue myself in 12.0.0, but using the correct command from both @JSoko and @mwalbeck has fixed it for now. Just to clarify, the command is:

sudo -u www-data php /var/www/**NEXTCLOUD FOLDER**/occ maintenance:mimetype:update-db --repair-filecache

[fthiery]

The workaround works (NC12), but needs to be repeated regulary; any idea why / how to fix this permanently ? Should i run this in a cron every minute ? Sounds like a bad solution to me... I believe that currently it should be run manually every time a new kbdx file is added.

I also added a cron to automate this:

root@nextcloud:/etc/cron.d# cat /etc/cron.d/fixmimetypes 
*/5 * * * * root sudo -u www-data php /var/www/html/nextcloud/occ maintenance:mimetype:update-db --repair-filecache

[fthiery]

The workaround works (NC12), but needs to be repeated regulary; any idea why / how to fix this permanently ? Should i run this in a cron every minute ? Sounds like a bad solution to me... I believe that currently it should be run manually every time a new kbdx file is added.

I also added a cron to automate this:

root@nextcloud:/etc/cron.d# cat /etc/cron.d/fixmimetypes 
*/5 * * * * root sudo -u www-data php /var/www/html/nextcloud/occ maintenance:mimetype:update-db --repair-filecache

[stratacast]

@fthiery did you solve your problem? The solution of putting the .json file in your nextcloud/config folder is a permanently lasting solution

[stratacast]

@fthiery did you solve your problem? The solution of putting the .json file in your nextcloud/config folder is a permanently lasting solution

[fthiery]

Yes it seems to work without the cron, sorry for not reporting.

[fthiery]

Yes it seems to work without the cron, sorry for not reporting.

[zeigerpuppy]

Thanks @JSoko and @mwalbeck! I can confirm the following works well with NC12 (no need to enable/disable app or run any crons):

nano /var/www/nextcloud/config/mimetypemapping.json

add kdbx mimetype

{
    "kdbx": ["x-application/kdbx"]
}

update database of mimetypes

sudo -u www-data php /var/www/nextcloud/occ maintenance:mimetype:update-db --repair-filecache

[zeigerpuppy]

Thanks @JSoko and @mwalbeck! I can confirm the following works well with NC12 (no need to enable/disable app or run any crons):

nano /var/www/nextcloud/config/mimetypemapping.json

add kdbx mimetype

{
    "kdbx": ["x-application/kdbx"]
}

update database of mimetypes

sudo -u www-data php /var/www/nextcloud/occ maintenance:mimetype:update-db --repair-filecache

[e-alfred]

Maybe the useful information from @zeigerpuppy can be put into the main readme file of this repository? It would help people a lot to get Keeweb open the files in Nextcloud.

[e-alfred]

Maybe the useful information from @zeigerpuppy can be put into the main readme file of this repository? It would help people a lot to get Keeweb open the files in Nextcloud.

[ds4a]

I just wanted to feedback that the upgrade to Keeweb 0.4.0 under NC 11.0.2 has resolved this issue for me. Although just to note that once upgraded the app needs to disabled and then reenabled, just the once! Then all is good. I can now select a keeweb file from NC and Keeweb opens in NC as expected.

I Like the other improvements delivered in Keeweb 0.4.0.

Well done to the NC maintainers on these fixes and improvements. Much appreciated, this is one of the most useful apps on NC, especially when you have lots of details to remember.

[ds4a]

I just wanted to feedback that the upgrade to Keeweb 0.4.0 under NC 11.0.2 has resolved this issue for me. Although just to note that once upgraded the app needs to disabled and then reenabled, just the once! Then all is good. I can now select a keeweb file from NC and Keeweb opens in NC as expected.

I Like the other improvements delivered in Keeweb 0.4.0.

Well done to the NC maintainers on these fixes and improvements. Much appreciated, this is one of the most useful apps on NC, especially when you have lots of details to remember.

[theScrabi]

I'm using Nextcloud 12.0.3 and Keeweb 0.4.0, however this error still occurs for me, and it seems this solution does not work for me either?

[theScrabi]

I'm using Nextcloud 12.0.3 and Keeweb 0.4.0, however this error still occurs for me, and it seems this solution does not work for me either?

[ghost]

@theScrabi After updating to 12.0.3 myself, I found it wasn't working. Ran the following command (as above), and then after opening the database file from the file structure (as opposed to just launching Keeweb and expecting it to find it), it launches the Keeweb app.

sudo -u www-data php /var/www/**NEXTCLOUD FOLDER**/occ maintenance:mimetype:update-db --repair-filecache

The app then recognises where the database is after this, though trying to open it from the app with the db password, I get an error:

Error There was an error opening file [object Event]

So it works fine when opening it from the file structure, but not when opening it from the app itself.

[ghost]

@theScrabi After updating to 12.0.3 myself, I found it wasn't working. Ran the following command (as above), and then after opening the database file from the file structure (as opposed to just launching Keeweb and expecting it to find it), it launches the Keeweb app.

sudo -u www-data php /var/www/**NEXTCLOUD FOLDER**/occ maintenance:mimetype:update-db --repair-filecache

The app then recognises where the database is after this, though trying to open it from the app with the db password, I get an error:

Error There was an error opening file [object Event]

So it works fine when opening it from the file structure, but not when opening it from the app itself.

[theScrabi]

Yes I can confirm. That worked :)

[theScrabi]

Yes I can confirm. That worked :)

[kevquirk]

I've not tested this workaround yet, but would updating the mimetype be required every time there is an NC update? Frustrating if that's the case. :(

[kevquirk]

I've not tested this workaround yet, but would updating the mimetype be required every time there is an NC update? Frustrating if that's the case. :(

[mammuth]

@kevquirk The webupdater does not override settings in the config. After the last updates I didn't need to update the mimetypes.

[mammuth]

@kevquirk The webupdater does not override settings in the config. After the last updates I didn't need to update the mimetypes.

[kepuvv]

Thank, zeigerpuppy! Its work for me

[kepuvv]

Thank, zeigerpuppy! Its work for me

[DMW007]

I can confirm that the mime-mapping from @zeigerpuppy is working fine on Nextcloud 12. Seems like that the command read the mimetypemappings.json file and copy all those mapping in the database. So afaik it should be possible for the nextcloud-keeweb extension to register it's mapping autmatically after installation?

If not, I agree that we should at least refer to this issue in the documentation/installation guide. Otherwise, a lot of people are wasting time to find out why this is not working. I also did cause it's confusing.

[DMW007]

I can confirm that the mime-mapping from @zeigerpuppy is working fine on Nextcloud 12. Seems like that the command read the mimetypemappings.json file and copy all those mapping in the database. So afaik it should be possible for the nextcloud-keeweb extension to register it's mapping autmatically after installation?

If not, I agree that we should at least refer to this issue in the documentation/installation guide. Otherwise, a lot of people are wasting time to find out why this is not working. I also did cause it's confusing.

[ppmt]

My instance of NextCloud is on a hosted site so I don't have access to the command line. Is there another way to update the mime and database?

[ppmt]

My instance of NextCloud is on a hosted site so I don't have access to the command line. Is there another way to update the mime and database?

[ggeorgg]

Upload the following cmd.phpx file to your nextcloud root.
cmd.zip
I also had to comment out line 39 in console.php (I am on nextcloud 12.0.3 with php 7.1 cgi, no php 5.6.0)
Open your browser and navigate to the cmd.phpx you have recently uploaded (e.g. https://nextcloud.domain.com/cmd.phpx)
That should do it.
At least undo your changes. Delete the cmd.phpx again and comment in the line in console.php, otherwise your nextcloud instance will complain the next time you want to update)

[ggeorgg]

Upload the following cmd.phpx file to your nextcloud root.
cmd.zip
I also had to comment out line 39 in console.php (I am on nextcloud 12.0.3 with php 7.1 cgi, no php 5.6.0)
Open your browser and navigate to the cmd.phpx you have recently uploaded (e.g. https://nextcloud.domain.com/cmd.phpx)
That should do it.
At least undo your changes. Delete the cmd.phpx again and comment in the line in console.php, otherwise your nextcloud instance will complain the next time you want to update)

[ppmt]

@ggeorg : thanks a lot for the script. I can now open my keepass file from Nextcloud!

I had to activate a module called posix to make the script work and rename it to php from phpx

[ppmt]

@ggeorg : thanks a lot for the script. I can now open my keepass file from Nextcloud!

I had to activate a module called posix to make the script work and rename it to php from phpx

[ludenticus]

Enabling/disabling the app has no effect on Nextcloud 12.0.3

[ludenticus]

Enabling/disabling the app has no effect on Nextcloud 12.0.3

[sunjam]

I've read through this thread and tried to setup Keeweb Webdav access on Nextcloud 12.0.4, but error I get is a little different.

[sunjam]

I've read through this thread and tried to setup Keeweb Webdav access on Nextcloud 12.0.4, but error I get is a little different.

[sbrl]

@sunjam I'd suggest opening a separate issue about that.

[sbrl]

@sunjam I'd suggest opening a separate issue about that.

[sesipod]

I got it working on Nextcloud 12.0.4 - Debian 9 x64

I put my .kdbx on an " SMB / CIFS " share.
Added the mimetypemapping.json file & restarted apache2.
https://github.com/jhass/nextcloud-keeweb/issues/34#issuecomment-278634544

I now can open the .kdbx form the SMB storage location.
Working for me on the following browsers....
Chrome Version 64.0.3282.39 (Official Build) beta (32-bit)
Firefox 57.0.3 (64-bit)

[sesipod]

I got it working on Nextcloud 12.0.4 - Debian 9 x64

I put my .kdbx on an " SMB / CIFS " share.
Added the mimetypemapping.json file & restarted apache2.
https://github.com/jhass/nextcloud-keeweb/issues/34#issuecomment-278634544

I now can open the .kdbx form the SMB storage location.
Working for me on the following browsers....
Chrome Version 64.0.3282.39 (Official Build) beta (32-bit)
Firefox 57.0.3 (64-bit)

[schnappijedi]

Wanted to add (clarify) a workaround. Granted have never been able to edit a .kdbx file in Nextcloud but this will work for opening and otherwise using a database. Use a bookmark pointing to one's .kdbx database such as: https://server/index.php/apps/keeweb/?open=/AnyFolder/Keepass-database.kdbx

Nextcloud has a bookmarking app that one could put this URL into or could keep in it a simple text document. Not ideal but works.

[schnappijedi]

Wanted to add (clarify) a workaround. Granted have never been able to edit a .kdbx file in Nextcloud but this will work for opening and otherwise using a database. Use a bookmark pointing to one's .kdbx database such as: https://server/index.php/apps/keeweb/?open=/AnyFolder/Keepass-database.kdbx

Nextcloud has a bookmarking app that one could put this URL into or could keep in it a simple text document. Not ideal but works.

[zerpex]

Don't understand this issue, I got it working since Nextcloud 11 & 12 & 13.
many kdbx files on nextcloud file manager : a click on one of them open it directly on keypass... The expected behaviour, right ?

Using Nextcloud on docker with hoellen/nextcloud image : https://github.com/hoellen/dockerfiles/tree/master/nextcloud
z.

[zerpex]

Don't understand this issue, I got it working since Nextcloud 11 & 12 & 13.
many kdbx files on nextcloud file manager : a click on one of them open it directly on keypass... The expected behaviour, right ?

Using Nextcloud on docker with hoellen/nextcloud image : https://github.com/hoellen/dockerfiles/tree/master/nextcloud
z.

[DovendyrE]

Hi
I'm currently using keeweb in nextcloud 13.0.1
Just edited the /var/www/nextcloud/apps/keeweb/appinfo/info.xml to make it support nextcloud 13 then ran the command below to update mimetypes, and wokrs like charm here.
sudo -u www-data php /var/www/nextcloud/occ maintenance:mimetype:update-db --repair-filecache

PS. this command worked for me when I was still using nextcloud 12.

[DovendyrE]

Hi
I'm currently using keeweb in nextcloud 13.0.1
Just edited the /var/www/nextcloud/apps/keeweb/appinfo/info.xml to make it support nextcloud 13 then ran the command below to update mimetypes, and wokrs like charm here.
sudo -u www-data php /var/www/nextcloud/occ maintenance:mimetype:update-db --repair-filecache

PS. this command worked for me when I was still using nextcloud 12.

[danger89]

So is it fixed or.. does it still require manual actions from the admin?

[danger89]

So is it fixed or.. does it still require manual actions from the admin?