Linux内测版

一楼写了啊,2.7.1只有docker版本
https://hub.docker.com/repository/docker/wxhere/bitcomet/general

不好意思,写完文档忘记提交了。现在有了,latest等同于v2.7.1

这个还得研究一下了

1個讚

感谢大佬回复,已经修的很好了,期待以后版本。:+1::+1::+1:

希望有web ui 服务器没有图形界面


一直报错是为什么啊,说什么not expected.访问6800也访问不了


有人在群晖上成功过吗


给他分配的文件夹也有文件生成,但是访问不了端口。设置的是host模式

勾选文件的时候,这个地方的 √ 显示不出来。
换上电脑,终于把这个图片上传上来了,,, :joy: :joy: :joy:

用手机APP连接docker版,似乎不怎么稳定,经常出现这个提示:
网络错误:javax.net.ssl.SSLHandshakeException: connection closed

话说这段时间手机发不了图片是我的问题还是论坛的问题?

重装以后这问题貌似没有了,真是奇怪,,,:joy::joy::joy:

发现了,这个问题在满速下载和上传时容易出现,是上传下载挤占了控制端链接的带宽吗?同时发现在这种时候,web端也会偶尔连不上,,,

用一段时间后,docker重启BitComet就没法自动启动了,每次非要手动重启一下才行,,,之前试过重建容器能管用一阵子,现在重建容器也不好用了,,,看log有时会有报错,但大部分时候也看不出啥,,,
附上一段log,大佬们有空帮忙看看:
2024-04-21 03:43:27,552 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-04-21 03:43:28,579 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
stored passwd in file: /.password2

  • enable custom user: sandbox
    useradd: user ‘sandbox’ already exists
  • enable HTTP base authentication
    Adding password for user sandbox
    2024-04-21 03:45:46,265 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
    2024-04-21 03:45:46,265 INFO Included extra file “/etc/supervisor/conf.d/supervisord.conf” during parsing
    2024-04-21 03:45:46,573 INFO RPC interface ‘supervisor’ initialized
    2024-04-21 03:45:46,573 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
    2024-04-21 03:45:46,573 INFO supervisord started with pid 22
    2024-04-21 03:45:47,579 INFO spawned: ‘nginx’ with pid 24
    2024-04-21 03:45:47,581 INFO spawned: ‘web’ with pid 25
    2024-04-21 03:45:47,583 INFO spawned: ‘xvfb’ with pid 26
    2024-04-21 03:45:47,584 INFO spawned: ‘lxpanel’ with pid 27
    2024-04-21 03:45:47,586 INFO spawned: ‘x11vnc’ with pid 28
    2024-04-21 03:45:47,588 INFO spawned: ‘novnc’ with pid 29
    2024-04-21 03:45:47,589 INFO exited: xvfb (exit status 1; not expected)
    2024-04-21 03:45:47,593 INFO exited: x11vnc (exit status 1; not expected)
    2024-04-21 03:45:47,641 INFO exited: lxpanel (terminated by SIGABRT (core dumped); not expected)
    2024-04-21 03:45:47,708 INFO Listening on http://localhost:6079 (run.py:87)
    2024-04-21 03:45:48,604 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2024-04-21 03:45:48,604 INFO success: web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2024-04-21 03:45:48,605 INFO spawned: ‘xvfb’ with pid 52
    2024-04-21 03:45:48,606 INFO spawned: ‘x11vnc’ with pid 54
    2024-04-21 03:45:48,606 INFO success: novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2024-04-21 03:45:48,653 INFO spawned: ‘lxpanel’ with pid 69
    2024-04-21 03:45:49,712 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2024-04-21 03:45:49,712 INFO success: lxpanel entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2024-04-21 03:45:49,712 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2024-04-21 03:56:51,914 WARN received SIGTERM indicating exit request
    2024-04-21 03:56:51,914 INFO waiting for nginx, web, xvfb, lxpanel, x11vnc, novnc to die
    2024-04-21 03:56:51,915 INFO stopped: novnc (exit status 143)
    2024-04-21 03:56:51,915 INFO stopped: x11vnc (exit status 2)
    2024-04-21 03:56:51,924 INFO stopped: xvfb (terminated by SIGKILL)
    2024-04-21 03:56:52,052 INFO stopped: lxpanel (exit status 0)
    2024-04-21 03:56:52,053 INFO stopped: web (terminated by SIGTERM)
    2024-04-21 03:56:52,056 INFO stopped: nginx (exit status 0)
    Unlinking stale socket /var/run/supervisor.sock
    stored passwd in file: /.password2
  • enable custom user: sandbox
    useradd: user ‘sandbox’ already exists
  • enable HTTP base authentication
    Adding password for user sandbox
    2024-04-21 03:57:05,671 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
    2024-04-21 03:57:05,671 INFO Included extra file “/etc/supervisor/conf.d/supervisord.conf” during parsing
    2024-04-21 03:57:05,674 INFO RPC interface ‘supervisor’ initialized
    2024-04-21 03:57:05,674 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
    2024-04-21 03:57:05,674 INFO supervisord started with pid 22
    2024-04-21 03:57:06,676 INFO spawned: ‘nginx’ with pid 24
    2024-04-21 03:57:06,678 INFO spawned: ‘web’ with pid 25
    2024-04-21 03:57:06,679 INFO spawned: ‘xvfb’ with pid 26
    2024-04-21 03:57:06,680 INFO spawned: ‘lxpanel’ with pid 27
    2024-04-21 03:57:06,682 INFO spawned: ‘x11vnc’ with pid 28
    2024-04-21 03:57:06,683 INFO spawned: ‘novnc’ with pid 30
    2024-04-21 03:57:06,821 INFO Listening on http://localhost:6079 (run.py:87)
    2024-04-21 03:57:07,708 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2024-04-21 03:57:07,708 INFO success: web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2024-04-21 03:57:07,708 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2024-04-21 03:57:07,708 INFO success: lxpanel entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2024-04-21 03:57:07,708 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
    2024-04-21 03:57:07,708 INFO success: novnc entered RUNNING state, proces

docker版想用host模式试试能不能upnp,结果80端口被占用了,能改下默认的80端口吗?

2.7.1的upnp能用吗?用设置了docker内外的端口,也做了映射,还是显示端口阻塞


命令行启动时 收藏夹栏总是这么窄咋回事
麻烦看下

win版怎么跑这里了

请问未来会支持ARM64架构的吗

1個讚

BitComet-2.8.0-loongarch64版左下角不显示个人账号信息,而且在工具->选项->BT下载->允许连接的BT客户端列表里,点击客户端列表,会导致该页面直接卡死(必现),无法点击确认

是的,目前界面库还有些问题

同求ARM,现在ARM硬路由的配置已经可以撑得住DOCKER版BC了

BitComet-2.8.0-loongarch64版的视频预览功能也有问题,我选择了vlc媒体播放器进行播放视频,第一次刚选择完播放器的时候视频可以正常播放,但是把播放器关闭之后再点击预览视频时却提示播放器程序不存在,这个也是必现

docker版经常会出现容器启动了但BitComet没启动起来的情况,日志里也看不出什么,重启容器大概率可以恢复正常,但有时会需要多重启几次,,,重建过很多次容器了,一直有这个问题。