> ## Documentation Index
> Fetch the complete documentation index at: https://apione.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Network, proxy, and connection troubleshooting

> Diagnose connection failures in the order: network, URL, authentication, model, and request body.

"Connection failure" can occur in the local network, proxy, DNS, TLS, endpoint address, authentication, or upstream model. Check from near to far, avoiding multiple configuration changes at once.

## Troubleshooting order

```text theme={null}
your application → local network/proxy → DNS/TLS → APIONE gateway → model route
```

### 1. Check domain and HTTPS

API requests should go to `https://api.apione.ai`. The console `https://apione.ai/en/app` is for account management, not an API Base URL.

```bash theme={null}
curl -I --connect-timeout 10 https://api.apione.ai
```

As long as TLS can be established and an HTTP response is returned, the basic network has reached the gateway; the status code does not have to be 200.

### 2. Verify authentication with the model list

```bash theme={null}
curl -sS --connect-timeout 10 --max-time 30 \
  https://api.apione.ai/v1/models \
  -H "Authorization: Bearer YOUR_APIONE_API_KEY"
```

After the model list succeeds, test the specific generation endpoint. This separates network/key issues from model parameter issues.

### 3. Compare cURL with the client

If cURL succeeds but the client fails, check the client's actual Base URL, proxy, environment variables, and protocol. Pay special attention to duplicate `/v1`, automatically appended endpoints, old configuration caches, and system proxies not inherited by the client.

## Common symptoms

| Symptom | Likely location | Check |
| - | - | - |
| DNS resolution failure | DNS, local network | System DNS, corporate network, domain spelling |
| Connection timeout | Proxy, firewall, routing | Proxy rules, egress policy, connection timeout |
| TLS/certificate error | System time, certificate chain, middle proxy | System time, root certificates, HTTPS inspection device |
| HTML returned | Wrong address or login page takeover | Whether the console URL was mistakenly used |
| 401/403 | Key, permission, proxy stripping headers | Key status and `Authorization` header |
| 404 | Base URL and endpoint concatenation error | Whether `/v1` is duplicated or missing |
| 429 | Concurrency, quota, or upstream rate limit | `Retry-After`, concurrency, and console usage |

## Proxy notes

* Clarify whether the proxy is system-level, terminal-level, or browser-extension-only.
* Do not write the API Key into the proxy URL, public logs, or screenshots.
* Corporate HTTPS inspection may replace certificates; the network administrator should provide a compliant certificate. Do not disable certificate verification long-term.
* After routing rules change, restart the actual client making the requests.

## Collect diagnostic information

When submitting to support: occurrence time and time zone, domain and endpoint, client version, network environment, HTTP status, redacted error, and request ID. Do not submit the full key, cookies, full prompts, or raw customer files.

Next: [Errors and troubleshooting](https://apione.ai/docs/en/support/errors.md), [Addresses and authentication](https://apione.ai/docs/en/api/overview.md), [Request tracking](https://apione.ai/docs/en/api/request-reliability.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.