The API rejects the token
Section titled “The API rejects the token”- Confirm the header starts with
Bearerand contains no quotes. - Check that the secret belongs to the intended LTESocks account.
- If the token was reset in the dashboard, replace every deployed copy.
- Test with the read-only
GET /useroperation.
A request fails before reaching the operation
Section titled “A request fails before reaching the operation”Remove Accept-Language or set it to a supported locale such as en. Verify Content-Type: application/json and validate the JSON syntax.
A port cannot be found
Section titled “A port cannot be found”Port identifiers are scoped to the authenticated account. List ports for that account and compare the exact identifier. Do not use a port number, reset token, or plan identifier where {id} is required unless the reference explicitly says so.
Requests receive 429
Section titled “Requests receive 429”Reduce concurrency, use larger pages, and retry after exponential backoff with jitter. Defaults are lower for mutating methods than for GET requests.
VPN response cannot be parsed
Section titled “VPN response cannot be parsed”VPN operations return a binary archive. Do not call response.json(). Stream the body to a protected file, check status and Content-Type, then validate the archive before use.
A mutating request timed out
Section titled “A mutating request timed out”Do not immediately repeat it. Read the affected port or payment history to determine whether the first request succeeded, then choose whether a retry is safe.
When contacting support, include the UTC time, method, path template, HTTP status, and a sanitized response. Never include the bearer token, full credentials, or VPN archive.