v0.1.4

docs/TROUBLESHOOTING.md

@@ -50,3 +50,20 @@ address requires `ACTIVE_PUSH_ALLOW_REMOTE_ADMIN=true` (preferably with TLS). Lo
 
 CLI commands must run as the service user so database files keep the right owner:
 `sudo -u active-push active-push ...`.
+
+## iPhone still asks for the server address
+
+iOS only runs Autodiscover when it can reach it for the **domain of the e-mail address**. It tries, in order,
+`https://<domain>/autodiscover/autodiscover.xml`, `https://autodiscover.<domain>/autodiscover/autodiscover.xml`
+and the DNS SRV record `_autodiscover._tcp.<domain>`; a failure is silent and the phone shows the manual
+"Server" field. Run the diagnostics on the **Autodiscover** page first (it checks DNS, SRV and every endpoint). Then open **Live** while adding the account:
+
+| What you see | Meaning / fix |
+|---|---|
+| nothing at all | the request never reaches ActivePush: no DNS record for `autodiscover.<domain>`, a certificate that does not cover that name, or no nginx `server_name` / locations for it. Add the name to the certificate and the three `location` blocks (see `deploy/nginx-active-push.conf`) |
+| `401 auth required`, then nothing | iOS did not accept the answer or the TLS certificate; check the certificate chain with a browser |
+| `503 backend unavailable` | IMAP login check failed, see Logs |
+| `200 ok (host)` but the phone still asks | the returned URL is built from the host the request arrived on (e.g. `autodiscover.example.com`); set **Autodiscover -> Public ActiveSync URL** to the public ActiveSync URL that has a valid certificate |
+
+The e-mail address typed on the phone must be a full address (`user@domain`); the login is derived from it
+according to the **Login** settings.