Jump to content

VergilGao

Members
 View Profile  See their activity

  • Posts

    50

  • Joined

  • Last visited

 Content Type 

Posts posted by VergilGao

    添加检验盘后读写速度非常慢

    in Chinese / 简体中文

    Posted

    7 hours ago, jinlife said:

    Unraid就是这个样子，加上校验盘后，写数据的时候会同时访问数据盘和校验盘，速度至少减半。所以校验盘最好是速度最快容量最大的盘，其他的数据盘最好也是类似的速度，要不就会被最慢的那个盘的速度拖累的。建议还是用NAS盘或者高速硬盘，本身有200MB/s的读写速度。

    如果不需要所有数据都保护，确实用不着校验盘，虽然安全，但是减速度。

     

    但是我做过测试，现在我就是有校验盘的情况下，SMB传文件还是能跑满千兆……

    add support for rtl8761bu

    in Feature Requests

    Posted · Edited by VergilGao

    I bought a bluetooth usb device using rtl8761bu chip, it can drive in unraid6.9.2 version, but when I run `bluetoothctl` scan on, it can't scan any device.

    When looking for information, I found the kernel patch and the temporary solution.

    patch: https://patchwork.kernel.org/project/bluetooth/patch/[email protected]/

    temp: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955916/comments/21

    I followed the temporary solution and completed the following repair script 

    #!/bin/sh

set -e

ko_path=/lib/modules/"$(uname -r)"/kernel/drivers/bluetooth

sudo cp "${ko_path}"/btusb.ko.xz "${ko_path}"/btusb.ko.xz.bak
xz -dkf "${ko_path}"/btusb.ko.xz
xxd "${ko_path}"/btusb.ko | sed 's/ca04 0540/5025 6187/g' |xxd -r > "${ko_path}"/btusb.ko.mod
mv "${ko_path}"/btusb.ko.mod "${ko_path}"/btusb.ko
xz -f "${ko_path}"/btusb.ko
chmod 644 /lib/modules/"$(uname -r)"/kernel/drivers/bluetooth/btusb.ko.xz

sudo cp /boot/config/custom/firmware/rtl8761b* /lib/firmware/rtl_bt
chmod 644 /lib/firmware/rtl_bt/rtl8761b*

modprobe -r btusb && modprobe btusb

    the usb device worked successfully.

    Please let me know if this is fixed in 6.10.

     

     

     

    [Support] ich777 - Gameserver Dockers

    in Docker Containers

    Posted · Edited by VergilGao

     

    dontstarve needs a 64-bit version.

     

    if you run the 32-bit server and use the 64-bit client, you would find you can walk on the sea, and could never save your profile in the server.

    I realized this problem after several failures. You can refer to this commit to upgrade 32-bit to 64-bit, but the best practice should be to create another branch to maintain the 64-bit version.

    https://github.com/VergilGao/docker-steamcmd-server/commit/7e09925ddae0db3849bcc1e4bdb854e340cd782b

    关于qbittorrent下载速度求助

    in Chinese / 简体中文

    Posted

    On 4/22/2022 at 12:51 AM, lyqalex said:

    QB对于端口映射要求不高，所以没有外网ip用户很友好，端口问题应该不大。在询问帮助时，应该提供更详细配置抓图。我给3个建议：

    1、在高级处开启”操作系统缓存“；

    2、在高级处开启“总是向同级的所有 Tracker 汇报”和“总是向所有等级的 Tracker 汇报”；

    3、docker网络模式选择host。

    ps：我并没有安装Linuxserver的qbittorrent，因为这个docker的端口是锁死的，没办法通过配置更改。用hotio的版本更佳。

    因为qb需要upnp，所以bridge肯定是不行的，那么如果选host的话，直接在配置里修改端口就好了。

    我不能反向代理到我的unraid，但是可以路由器端口转发连接到unraid（已解决）

    in Chinese / 简体中文

    Posted

    On 2/17/2022 at 9:24 AM, BlueFang said: 
            location / {
            proxy_pass http://$server;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            proxy_set_header Host $http_host;
            proxy_set_header Access-Control-Allow-Origin $server;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-NginX-Proxy true;
        }

    nginx proxy manager配置，面板上cpu占用之类能动了，但是安装插件或者docker时弹出的日志面板空白，直到安装完插件才会突然显示所有日志信息，等大雕出方案抄作业。

    目前我已经完美搞定了，你参考一下

    • Like 1

    unraid 禁用root

    in Chinese / 简体中文

    Posted · Edited by VergilGao

    也不要谈root色变，很简单的道理，只要你进了unraid的web端，不管你是什么用户，基本上就宣告拿到了系统的root权限。

    你需要在外层就做好防范。

    如何通过其他设备的nginx反代unraid的webui？

    in Chinese / 简体中文

    Posted · Edited by VergilGao

    感谢，配置了 ws 之后就正常了，脑子糊涂了忘记了

     

    下面是我的nginx.conf文件，仅供参考，敏感信息已经隐去。

      

    upstream unraid {
    server 192.168.199.200;
    keepalive 64;
}

server {
    listen 80;
    listen [::]:80;
    server_name unraid.example.com;
    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name unraid.example.com;

    access_log /tmp/log/nginx/unraid.access.log;
    error_log /tmp/log/nginx/unraid.error.log;

    ssl_protocols TLSv1.3;
    ssl_prefer_server_ciphers on;

    ssl_ciphers EECDH+AESGCM:EDH+AESGCM;

    ssl_session_timeout 10m;
    ssl_session_cache shared:SSL:10m;
    ssl_session_tickets off;

    ssl_certificate /etc/acme/*.example.com/*.example.com.cer;
    ssl_certificate_key /etc/acme/*.example.com/*.example.com.key;

    location / {
        proxy_pass http://unraid;

        proxy_http_version 1.1;
        proxy_buffering off;
        proxy_set_header Host $http_host;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        
        proxy_redirect off;
    }
}

     

    • Like 1
×
×
  • Create New...