-
Notifications
You must be signed in to change notification settings - Fork 57.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] 部署的时候环境变量设置了APIKEY和code,进入网站提示未设置,在settings页面设置了CODE,打开网页没有出现密码验证 #4437
Comments
Title: [Bug] When deploying, the environment variables APIKEY and code are set. When entering the website, it prompts that they are not set. CODE is set on the settings page. When opening the web page, password verification does not appear. |
vercel中redeploy试试 |
Try redeploy in vercel |
The same problem occurred. On my side, the CODE settings took effect, but the KEY and proxy did not take effect. |
@mengluo04 cannot reproduce this issue. if you send message in chat did the app response letting user to set code? |
I do it now,but also not work right |
I delete the project ,and create project,before deloy,i set the env |
…… |
… |
无痕模式一样的,没有出现code验证页面,换浏览器也一样 |
你要点登录,然后再登录页面输入你的code,本身是不会跳出来密码验证 |
You click to log in, and then enter your code on the login page. The password verification will not pop up. |
如果设置了CODE 环境变量,则会强制提示验证信息,除非曾经在『设置』中输入过 任意服务提供商的apikey |
If the CODE environment variable is set, verification information will be forced to be prompted unless the apikey of any service provider has been entered in "Settings" |
Bug Description
在vercel上部署,部署的时候环境变量设置了APIKEY和code,进入网站提示未设置,在settings页面设置了CODE,打开网页没有出现密码验证
Steps to Reproduce
1、fork项目
2、在vercel新建
3、选择fork的项目
4、设置环境变量
5、部署
6、进入页面
7、页面提示没有设置apikey和code
8、设置之后刷新或者新开页面没有弹出密码框
Expected Behavior
正常进行页面密码验证
Screenshots
No response
Deployment Method
Desktop OS
No response
Desktop Browser
No response
Desktop Browser Version
No response
Smartphone Device
No response
Smartphone OS
No response
Smartphone Browser
No response
Smartphone Browser Version
No response
Additional Logs
No response
The text was updated successfully, but these errors were encountered: