Open RanExoi opened 4 months ago
Bot detected the issue body's language is not English, translate it automatically.
Title: [Bug] Cloud synchronization of Webdav failed
有浏览器开发者工具中截取的关于接口请求报错的截图么?目前,出于安全考虑,除了通过env var 配置的webdev endpoint之外,仅支持几个公开可信的服务提供商
Bot detected the issue body's language is not English, translate it automatically.
Are there any screenshots of interface request errors taken from the browser developer tools? Currently, due to security concerns, only a few publicly trusted service providers are supported in addition to the webdev endpoint configured via env var
webdav有坑,无论是否是浏览器,代理必须勾选上,代理的URL就是当前你访问的域名,app;里面代理可以写你部署的域名后者ip,在你的云存储设置webdav的根目录下,新建文件夹chatgpt-next-web
,文件夹里新建 backup.json
文件,不用管检查,直接同步即可,太坑了
Bot detected the issue body's language is not English, translate it automatically.
Webdav has pitfalls. Regardless of whether it is a browser or not, the proxy must be checked. The URL of the proxy is the domain name you are currently visiting. In the root directory of your cloud storage settings webdav, create a new folder `chatgpt-next-web
webdav有坑,无论是否是浏览器,代理必须勾选上,代理的URL就是当前你访问的域名,app;里面代理可以写你部署的域名后者ip,在你的云存储设置webdav的根目录下,新建文件夹
chatgpt-next-web
,文件夹里新建backup.json
文件,不用管检查,直接同步即可,太坑了
朋友,可以看下你的配置吗,代理URL还是不知道怎么填写😫
Bot detected the issue body's language is not English, translate it automatically.
Webdav has pitfalls. Regardless of whether it is a browser or not, the proxy must be checked. The URL of the proxy is the domain name and app you are currently visiting. The proxy can write the domain name and IP of your deployment. Set the root of webdav in your cloud storage. Directory, create a new folder
chatgpt-next-web
, and create abackup.json
file in the folder. Don’t bother checking, just synchronize directly. It’s too confusing.
Friend, can you take a look at your configuration? I still don’t know how to fill in the proxy URL😫
试了下,以下两项都需要满足才能成功:
environment:
- WHITE_WEBDEV_ENDPOINTS=https://webdav.example.com/
endpoint/
└── chatgpt-next-web
└── backup.json
其中第一点是程序安全设计 第二点应该是一个BUG
Bot detected the issue body's language is not English, translate it automatically.
After giving it a try, the following two items need to be met to succeed:
- When deploying, you need to add the endpoint of webdav to the whitelist.
environment: - WHITE_WEBDEV_ENDPOINTS=https://webdav.example.com/
- Under the address of the endpoint of webdav, the following file structure must exist, and the json file must also exist:
endpoint/ └── chatgpt-next-web └── backup.json
The first point is program security design The second point should be a BUG
webdav有坑,无论是否是浏览器,代理必须勾选上,代理的URL就是当前你访问的域名,app;里面代理可以写你部署的域名后者ip,在你的云存储设置webdav的根目录下,新建文件夹
chatgpt-next-web
,文件夹里新建backup.json
文件,不用管检查,直接同步即可,太坑了朋友,可以看下你的配置吗,代理URL还是不知道怎么填写😫
我的代理地址不填,但必须勾上代理,检查可用性不需要管他,能同步成功就行,其他都是和上面那位一样的
Bot detected the issue body's language is not English, translate it automatically.
Webdav has pitfalls. Regardless of whether it is a browser or not, the proxy must be checked. The URL of the proxy is the domain name and app you are currently visiting. The proxy can write the domain name and IP of your deployment. Set webdav in your cloud storage. In the root directory, create a new folder
chatgpt-next-web
, and create a newbackup.json
file in the folder. You don’t need to check it, just synchronize it directly. It’s too confusing.Friends, can you take a look at your configuration? I still don’t know how to fill in the proxy URL😫
My proxy address is not filled in, but the proxy must be checked. You don’t need to worry about it to check the availability. As long as the synchronization is successful, everything else is the same as the one above.
我用的main分支自己部署了,可以同步成功,用的 teracloud,没用坚果云试过
Bot detected the issue body's language is not English, translate it automatically.
I deployed the main branch myself, and it can be synchronized successfully. I used teracloud, but I haven’t tried it with Nut Cloud.
本身的同步是有两个问题,一是检查走代理会400异常;二是如果webdav中刚开始没有文件404时,会同步失败。我这边修复了一版,我自己用很正常,你们可以试试。见 #5174
Bot detected the issue body's language is not English, translate it automatically.
The synchronization itself has two problems. One is that when checking the proxy, a 400 exception will occur; the other is that if there is no file in webdav at the beginning and a 404 error occurs, the synchronization will fail. I have fixed a version here and it works fine for me. You can try it. See #5174
有浏览器开发者工具中截取的关于接口请求报错的截图么?目前,出于安全考虑,除了通过env var 配置的webdev endpoint之外,仅支持几个公开可信的服务提供商
您 env var 配置 在哪个目录哪个文件。谢谢
Bot detected the issue body's language is not English, translate it automatically.
Are there any screenshots of interface request errors taken from the browser developer tools? Currently, due to security concerns, only a few publicly trusted service providers are supported in addition to the webdev endpoint configured via env var
Your env var configuration is in which directory and which file. Thanks
有浏览器开发者工具中截取的关于接口请求报错的截图么?目前,出于安全考虑,除了通过env var 配置的webdev endpoint之外,仅支持几个公开可信的服务提供商
您 env var 配置 在哪个目录哪个文件。谢谢
通过环境变量配置:WHITE_WEBDEV_ENDPOINTS,我是用docker compose启动的。 比如我的配置文件为:
# cat docker-compose.yml
version: '3.3'
services:
ahzmr-chatgpt-next-web:
build: ./src
image: ahzmr/chatgpt-next-web
restart: always
container_name: ahzmr-chatgpt-next-web
ports:
- '19086:3000'
environment:
TZ: 'Asia/Shanghai'
WHITE_WEBDEV_ENDPOINTS: 'https://domain/lc/sync/'
...
Bot detected the issue body's language is not English, translate it automatically.
Are there any screenshots of interface request errors taken from the browser developer tools? Currently, due to security concerns, only a few publicly trusted service providers are supported in addition to the webdev endpoint configured via env var
Your env var configuration is in which directory and which file. Thanks
Configured through environment variables: WHITE_WEBDEV_ENDPOINTS, I started it with docker compose. For example, my configuration file is:
cat docker-compose.yml
version: '3.3'
services:
ahzmr-chatgpt-next-web:
build: ./src
image: ahzmr/chatgpt-next-web
restart: always
container_name: ahzmr-chatgpt-next-web
ports:
- '19086:3000'
environment:
TZ: 'Asia/Shanghai'
WHITE_WEBDEV_ENDPOINTS: 'https://domain/lc/sync/'
...
加了环境变量WHITE_WEBDEV_ENDPOINTS, 错误码变了,但是还是有错。。
[WebDav] get key = webdav_share 504 8069-585fe05109d5b99c.js:1 [Sync] SyntaxError: Unexpected token 'A', "An error o"... is not valid JSON
为什么是 WHITE_WEBDEV_ENDPOINTS 不应该是 WHITE_WEBDAV_ENDPOINTS 吗?
我说呢 大家注意下版本吧
@JsonSong89 感谢指出,的确是有拼写错误,已经修正。但是还是出错,打了一些日志出来,发现还是 504, EDGE_FUNCTION_INVOCATION_TIMEOUT
更新到v2.15.3之后,依旧报错,但是错误变成了:
Bug Description
地址正常公网可以打开 但Webdav云同步检查可用性不通过 不知道是怎么回事
Steps to Reproduce
1
Expected Behavior
1
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