-
Notifications
You must be signed in to change notification settings - Fork 56.8k
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] v2.12.2 UpStash同步问题 #4666
Comments
Title: [Bug] v2.12.2 UpStash synchronization problem |
do you have the error screenshot of api |
本来想用 WebDAV,部署好了用 Curl 操作没问题,但是死活解决不了 CORS,折腾了 2 天用 Nginx 各种 Proxy 最后莫名其妙跳到 80 端口(WebDAV 和 NextChat 都是用 Docker 部署在同一域名下用不同端口访问),彻底崩溃。暂时放弃了等官方什么时候更新说明下自带那个「代理地址」怎么用再折腾了。 |
I originally wanted to use WebDAV, and after deploying it, it worked fine with Curl, but CORS could not be solved. I spent 2 days using Nginx and various Proxies and finally jumped to port 80 inexplicably (WebDAV and NextChat were deployed under the same domain name using Docker and using different port access), a complete crash. For the time being, I have given up waiting for the official update to explain how to use the "proxy address" that comes with it. |
新版本已经解决upstach问题了,但是不知道为什么IP+端口号就能进项目,nginx就一直报错 |
The new version has solved the upstach problem, but I don’t know why IP + port number can enter the project, but nginx keeps reporting errors. |
一般来说,代理地址是不需要填写的,这个地址默认指向的是本项目自带的代理 |
Generally speaking, the proxy address does not need to be filled in. By default, this address points to the proxy that comes with this project. |
有报错截图么? |
Do you have any error screenshots? |
|
Are you using nightly? I also had this problem when using nightly before, but later I switched to the regular version and it was fine. |
我用的vestacp面板自动安装的,我感觉是vestacp的问题,我想重装系统然后只安装nginx试一试 |
Bug Description
我使用VPS,在docker里自行部署项目,按照教程
https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web/blob/main/docs/synchronise-chat-logs-cn.md
进行UpStash同步,配置完相关REST API的参数,检查可用性是通过的,但是点击同步的时候,就显示同步失败。
我想知道 启动代理与代理地址 填写什么,是不是我没有填写代理地址的原因,我不知道应该填写说明。
Steps to Reproduce
1.配置完相关REST API的参数,检查可用性是通过的
2.点击同步的时候,就显示同步失败
Expected Behavior
期望能修复同步失败问题
Screenshots
No response
Deployment Method
Desktop OS
Windows11
Desktop Browser
Chrome
Desktop Browser Version
No response
Smartphone Device
iPhone 13Pro
Smartphone OS
iOS 17.5
Smartphone Browser
Safari
Smartphone Browser Version
No response
Additional Logs
No response
The text was updated successfully, but these errors were encountered: