THUDM / THUDM/slime

request sglang server,{api_key} how to config?

Open
#703 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
8.5k
Forks
1.3k
Avg merge
5h 36m
Merged PRs (30d)
22

Description

after sglang server init,enter while true loop and always print http://{self.server_host}:{self.server_port}/health_generate , and reponse is 403,
sglangServer's api_key=None, so how do I set the {api_key}

Image

log print:
(SGLangEngine pid=11240) requests.Session first true loop start, url: http://xxxxx:10000/health_generate, retryTime:298
(SGLangEngine pid=11240) requests.Session first true loop reponse, <Response [403]>
(SGLangEngine pid=11240) requests.Session first true loop start, url: http://xxxxx:10000/health_generate, retryTime:299
(SGLangEngine pid=11240) requests.Session first true loop reponse, <Response [403]>
@zhuzilin

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing SGLangServer initialization and the request to /health_generate, focusing on how api_key=None is handled. Confirm where authentication is configured and how the health request supplies it. Done means the server can initialize and the health endpoint no longer returns 403 with the documented configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.