Since: v1.7.0
Status: β
Supported
Simple Notes Sync now supports connecting to WebDAV servers with self-signed SSL certificates, such as:
- ownCloud/Nextcloud with self-signed certificates
- Synology NAS with default certificates
- Raspberry Pi or home servers
- Internal corporate servers with private CAs
On your server:
- Locate your certificate file (usually
.crt,.pem, or.derformat) - If you created the certificate yourself, you already have it
- For Synology NAS: Control Panel β Security β Certificate β Export
- For ownCloud/Nextcloud: Usually in
/etc/ssl/certs/on the server
On your Android device:
-
Transfer the
.crtor.pemfile to your phone (via email, USB, etc.) -
Open Settings β Security β More security settings (or Encryption & credentials)
-
Install from storage / "Install a certificate"
- Choose "CA certificate"
- Warning: Android will display a security warning. This is normal.
- Tap "Install anyway"
-
Browse to your certificate file and select it
-
Name it something recognizable (e.g., "My ownCloud CA")
-
β Done! The certificate is now trusted system-wide
- Open Simple Notes Sync
- Go to Settings β Server Settings
- Enter your
https://server URL as usual - The app will now trust your self-signed certificate β
- Installing a CA certificate grants trust to all certificates signed by that CA
- Only install certificates from sources you trust
- Android will warn you before installation β read the warning carefully
- You manually install the certificate (conscious decision)
- The app uses Android's native trust store (no custom validation)
- You can remove the certificate anytime from Android Settings
- F-Droid and Google Play compliant (no "trust all" hack)
Problem: App still shows SSL error after installing certificate
Solutions:
- Verify installation: Settings β Security β Trusted credentials β User tab
- Check certificate type: Must be a CA certificate, not a server certificate
- Restart app: Close and reopen Simple Notes Sync
- Check URL: Must use
https://(nothttp://)
Problem: Android 7+ restricts user certificates for apps
Solution: This app is configured to trust user certificates β
If the problem persists, check:
- Certificate is installed in "User" tab (not "System")
- Certificate is not expired
- Server URL matches certificate's Common Name (CN) or Subject Alternative Name (SAN)
| Type | Installation Required | Security |
|---|---|---|
| Self-Signed | β Yes | Manual trust |
| Let's Encrypt | β No | Automatic |
| Private CA | β Yes (CA root) | Automatic for all CA-signed certs |
If your server is publicly accessible, consider using Let's Encrypt for free, automatically-renewed SSL certificates:
- No manual certificate installation needed
- Trusted by all devices automatically
- Easier for end users
Setup guides:
- Uses Android's Network Security Config
- Trusts both system and user CA certificates
- No custom TrustManager or hostname verifier
- F-Droid and Play Store compliant
File: android/app/src/main/res/xml/network_security_config.xml
<base-config>
<trust-anchors>
<certificates src="system" />
<certificates src="user" /> <!-- β Enables self-signed support -->
</trust-anchors>
</base-config>Q: Do I need to reinstall the certificate after app updates?
A: No, certificates are stored system-wide, not per-app.
Q: Can I use the same certificate for multiple apps?
A: Yes, once installed, it works for all apps that trust user certificates.
Q: How do I remove a certificate?
A: Settings β Security β Trusted credentials β User tab β Tap certificate β Remove
Q: Does this work on Android 14+?
A: Yes, tested on Android 7 through 15 (API 24-35).
- GitHub Issue #X - User request for ownCloud support
- Feature Analysis - Technical analysis
Need help? Open an issue on GitHub