[Bug] 网页页面卡在“用户状态初始化”

[C-Dragon8]

📦 部署环境

Vercel

📌 软件版本

1.38.0

💻 系统环境

Windows, macOS, iOS

🌐 浏览器

Chrome, Edge, Safari

🐛 问题描述

Vecel部署v1.37.0-1.38.0各版本均遇到此问题，网页显示如下：

身份认证采用Cloudflare Zero Trust，不清楚问题原因。

📷 复现步骤

Vecel部署v1.37.0-1.38.0各版本均遇到此问题。

🚦 期望结果

期待问题的解决方案。

📝 补充信息

No response

[lobehubbot]

👀 @C-Dragon8

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

[C-Dragon8]

网页卡在了上述页面“用户状态初始化”状态。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

The web page is stuck in the "User Status Initialization" state of the above page.

[dosubot]

Hey @C-Dragon8, I'm here to help you with any bugs, questions, or contributions. Let's tackle this together!

I found a similar closed issue related to deployment on Vercel, which might be relevant to your problem. The issue titled "[Question] 在Vercel上部署118.1之后报错，无法正常打开页面" was resolved by pinning the antd version to fix a chat page crash ^[1].

For your specific issue with the "User status initializing..." message, ensure that your Cloudflare Zero Trust configuration is correct. Verify that the environment variables for authentication are set properly, as incorrect settings can lead to initialization issues. Additionally, check the database connection and ensure that all required environment variables for Vercel deployment are correctly configured, including those for the database, authentication, and any external services ^[2][3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[arvinxx]

@C-Dragon8 是服务端版本吗？还是客户端版本

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

@C-Dragon8 Is it the server version? Or client version

[C-Dragon8]

@C-Dragon8 是服务端版本吗？还是客户端版本

不清楚您说的服务端版本还是客户端版本具体指哪个，我fork的就是这个分支forked from https://github.com/lobehub/lobe-chat
目前，版本v1.39.0版本依然存在此问题。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

@C-Dragon8 Is it the server version? Or client version

I'm not sure which one you are referring to, the server version or the client version. This is the branch I forked from https://github.com/lobehub/lobe-chat
Currently, this problem still exists in version v1.39.0.

[arvinxx]

@C-Dragon8 你怎么部署的，有没有用到数据库

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

@C-Dragon8 How did you deploy it? Did you use a database?

[C-Dragon8]

@C-Dragon8 你怎么部署的，有没有用到数据库

我用Vercel关联GitHub的库进行部署，配置的环境变量有OPENAI_MODEL_LIST、AU_CLOUDFLARE_ZERO_TRUST_ISSUER、AU_CLOUDFLARE_ZERO_TRUST_CLIENT_SECRET、AU_CLOUDFLARE_ZERO_TRUST_CLIENT_ID、NEXT_AUTH_SECRET、NEXT_AUTH_SSO_PROVIDERS、NEXTAUTH_URL、MOONSHOT_API_KEY、ANTHROPIC_PROXY_URL、ANTHROPIC_API_KEY、GOOGLE_PROXY_URL、GOOGLE_API_KEY、ACCESS_CODE，仔细核对过，环境变量并未做过什么改动，v1.37.0前的版本没有遇到过这类问题。印象中自动部署完，从v1.37.0就开始了，更换不同的设备、浏览器都是这样的。

没有用到数据库。

刚刚自动部署的v1.39.1版本，此问题依然存在。

[lobehubbot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

@C-Dragon8 How did you deploy it? Did you use a database?

I use Vercel to associate the GitHub library for deployment. The configured environment variables are OPENAI_MODEL_LIST, AU_CLOUDFLARE_ZERO_TRUST_ISSUER, AU_CLOUDFLARE_ZERO_TRUST_CLIENT_SECRET, AU_CLOUDFLARE_ZERO_TRUST_CLIENT_ID, NEXT_AUTH_SECRET, NE XT_AUTH_SSO_PROVIDERS, NEXTAUTH_URL, MOONSHOT_API_KEY, ANTHROPIC_PROXY_URL, ANTHROPIC_API_KEY, GOOGLE_PROXY_URL, GOOGLE_API_KEY, ACCESS_CODE. After careful checking, the environment variables have not been changed. Versions before v1.37.0 have not encountered this kind of problem. In my impression, automatic deployment has been completed since v1.37.0. This is the case when changing different devices and browsers.

No database is used.

This problem still exists in the v1.39.1 version that was just automatically deployed.