Skip to content
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

Open
2 of 3 tasks
Why-SVIP opened this issue May 12, 2024 · 16 comments
Open
2 of 3 tasks

[Bug] v2.12.2 UpStash同步问题 #4666

Why-SVIP opened this issue May 12, 2024 · 16 comments
Labels
bug Something isn't working

Comments

@Why-SVIP
Copy link

Bug Description

我使用VPS,在docker里自行部署项目,按照教程
https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web/blob/main/docs/synchronise-chat-logs-cn.md
进行UpStash同步,配置完相关REST API的参数,检查可用性是通过的,但是点击同步的时候,就显示同步失败。
我想知道 启动代理与代理地址 填写什么,是不是我没有填写代理地址的原因,我不知道应该填写说明。
{20240512131412}

Steps to Reproduce

1.配置完相关REST API的参数,检查可用性是通过的
{9EF8681B-D78C-4121-A7A3-8E055217139F}
2.点击同步的时候,就显示同步失败
20240512131248

Expected Behavior

期望能修复同步失败问题

Screenshots

No response

Deployment Method

  • Docker
  • Vercel
  • Server

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

@Why-SVIP Why-SVIP added the bug Something isn't working label May 12, 2024
@Issues-translate-bot
Copy link

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


Title: [Bug] v2.12.2 UpStash synchronization problem

@Dean-YZG
Copy link
Contributor

do you have the error screenshot of api /api/upstash/ in the console of browser dev tools

@Why-SVIP
Copy link
Author

do you have the error screenshot of api /api/upstash/ in the console of browser dev tools

image

@phengite
Copy link

本来想用 WebDAV,部署好了用 Curl 操作没问题,但是死活解决不了 CORS,折腾了 2 天用 Nginx 各种 Proxy 最后莫名其妙跳到 80 端口(WebDAV 和 NextChat 都是用 Docker 部署在同一域名下用不同端口访问),彻底崩溃。暂时放弃了等官方什么时候更新说明下自带那个「代理地址」怎么用再折腾了。

@Issues-translate-bot
Copy link

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


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.

@Why-SVIP
Copy link
Author

本来想用 WebDAV,部署好了用 Curl 操作没问题,但是死活解决不了 CORS,折腾了 2 天用 Nginx 各种 Proxy 最后莫名其妙跳到 80 端口(WebDAV 和 NextChat 都是用 Docker 部署在同一域名下用不同端口访问),彻底崩溃。暂时放弃了等官方什么时候更新说明下自带那个「代理地址」怎么用再折腾了。

新版本已经解决upstach问题了,但是不知道为什么IP+端口号就能进项目,nginx就一直报错

@Issues-translate-bot
Copy link

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


Originally I wanted to use WebDAV, and after deploying it, it worked fine with Curl, but CORS couldn't 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). Different port access), completely crashed. 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.

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.

@Dean-YZG
Copy link
Contributor

do you have the error screenshot of api /api/upstash/ in the console of browser dev tools

image

这个问题应该是由于代码中对远端数据为""空字符串的情景没有进行过滤导致的,目前,已经解决

@Dean-YZG
Copy link
Contributor

本来想用 WebDAV,部署好了用 Curl 操作没问题,但是死活解决不了 CORS,折腾了 2 天用 Nginx 各种 Proxy 最后莫名其妙跳到 80 端口(WebDAV 和 NextChat 都是用 Docker 部署在同一域名下用不同端口访问),彻底崩溃。暂时放弃了等官方什么时候更新说明下自带那个「代理地址」怎么用再折腾了。

一般来说,代理地址是不需要填写的,这个地址默认指向的是本项目自带的代理

@Issues-translate-bot
Copy link

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


Originally I wanted to use WebDAV, and after deploying it, it worked fine with Curl, but CORS couldn't 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). Different port access), completely crashed. 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.

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.

@Dean-YZG
Copy link
Contributor

本来想用 WebDAV,部署好了用 Curl 操作没问题,但是死活解决不了 CORS,折腾了 2 天用 Nginx 各种 Proxy 最后莫名其妙跳到 80 端口(WebDAV 和 NextChat 都是用 Docker 部署在同一域名下用不同端口访问),彻底崩溃。暂时放弃了等官方什么时候更新说明下自带那个「代理地址」怎么用再折腾了。

