We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v2.2.1
Docker
主程序运行问题
大佬,你好。 目前我配置的下载器为tr3.0版本,在MP-设置中,也可以正常获取下载速度,组件检查中也显示正常。 但我的下载任务,无法在MP的下载状态中获取到。 导致MP没办法使用下载器监控,来完成后续的任务。 我已经尝试使用原版tr和最新版tr,都是一样。
INFO: 192.168.31.108:0 - "GET /api/v1/download/?name=TR HTTP/1.1" 200 OK INFO: 192.168.31.108:0 - "GET /api/v1/download/?name=TR HTTP/1.1" 200 OK DEBUG: chain - 请求模块执行:list_torrents ... INFO: 192.168.31.108:0 - "GET /api/v1/download/?name=TR HTTP/1.1" 200 OK DEBUG: chain - 请求模块执行:list_torrents ... INFO: 192.168.31.108:0 - "GET /api/v1/download/?name=TR HTTP/1.1" 200 OK DEBUG: chain - 请求模块执行:list_torrents ... INFO: 192.168.31.108:0 - "GET /api/v1/download/?name=TR HTTP/1.1" 200 OK DEBUG: chain - 请求模块执行:list_torrents ... INFO: 192.168.31.108:0 - "GET /api/v1/download/?name=TR HTTP/1.1" 200 OK DEBUG: chain - 请求模块执行:list_torrents ... INFO: 192.168.31.108:0 - "GET /api/v1/download/?name=TR HTTP/1.1" 200 OK DEBUG: chain - 请求模块执行:list_torrents ... INFO: 192.168.31.108:0 - "GET /api/v1/download/?name=TR HTTP/1.1" 200 OK DEBUG: chain - 请求模块执行:list_torrents ... INFO: 192.168.31.108:0 - "GET /api/v1/download/?name=TR HTTP/1.1" 200 OK DEBUG: chain - 请求模块执行:list_torrents ... INFO: 192.168.31.108:0 - "GET /api/v1/download/?name=TR HTTP/1.1" 200 OK
The text was updated successfully, but these errors were encountered:
me too Transmission 版本:3.00 (bb6b5a062e), RPC: 16
Sorry, something went wrong.
No branches or pull requests
确认
当前程序版本
v2.2.1
运行环境
Docker
问题类型
主程序运行问题
问题描述
大佬,你好。
目前我配置的下载器为tr3.0版本,在MP-设置中,也可以正常获取下载速度,组件检查中也显示正常。
但我的下载任务,无法在MP的下载状态中获取到。
导致MP没办法使用下载器监控,来完成后续的任务。
我已经尝试使用原版tr和最新版tr,都是一样。
发生问题时系统日志和配置文件
The text was updated successfully, but these errors were encountered: