Troubleshooting: API Endpoints Not Visible in Astra Dashboard After Sending Requests via Proxy
Last updated: August 13, 2025
Symptoms
You've configured your API client (e.g., Hoppscotch, Postman, or cURL) to send requests through the astra-proxy-service, but you're not seeing any API endpoints in the Astra dashboard or inventory after firing the requests in your API Client.
Common Causes and Fixes
Requests Do Not Return 2XX or 3XX Status Codes
Cause:
Astra Proxy only logs API traffic that results in a successful response — specifically, HTTP 2XX or 3XX. Requests resulting in errors (4XX or 5XX) are not captured.
✅ Solution:
Check the response status code in your API client. Ensure the request returns a successful response (200 OK, 201 Created, 302 Found, etc.).
API Domain Not Listed in ALLOWED_HOSTS
Cause:
The proxy ignores traffic to domains not explicitly allowed.
✅ Solution:
Find the domain in your request URL (e.g., in https://api.mydomain.com/v1/..., the domain is api.mydomain.com).
Ensure it is added to the ALLOWED_HOSTS entry in your env.env file.
Missing or Incorrect env.env Configuration
Cause:
Your proxy might be misconfigured due to missing or incorrect environment variables.
✅ Solution:
Verify that your env.env file includes the following values:
SENSOR_IDALLOWED_HOSTSCOLLECTOR_IDCLIENT_IDCLIENT_SECRET
You can validate the configuration using:
./astra-cli validate -e env.envBest Practices
Use any API client that supports setting a proxy (Hoppscotch, Postman, curl, etc.).
Ensure the proxy settings are correctly applied for HTTPS requests.
Validate that your API client isn't bypassing the proxy due to direct DNS resolution or local caching.
Send a few successful (2XX/3XX) requests and check Astra dashboard after a short delay.