Outbound HTTPS requests from my server to api.groq.com return 404 Not Found

Posted by user_xha71p in bugs.

Hello Wispbyte Support, My Discord bot (Python, aiohttp) runs on your hosting. Since 19 Nov 2026 (about 08:56 in the console timestamps), every outbound request from my server to Groq's API fails with HTTP 404, even a simple key check call. The same code and key are correct, so I suspect something on the network side of the host (outbound filtering, a proxy, DNS, or an IP block). What I see in my server console: 1. GET https://api.groq.com/openai/v1/models 404, server=cloudflare, content type=application/json, body={"error":{"message":"Not Found"}} 2. POST https://api.groq.com/openai/v1/chat/completions (model openai/gpt oss 120b) HTTP 404 Not Found Why I think this is not my code or key: The URL is Groq's documented endpoint and base path. GET /openai/v1/models is the simplest authenticated call and normally returns 200 with a valid key. A wrong model name or request body cannot cause a 404 there. A bad API key normally returns 401, not 404. What I need from you: 1. Please check whether outbound connections from my server to api.groq.com (HTTPS, port 443) are blocked, filtered, proxied or rewritten. 2. Please check whether my server's outgoing IP address is blocked or rate limited by Cloudflare or Groq, and whether another IP or node is available. 3. If you can, run this from my server's console or container and tell me the result: curl i https://api.groq.com/openai/v1/models H "Authorization: Bearer <my key " (Expected: 200 with a JSON list of models. I am getting 404.) 4. If outbound access to this domain is restricted on my plan, please tell me which domains are allowed. I can send more console logs or my server ID if that helps. Thank you for your help. Kind regards

Replies

Byte (AI assistant)

This doesn’t look like outbound HTTPS being blocked: the request reaches a server and gets an HTTP 404 response. A blocked connection would more typically time out or fail DNS/TLS; a Cloudflare branded 404 points more toward the URL or an API side routing issue than a blocked port. 1. Check the URL your code builds at runtime. For the OpenAI compatible API, the base URL should be ; make sure isn’t being added twice. 2. Try the exact same request from another network. Don’t share your API key. 3. If it still returns 404, compare the sanitized response headers and exact URL with Groq’s API reference. Include any header and the timestamp when contacting Groq. The 404 alone isn’t evidence that your server’s outgoing IP is blocked.

Related discussions

Wispbyte Community Forum