alist
alist copied to clipboard
本地电脑桌面版可以正常访问,部署服务器同样配置报错
Please make sure of the following things
-
[X] I have read the documentation. 我已经阅读了文档。
-
[X] I'm sure there are no duplicate issues or discussions. 我确定没有重复的issue或讨论。
-
[X] I'm sure it's due to
AListand not something else(such as Network ,DependenciesorOperational). 我确定是AList的问题,而不是其他原因(例如网络,依赖或操作)。 -
[X] I'm sure this issue is not fixed in the latest version. 我确定这个问题在最新版本中没有被修复。
AList Version / AList 版本
v3.35.0
Driver used / 使用的存储驱动
对象存储的cloudfare
Describe the bug / 问题描述
我下载的是alist的桌面版,本地电脑正常访问没问题 部署到linux服务器,一直无法访问cloudfare存储 然后我尝试部署到windows服务器,7月4日一切正常,7月5日就无法访问了
报错信息 Request failed with status code 504
现在又可以正常访问了
Reproduction / 复现链接
http://xxz.hehaokun.work/
Config / 配置
{ "force": false, "site_url": "", "cdn": "", "jwt_secret": "fUcoRJPZaXPB2SAG", "token_expires_in": 48, "database": { "type": "sqlite3", "host": "", "port": 0, "user": "", "password": "", "name": "", "db_file": "C:\Users\Administrator\AppData\Roaming\ci.nn.alist\data.db", "table_prefix": "x_", "ssl_mode": "", "dsn": "" }, "meilisearch": { "host": "http://localhost:7700", "api_key": "", "index_prefix": "" }, "scheme": { "address": "0.0.0.0", "http_port": 5244, "https_port": -1, "force_https": false, "cert_file": "", "key_file": "", "unix_file": "", "unix_file_perm": "" }, "temp_dir": "C:\Users\Administrator\AppData\Roaming\ci.nn.alist\temp", "bleve_dir": "C:\Users\Administrator\AppData\Roaming\ci.nn.alist\bleve", "dist_dir": "", "log": { "enable": true, "name": "C:\Users\Administrator\AppData\Roaming\ci.nn.alist\log\log.log", "max_size": 50, "max_backups": 30, "max_age": 28, "compress": false }, "delayed_start": 0, "max_connections": 0, "tls_insecure_skip_verify": true, "tasks": { "download": { "workers": 5, "max_retry": 1 }, "transfer": { "workers": 5, "max_retry": 2 }, "upload": { "workers": 5, "max_retry": 0 }, "copy": { "workers": 5, "max_retry": 2 } }, "cors": { "allow_origins": [ "" ], "allow_methods": [ "" ], "allow_headers": [ "*" ] }, "s3": { "enable": false, "port": 5246, "ssl": false } }
Logs / 日志
/source/internal/op/fs.go:127 github.com/alist-org/alist/v3/pkg/singleflight.(*Group[...]).doCall.func2 /source/pkg/singleflight/singleflight.go:193 github.com/alist-org/alist/v3/pkg/singleflight.(*Group[...]).doCall /source/pkg/singleflight/singleflight.go:195 github.com/alist-org/alist/v3/pkg/singleflight.(*Group[...]).Do /source/pkg/singleflight/singleflight.go:108 github.com/alist-org/alist/v3/internal/op.List /source/internal/op/fs.go:124 github.com/alist-org/alist/v3/internal/fs.list /source/internal/fs/list.go:25 github.com/alist-org/alist/v3/internal/fs.List /source/internal/fs/fs.go:22 github.com/alist-org/alist/v3/server/handles.FsList /source/server/handles/fsread.go:86 github.com/gin-gonic/gin.(*Context).Next /go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:174 github.com/alist-org/alist/v3/server/middlewares.Auth /source/server/middlewares/auth.go:73 github.com/gin-gonic/gin.(*Context).Next /go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:174 github.com/alist-org/alist/v3/server/middlewares.StoragesLoaded /source/server/middlewares/check.go:14 github.com/gin-gonic/gin.(*Context).Next /go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:174 github.com/gin-gonic/gin.CustomRecoveryWithWriter.func1 /go/pkg/mod/github.com/gin-gonic/[email protected]/recovery.go:102 github.com/gin-gonic/gin.(*Context).Next /go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:174 github.com/gin-gonic/gin.LoggerWithConfig.func1 /go/pkg/mod/github.com/gin-gonic/[email protected]/logger.go:240 github.com/gin-gonic/gin.(*Context).Next /go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:174 github.com/gin-gonic/gin.(*Engine).handleHTTPRequest /go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:620 github.com/gin-gonic/gin.(*Engine).ServeHTTP /go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:576 net/http.serverHandler.ServeHTTP /usr/local/go/src/net/http/server.go:3137 net/http.(*conn).serve
Thanks for opening your first issue here! Be sure to follow the issue template!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hello @, this issue was closed due to inactive more than 52 days. You can reopen or recreate it if you think it should continue. Thank you for your contributions again.