Symptoms

You have configured your API client (such as Hoppscotch, Postman, or cURL) to send requests through the Astra Proxy Service, but no API endpoints are appearing in the Astra dashboard or inventory.

Common Causes and Fixes

Requests are not returning 2XX or 3XX status codes Astra Proxy only captures traffic that results in a successful response. Requests returning 4XX or 5XX errors are not logged.

Check the response status code in your API client and ensure requests are returning successful responses such as 200 OK, 201 Created, or 302 Found before expecting them to appear in the dashboard.

API domain is not listed in ALLOWED_HOSTS The proxy ignores traffic to domains that are not explicitly permitted.

Find the domain from your request URL — for example, in https://api.mydomain.com/v1/..., the domain is api.mydomain.com. Add it to the ALLOWED_HOSTS entry in your env.env file.

Missing or incorrect env.env configuration A misconfigured environment file will prevent the proxy from functioning correctly.

Verify that your env.env file contains all of the following values: SENSOR_ID, ALLOWED_HOSTS, COLLECTOR_ID, CLIENT_ID, and CLIENT_SECRET. You can validate the file using the Astra CLI:

./astra-cli validate -e env.env

Best 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.