mirror of https://github.com/ospab/ostp.git
ospab
a1c146aff3
A relay configured with upstream_api_url = "http://HOST:9090" fails every key sync with a bare "API returned HTTP 404", which reads like the server is down or the token is wrong. Neither is true: the management API is nested under the target server's api.webpath (create_api_router mounts it at "/{webpath}/api"), because that secret segment is what keeps the panel from being discoverable by scanners. A bare host:port therefore resolves to a route that does not exist and the token is never even looked at. Nothing said so — the config template, the wizard prompt and the shipped example all suggested exactly the host:port form that cannot work. - sync_keys now reports the full URL and, for 404 specifically, states that the webpath must be included and what the URL should look like. 401 is called out separately as a token mismatch, since the two are otherwise indistinguishable from the log. - The relay config template, the shipped example and the wizard prompt now show the path-bearing form, and the wizard warns when the URL entered has no path segment rather than letting it fail later. Docs under docs/ and the wiki are being rewritten concurrently and are left alone here. |
||
|---|---|---|
| .. | ||
| en | ||
| ru | ||
| banner.txt | ||
| relay-config-example.json | ||