新版本已经解决upstach问题了,但是不知道为什么IP+端口号就能进项目,nginx就一直报错

有报错截图么?

@Issues-translate-bot
Copy link

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


I originally wanted to use WebDAV, and after deploying it, it worked fine with Curl, but CORS couldn't 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). Accessed using different ports), completely crashed. 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.

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.

Do you have any error screenshots?

@Why-SVIP
Copy link
Author

本来想用 WebDAV,部署好了用 Curl 操作没问题,但是死活解决不了 CORS,折腾了 2 天用 Nginx 各种 Proxy 最后莫名其妙跳到 80 端口(WebDAV 和 NextChat 都是用 Docker 部署在同一域名下用不同端口访问),彻底崩溃。暂时放弃了等官方什么时候更新说明下自带那个「代理地址」怎么用再折腾了。

新版本已经解决upstach问题了,但是不知道为什么IP+端口号就能进项目,nginx就一直报错

有报错截图么?

image

@Issues-translate-bot
Copy link

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


I originally wanted to use WebDAV, and after deploying it, it worked fine with Curl, but CORS couldn't be solved. I spent 2 days trying to use Nginx and various Proxies and finally jumped to port 80 inexplicably (WebDAV and NextChat were both deployed on the same domain name using Docker). accessed using different ports), completely crashed. 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.

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.

Do you have any error screenshots?

image

@Issues-translate-bot
Copy link

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


I originally wanted to use WebDAV, and after deploying it, it worked fine with Curl, but I couldn't solve CORS. I spent 2 days using Nginx and various Proxies and finally jumped to port 80 inexplicably (WebDAV and NextChat were both deployed on the same server using Docker). Accessed using different ports under the domain name), completely crashed. 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.

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.

Do you have any error screenshots?

![image](https://private-user-images.githubusercontent.com/56478325/333382051-3d1493fd-07b7-4500-8e7f-973562ec4bf2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3 MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTcxMjc4MTQsIm5iZiI6MTcxNzEyNzUxNCwicGF0aCI6Ii81NjQ3 ODMyNS8zMzMzODIwNTEtM2QxNDkzZmQtMDdiNy00NTAwLThlN2YtOTczNTYyZWM0YmYyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTU zUFFLNFpBJTJGMjAyNDA1MzElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNTMxVDAzNTE1NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlP TM3MmU3ODk3OGZlOTVjNzhjM2IxNzg1NWFmMjkzZDlmMGQxYTY3NDg5NTQwMDMyMGNlMDdhYzRhM jEwMjM2MDkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb 19pZD0wIn0.dK1wycOVfonvfPnXTkHhWZghrBOaz6IMKe508NT_6AY)

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.

@Why-SVIP
Copy link
Author

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

I originally wanted to use WebDAV, and after deploying it, it worked fine with Curl, but I couldn't solve CORS. I spent 2 days using Nginx and various Proxies and finally jumped to port 80 inexplicably (WebDAV and NextChat were both deployed on the same server using Docker). Accessed using different ports under the domain name), completely crashed. 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.

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.

Do you have any error screenshots?

![image](https://private-user-images.githubusercontent.com/56478325/333382051-3d1493fd-07b7-4500-8e7f-973562ec4bf2.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3 MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTcxMjc4MTQsIm5iZiI6MTcxNzEyNzUxNCwicGF0aCI6Ii81NjQ3 ODMyNS8zMzMzODIwNTEtM2QxNDkzZmQtMDdiNy00NTAwLThlN2YtOTczNTYyZWM0YmYyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTU zUFFLNFpBJTJGMjAyNDA1MzElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNTMxVDAzNTE1NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlP TM3MmU3ODk3OGZlOTVjNzhjM2IxNzg1NWFmMjkzZDlmMGQxYTY3NDg5NTQwMDMyMGNlMDdhYzRhM jEwMjM2MDkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb 19pZD0wIn0.dK1wycOVfonvfPnXTkHhWZghrBOaz6IMKe508NT_6AY)

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试一试

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants