tTony Posted March 20, 2023 Report Share Posted March 20, 2023 I get this error code (WebDAV Sync Error with code 904035) on both, a Mac Desktop Client and an iOS mobile app, when I changed the certificate my webdav server from a normal SNI to a wildcard certificate (let's encrpyt). When I change back the certificate to the normal SNI, it directly starts to work again. Any possible explanations? in a browser and when manually checking the wildcard cert, it all looks valid and ok. Link to comment Share on other sites More sharing options...
Abhishek Dewan Posted March 20, 2023 Report Share Posted March 20, 2023 Hi @tTony Welcome to the Enpass Forums. To assist you better with the concern, please share the version of the Enpass app, and OS you are using. Link to comment Share on other sites More sharing options...
tTony Posted March 21, 2023 Author Report Share Posted March 21, 2023 Hi, my versions are as follows: from Mac App Store, 6.8.5 (1256), MacOS Ventura 13.2.1 on the iPhone, 6.8.6, iOS 16.3.1 both, iOS and MacOS showed the exact same error code 904035 thanks for checking. Link to comment Share on other sites More sharing options...
Abhishek Dewan Posted March 22, 2023 Report Share Posted March 22, 2023 Hi @tTony Thank you for sharing the requested details. I'm discussing this case with our dedicated team and will get back to you soon with an update. #SI-3317 Link to comment Share on other sites More sharing options...
Abhishek Dewan Posted March 28, 2023 Report Share Posted March 28, 2023 Hi @tTony In our thorough investigation, we found that 904035 error is thrown due to SSL Handshake failure between server and client. Please try the below steps when setting up sync with WebDAV - Enable Bypass SSL certificate verification checkbox: For Mac - For iOS - If the issue still persists, please create a demo account for your WebDAV with mentioned certificate enabled and DM me the URL, username and password. Link to comment Share on other sites More sharing options...
OGM Posted May 3, 2023 Report Share Posted May 3, 2023 You should also check, if your server still supports old TLS version (anything before TLS 1.3), because enpass is not capable of dealing with modern TLS version. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now