Suanlimao
← Back to all tutorials

Troubleshooting & security

Can't connect, broken streams, which address to use

A step-by-step check for requests that do not go out, time out or break mid-stream.

About 6 minFor:Anyone with connection problems

Before you start

  • A terminal
  • Your key in an environment variable

Step 1 · STEP 0x01

Use curl to tell which side the problem is on

terminal
$ curl -i https://api.suanlimao.shop/v1/models -H "Authorization: Bearer <YOUR_API_KEY>"HTTP/2 200…
  • curl works but the tool does not: the problem is in the tool's settings (address, /v1, model name). Check its tutorial.
  • curl fails too: continue with network and address below.
Replace <YOUR_API_KEY> with your key (never paste it where others can see).

Step 2 · STEP 0x02

Try the other address

terminal
$ time curl -sS -o /dev/null https://api.suanlimao.shop/v1/models -H "Authorization: Bearer <YOUR_API_KEY>"$ time curl -sS -o /dev/null https://api.suanlimao.shop/v1/models -H "Authorization: Bearer <YOUR_API_KEY>"real    0m0.4s(时间越短越好;其中一个失败就用另一个)
  • The Chinese interface lists the accelerated address first because it is steadier from mainland China; if it fails switch to the alternative Cloudflare domain.
  • The English interface only shows the Cloudflare domain.
  • The API keys page and each share page list every available address.
If one domain is blocked you only change the address in your tool — no new key, no new top-up.

Step 3 · STEP 0x03

Check your own network

  • With a proxy or VPN on, try adding our domain to the direct (bypass) rules — system proxies can slow or cut long connections.
  • A corporate network may block unfamiliar domains — compare using a phone hotspot.
  • A certificate error in curl usually means a wrong system clock or HTTPS inspection on your network.

Check the status page too: it shows success rate and time to first byte per model over the last 90 minutes, 24 hours and 7 days.

Open the model plaza →

Step 4 · STEP 0x04

A stream breaks midway

terminal
data: {"choices":[{"delta":{"content":"…"}}]}: ping(突然没有后续了)
  • : ping is a keep-alive heartbeat from us, not an error — your client should ignore it.
  • Raise the client's read timeout (long answers and reasoning models can take minutes); avoid a short overall timeout on streaming requests.
  • If a gateway or reverse proxy in between buffers responses, the stream stalls in blocks — turn buffering off (e.g. proxy_buffering off in nginx).
  • When a stream is cut, the tokens already generated are billed.
Long requests through Cloudflare can occasionally be cut by the intermediary (typically a 524). Prefer streaming, or switch to the accelerated address.

✓ How to tell it worked

  • curl returns 200, your tool chats normally and streams end with [DONE].

FAQ

It just spins.

It may just be a long answer; streaming shows immediately whether content is arriving. Then compare with curl above.

I tried everything.

Open a ticket with the curl output (without the key), the time and your network (ISP or corporate).

Related tutorials

Still stuck?

Read the troubleshooting tutorials first. If that does not help, open a ticket with the request_id, time, model and the exact error (never paste your key).