Robin Posted December 28, 2018 Report Posted December 28, 2018 Hello, After the upgrade I had to reconfigure my webdav sync (using Nextcloud). Sadly this resulted in an error on both my windows and android client. I made sure that Enpass had a clean Nexctloud environment to setup the sync: the old Enpass 5 folder has been moved to a backup location. I can see that a new Enpass folder gets created, but it stays empty. So at least they seem to be connecting and can create the Enpass directory, but nothing else? When trying to sync, I get the following message: Quote Sync Error Something went wrong while syncing with WebDAV. Error code: 908405 Same error occurs in both the windows store and android play store version. I did not encounter these issues on Enpass 5, nothing else has changed on my Nextcloud server. Could anyone shed some light on what the error code means?
Vinod Kumar Posted December 29, 2018 Report Posted December 29, 2018 Hi @Robin, Sorry for inconvenience. Can you please PM a demo webdav account (if possible at all)? It will help us to pinpoint the issue quickly. Thanks.
Robin Posted December 29, 2018 Author Report Posted December 29, 2018 Hi @Vinod Kumar I seem to get flagged by the spam filter, I'm not able to send you a PM Are external URL's not allowed or something?
Vinod Kumar Posted December 29, 2018 Report Posted December 29, 2018 @Robin Try url without https and with spaces. I will correct it.
Robin Posted December 29, 2018 Author Report Posted December 29, 2018 @Vinod Kumar That worked, you should have received a PM
Richard Posted December 29, 2018 Report Posted December 29, 2018 I had the same issue but I think I have an idea what the problem is. It says you need to reconfigure but some remnant of the old config remains. I got the error but then selected cancel. It then displayed an error saying that two accounts can not sync to the same location. After that, it appears to be synced up. I think that the settings screen thinks no sync is configured but something, somewhere else in the system thinks it is.
ceage Posted December 29, 2018 Report Posted December 29, 2018 (edited) Sorry, posted to wrong thread. Edited December 30, 2018 by ceage Posted to wrong thread
Nico67 Posted January 31, 2019 Report Posted January 31, 2019 The suggested workaround by Vinod does not provide a solution. Any URL must start with a protocol declaration, you cannot leave it out. When I enter the the URL as <<SERVERIP>>/PATH, as suggested by Vinod, I am unable to connect, which makes perfectly sense since the protocol declaration is missing. When I enter the URL as HTTP://<<SERVERIP>>/PATH login also fails, because this connects to the webserver on port 80. On this port our WebDAV server doesn't listen since it uses SSL. Without this being fixed for me Enpass basically is useless.
Recommended Posts