API connectivity diagnostics — 2026-11-03

API Base URL: https://codex-free.com/v1
Probe request: GET https://codex-free.com/v1/models
DNS: codex-free.com -> 94.232.46.134
System DNS and Google DNS-over-HTTPS returned the same IPv4 address.

From the speaker, Go HTTP client:
Get "https://codex-free.com/v1/models": dial tcp 94.232.46.134:443: connect: no route to host

From Windows, Python HTTPS client:
URLError: <urlopen error [SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1081)>

From Windows, Python HTTPS client restricted to TLS 1.2:
URLError: <urlopen error _ssl.c:1063: The handshake operation timed out>

From Windows, curl, HTTPS root without credentials:
curl: (28) Connection timed out after 8009 milliseconds

No HTTP response from the provider was received. Authentication, quota and model availability could not be tested. The speaker's local management panel returns HTTP 502 to report its outbound connection error; this 502 is not an HTTP status received from the provider.

Please confirm that 94.232.46.134:443 is serving this API, whether any source-IP or regional restrictions apply, and whether there is another working base URL.

This report intentionally contains no API key.

Additional checks:
- Windows route selection for 94.232.46.134 uses the happ-xray interface.
- The speaker has a default route over wlan0 through 192.168.3.1.
- Explicit HTTPS CONNECT through the existing Happ HTTP proxy at 127.0.0.1:10809 also timed out during TLS handshake, both for the API and the management page.
- A credential-free curl HTTPS request bound to the Ethernet IPv4 address timed out after 6009 ms. Binding an address alone does not prove that all VPN routing rules were bypassed.

The user separately reports receiving "exceed quota" on an earlier request. We have not reproduced that response and do not yet have its HTTP status, full JSON, model ID or client details. That earlier response means the API was reachable at that time. The current network failures do not establish that the key is invalid, nor conclusively assign fault to the provider, VPN, local network or ISP.
