My first guess would be no to both because I don’t think it would make a difference. Something to try might be using the webdav on the official app and see if that works. If yes, then your webdav setup is correct and the problem is with our keeweb. If no, then perhaps it could point to a problem your webdav setup.Įitherway, I will do some of my own testing and report back.Įdit: Initially I was having similar problems with ‘network error’ and then a ‘401’ error. But now it seems to be working find for me. Compatible with the majority of alternative programs (KeePass, KeePassXC, KeeWeb. I’m using Nextcloud for webdav and used the following link: then I enter my username and password.Įdit2: You don’t actually need to enter your user name and password to load the database from webdav. kdbx files (version 1 to 4) with AES - Twofish - ChaCha20 - Argon2 algorithm. Yunohost should already have that figure out. I dig this topic as i encounter the same problem. I’m on the last version og Yunohost on my RPI3B+. My Nextcloud is on another server and i have the version 15.0.7.īut i have the network error 401 too. When i look up the console debug with F12 in my browser, i have this message : has been blocked by CORS policy: Response to preflight request doesn’t pass access control check: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. ![]() I try to google this message and it seems there is a workaround by changing the htaccess or the virtual host in apache/niginx but i’m a little bit lost.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |