Skip to content
Deckloud
Guides

Fix the Nextcloud self-signed certificate error on iPhone.

A server that works in your desktop browser can still fail on iPhone, where apps accept only certificates the system trusts.

Last checked:

Why the browser works and the app fails

Your desktop browser remembers the warning you once accepted. iOS apps need a complete chain, a matching hostname, and valid dates, so a bare self-signed certificate fails before any Deck data loads.

Best fix: a Let's Encrypt certificate

A free Let's Encrypt certificate on a public hostname works on every device without setup. For a server that stays off the internet, use the DNS-01 challenge. Your reverse proxy (Caddy, Traefik, Nginx Proxy Manager) then proves domain ownership through your DNS provider.

If you must keep a private certificate authority

Install your CA's root certificate under Settings, General, VPN & Device Management. Then turn on full trust under Settings, General, About, Certificate Trust Settings; most people miss this step. The server certificate must come from that CA and match the hostname you type into the app.

Checks before blaming the certificate

Open the server URL in Safari on the iPhone. Its error names the broken rule: untrusted issuer, hostname mismatch, or expired. A lock icon means the certificate is fine; check DNS or reachability instead.

Questions

Can Deckloud just ignore certificate errors?

Not on iPhone or iPad. A local server without HTTPS can use plain http://, such as http://192.168.1.20:8080. The desktop app has an Allow self-signed certificates setting.

Does Let's Encrypt work for a LAN-only server?

Yes, with the DNS-01 challenge and a domain at a DNS provider with an API. The server can stay unreachable from the internet.

Why did it stop working after months of working?

Certificates expire, and private ones are easy to forget. Check the expiry date in Safari first.

Need help?

Write to support@deckloud.com and describe what you see.