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] webDav.UpStash云端同步失败 #4563

Open
1 of 3 tasks
cacosub7 opened this issue Apr 24, 2024 · 16 comments · May be fixed by #4610
Open
1 of 3 tasks

[Bug] webDav.UpStash云端同步失败 #4563

cacosub7 opened this issue Apr 24, 2024 · 16 comments · May be fixed by #4610
Labels
bug Something isn't working

Comments

@cacosub7
Copy link

Bug Description

在使用正确的坚果云WebDav / UpStash配置后,检查可用性看上去没问题,但是点击同步后均失败

WebDav

看上去跨域直接报错了,如果要配置这个代理的话 具体教程/参考有么
image

UpStash

chatnextweb的前端代码没有响应这个重定向吗?
image
image

Steps to Reproduce

如题

Expected Behavior

保存正确的WevDav/UpStash 配置后能够正常访问

Screenshots

No response

Deployment Method

  • Docker
  • Vercel
  • Server

Desktop OS

No response

Desktop Browser

Chrome

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

@cacosub7 cacosub7 added the bug Something isn't working label Apr 24, 2024
@Issues-translate-bot
Copy link

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


Title: [Bug] webDav.UpStash cloud synchronization failed

@cacosub7
Copy link
Author

Durrent version

2.11.3

@Issues-translate-bot
Copy link

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


Current version

2.11.3

@Dean-YZG
Copy link
Contributor

使用的是最新版本么?nextchat应用是部署在vercel了是么?webdev的配置是什么有截图么?

@Issues-translate-bot
Copy link

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


Are you using the latest version? Is the nextchat application deployed in vercel? What is the configuration of webdev? Do you have any screenshots?

@cacosub7
Copy link
Author

使用的是最新版本么?nextchat应用是部署在vercel了是么?webdev的配置是什么有截图么?

1.使用目前最新的2.11.3
2.部署在vercel
3.webdav用的坚果云账户,代理没有配
image

@davidw0374
Copy link

Cloud Data Sync does not work.
1.version: 2.11.3
2.windows 10 client
3.upstash protocol, and no proxy config.
a.watching from client:
check connection is OK
sync is OK
b.watching from upstash admin platform,:
10 reads , 0 writes, 0 byte storage

@haso2007
Copy link

已知上一版本是没有这个问题的,我同步后部署到vercel upstash部署就就不行了。

@Issues-translate-bot
Copy link

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


It is known that the previous version did not have this problem. After synchronization, I deployed it to vercel upstash and it failed.

@xcpky
Copy link

xcpky commented May 3, 2024

我用UpStash,也是同步失败,chat-next的版本是v2.12.2,部署在vercel上

@Issues-translate-bot
Copy link

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


I used UpStash, but the synchronization also failed. The version of chat-next is v2.12.2, which is deployed on vercel.

@rooben-me rooben-me linked a pull request May 3, 2024 that will close this issue
rooben-me added a commit to rooben-me/ChatGPT-Next-Web that referenced this issue May 3, 2024
@rooben-me
Copy link

@xcpky 我也遇到了同样的问题,可以尝试这个分支 #4610

@Issues-translate-bot
Copy link

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


@xcpky I also encountered the same problem, you can try this branch #4610

@starsead
Copy link

starsead commented May 8, 2024

@xcpky 我也遇到了同样的问题,可以尝试这个分支 #4610

你说的这个分支在 vercel 怎么部署?

@Issues-translate-bot
Copy link

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


@xcpky I also encountered the same problem, you can try this branch #4610

How to deploy this branch in vercel?

@rooben-me
Copy link

rooben-me commented May 8, 2024

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

Successfully merging a pull request may close this issue.

8 participants