Errors
404 - instance / endpoint not found
What happened
The requested instance address or identifier cannot be found. A saved URL may refer to a deleted, incorrect or unfinished instance.
- Check the target instanceConfirm it exists and is ready.
- Copy its connection detailsUse the address shown by the Connect instructions.
- Update and verifyCorrect the application configuration and check the connection.
Request that triggers it
A request to a hostname that doesn't belong to any tenant.
curl -X POST "https://nope.db.originchain.ai/v1/tenants/$OC_TENANT/sql" \
-H "Authorization: Bearer $OC_TOKEN" \
-H "Content-Type: application/json" \
-d '{"sql": "SELECT id FROM shop.products LIMIT 1"}'Read the response
{
"error": "not_found",
"message": "no instance is provisioned at this endpoint",
"retry": false
}Fix the request
- Copy the current connection details from the console.
- Check the selected instance and its provisioning state.
- Update the application’s configuration.
- Retry against that instance.
Keep in mind: Keep the provided address intact instead of guessing or removing path segments.
Common causes
- Typo in the instance subdomain.
- A copied instance address that differs from the connection details shown in the console.
- Instance was destroyed; the env var still points at the old endpoint.
- Pre-launch hostname queued in DNS but provisioning hasn't completed yet.
- Calling
/api/v1instead of/v1, or a roadmap endpoint that hasn't shipped.
Continue
See error handling and retries, or return to error examples.