sync: tell the user which address their server got wrong

Two gaps left by fc7e520, both found in review. The claimed path was kept when the claimed host was replaced, though both come from the generator we had just decided not to trust. A subdirectory install behind a proxy reports an empty webroot from inside the container, so /nextcloud was dropped and discovery ran against the wrong base -- the same dead end, one level down. The origin is now rebuilt entirely from the poll endpoint, whose own prefix is whatever precedes index.php/login/v2/poll. And the mismatch rode out of poll() with nowhere to go. It is carried on the state rather than the step, because it is learned during the browser step while the setting it blames is what the user has to go and fix afterwards -- so it has to outlive the step that discovered it.
2026-09-07 22:09:17 +02:00
parent 3a9f623d2a
commit 730a1eb88d
6 changed files with 104 additions and 11 deletions
@@ -355,6 +355,7 @@
    <string name="add_account_browser_reopen">Open the browser again</string>
    <string name="add_account_browser_use_password">Use a password instead</string>
    <string name="add_account_browser_host_mismatch">The server sent us to %1$s, but you typed %2$s. That usually means its overwrite.cli.url setting is wrong.</string>
+    <string name="add_account_origin_mismatch">The server reported its address as %1$s, which this device cannot reach, so %2$s was used instead. Its overwrite.cli.url or trusted_proxies setting is probably wrong.</string>

    <string name="add_account_lists_title">Which lists should sync?</string>
    <string name="add_account_lists_read_only">Read-only</string>