KEEWEB WEBDAV 304 ERROR CODE
KEEWEB WEBDAV 304 ERROR PASSWORD
KEEWEB WEBDAV 304 ERROR WINDOWS

This comes with security risks, especially if any untrusted code or content is present in the unsandboxed process. In certain use cases that are incompatible with the sandbox (for instance, when using native node modules in the renderer), it is possible to disable the sandbox for specific processes. According to the official documentation of Electron Framework:įor most apps, sandboxing is the best choice. Temporary solution (until Keeweb receives an update)Īlthough no the ideal solution, it is for sure the quickest solution to launch the application in your system is to launch it through the terminal with an additional parameter, namely -no-sandbox: keeweb -no-sandboxĪfter running this command the application should be launched without any problem.

This issue was solved in the official electron project already, the problem is that the latest version of Keeweb doesn't use a newer version of Electron (the issue is still open on Github), causing the problem of the application in many of the latest operative systems based in Linux such as Arch Linux, Ubuntu, Fedora etc. The issue is caused specifically because of the version of Electron Framework used on the project that contains a bug where it makes applications crash in with glibc 2.34.

KEEWEB WEBDAV 304 ERROR WINDOWS

Electron Framework is the choice of many developers for packing web based applications as desktop applications that run on Linux, macOS and Windows using the same codebase. usr/bin/keeweb: line 2: 17607 Trace/breakpoint trap (core dumped) /usr/share/keeweb-desktop/keeweb ' 'Īfter some research, I found out that the problem wasn't Keeweb directly, but the platform where it runs on, Electron. Libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) Then, I tried to launch the application from the terminal and that's when I found the following error: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) At the beginning, I thought that maybe there was a problem with the way I installed Keeweb, so instead of using sudo apt-get, I used dpkg -i, with no success. I've always used Keeweb for Ubuntu, however during the installation of this program in Ubuntu 22.04, the application simply didn't start when clicking the icon. I usually store all of my credentials in keepass files as this allows me to store and use secure passwords for every account I have on the internet in a very safe way. This means that you can use it to manage your keepass files in other environment that isn't Windows.

KEEWEB WEBDAV 304 ERROR PASSWORD

See more details below.Keeweb is an awesome free cross-platform desktop application password manager compatible with KeePass. # This option is only available for Nginx >= 1.8.0. The WebDAV block for Seafile looks like this: location /seafdavįastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name įastcgi_param PATH_INFO $fastcgi_script_name įastcgi_param SERVER_PROTOCOL $server_protocol įastcgi_param QUERY_STRING $query_string įastcgi_param REQUEST_METHOD $request_method įastcgi_param CONTENT_TYPE $content_type įastcgi_param CONTENT_LENGTH $content_length I haven't tried Keepass2droid, but I managed to get KeeWeb (works fine on mobile) syncing with a Seafile hosted WebDAV share (using NGINX). I tried with Keepass2droid version 1.01-g (android application) and Keepass 'Professional' 2.36 and both have this issue, using the regular seafile client, everhting works fine.

I configured the Webdav access on Seafile (used their recommended configuration from here), their documentation was easy enough to follow, i can access the database no problem the issues comes when i add/change (only happens using Webdav) something to the Keepass database and save it it will corrupt Keepass database and replace it with a 0kb file. I m using Seafile for sometime and last week i read someone saying that they were using Webdav to access a Keepass database on android. I m posting here because i m trying to see if anyone ever came across this issue.

Keeweb webdav 304 error