[Bug] API key 无法在ChatGPT-Next-Web中使用

[zip8919]

Describe the bug
A clear and concise description of what the bug is.
API key在其他项目能使用，这个项目就不能
输入正确的访问密码提示访问密码不正确或为空
使用vercel自定义域名不能打开，显示“将您重定向的次数过多。”，使用cloudflare worker反向代理可以打开

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Deployment

• Docker
• Vercel
• Server

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional Logs
Add any logs about the problem here.
{
"error": {
"message": "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.",
"type": "invalid_request_error",
"param": null,
"code": null
}
}

{
"error": {
"message": "We could not parse the JSON body of your request. (HINT: This likely means you aren't using your HTTP library correctly. The OpenAI API expects a JSON payload, but what was sent was not valid JSON. If you have trouble figuring out how to fix this, please contact us through our help center at help.openai.com.)",
"type": "invalid_request_error",
"param": null,
"code": null
}
}

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: [Bug] API key cannot be used in ChatGPT-Next-Web

[QAbot-zh]

部署的时候接口地址配了吗

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Was the interface address configured during deployment?

[fred-bf]

Its more like your deployment issue, you should be able to directly access via your vercel deployment url