-
Minisforum N5 / N5 Pro
Some new info: I have contacted Minisforum and they say that the fans are appropriately controlled for HDD and SSD temperatures by the BIOS. Some other info here: https://github.com/frankcrawford/it87/issues/49 and here: https://github.com/RafalGoslawski/lunar-kernel-driver I will try to do something about this given some time.
-
[Support] ich777 - AMD Vendor Reset, CoralTPU, hpsahba,...
I don't think it is, but I saw that the plugin is downloading drivers, and thought they are running in userspace. Here is the lm-sensors issue for this part: https://github.com/lm-sensors/lm-sensors/issues/400
-
[Support] ich777 - AMD Vendor Reset, CoralTPU, hpsahba,...
If I can source the drivers, I could work on including it in the next build.
-
[Support] ich777 - AMD Vendor Reset, CoralTPU, hpsahba,...
I have an issue with detecting a temperature sensor. sensor-detect reports it as Ite 0x5571. It appears not to be supported by the ITE plugin?
-
Minisforum N5 / N5 Pro
I have one as well. I have problems with detecting the driver for the temp/pwm controller too. It is not ITE or Nuvoton. For GPU, i just installed a low profile A310. It is being detected, but I have not tried it in any media server yet. If anybody has any ideas.. :)
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
The name of the container is: binhex-qbittorrentvpn. I've edited that in the file, same as it is for other containers that are on Swag and are working. It is on the same network created specially for Swag. I use Cloudflare for DNS. There is no special setting for each container. There is a wildcard setting. The error I get is: 502 Bad Gateway, with a "Not secure" note.
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Could somebody help me out? I've been trying to get binhex-qbittorrent to run with swag. I used the regular qbittorent subdomain conf file, and swapped the container name and port. The Subdomain(s): variable field for the container contains "qbittorrent" File attached. binhex-qbittorrent.subdomain.conf
-
[Support] binhex - qBittorrentVPN
That was easy enough to verify, and it indeed solved the problem. For reference, the field LAN_NETWORK should state: IP networks, comma separated, without spaces. THANKS!
-
[Support] binhex - qBittorrentVPN
I've been accessing it through wireguard remotely. All other containers work as expected.
-
[Support] binhex - qBittorrentVPN
Thanks. I'll replace that pass. Slipped my mind when I posted the second time. I edited in a minute, but nevertheless. I've attached the file, since it's too long. I hope I edited all the passwords out of it. supervisord.log
-
[Support] binhex - qBittorrentVPN
Thanks, I am indeed running UnRaid. I've run into similar difficulties with Deluge, and decided to switch, as Qbittorrent has a better gui anyway. Here is how that looks now: docker run -d --name='binhex-qbittorrentvpn' --net='swagproxy' --ip='172.18.0.55' --privileged=true -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e HOST_HOSTNAME="MARVIN" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='XXXXXXXX' -e 'VPN_PASS'='XXXXXXXX' -e 'VPN_PROV'='custom' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'WEBUI_PORT'='8116' -e 'LAN_NETWORK'='192.168.42.0/24' -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8116]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png' -p '6881:6881/tcp' -p '6881:6881/udp' -p '8118:8118/tcp' -p '8116:8116/tcp' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn' 6ae71aedc744cddfe750d687c842587862458728cdc225513e1f367db68c8af5 The command finished successfully! Still no access to the UI. The browser says "This site can’t be reached"
-
[Support] binhex - qBittorrentVPN
Thanks! I don't have that option in the gui? How would I go about changing that setting?
-
[Support] binhex - qBittorrentVPN
I too have trouble accessing the GUI. The VPN worked, but it stopped in the meantime. Here is the config for the container: docker run -d --name='binhex-qbittorrentvpn' --net='swagproxy' --ip='172.18.0.55' --privileged=true -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e HOST_HOSTNAME="MARVIN" -e HOST_CONTAINERNAME="binhex-qbittorrentvpn" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='XXXXXX' -e 'VPN_PASS'='XXXXXX' -e 'VPN_PROV'='custom' -e 'VPN_CLIENT'='openvpn' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='yes' -e 'WEBUI_PORT'='8116' -e 'LAN_NETWORK'='192.168.42.0/24' -e 'NAME_SERVERS'='84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1' -e 'VPN_INPUT_PORTS'='' -e 'VPN_OUTPUT_PORTS'='' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8116]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/qbittorrent-icon.png' -p '6881:6881/tcp' -p '6881:6881/udp' -p '8116:8080/tcp' -p '8118:8118/tcp' -v '/mnt/user/appdata/data':'/data':'rw' -v '/mnt/user/appdata/binhex-qbittorrentvpn':'/config':'rw' --sysctl="net.ipv4.conf.all.src_valid_mark=1" 'binhex/arch-qbittorrentvpn' 472b97658a6912de72f09983597e5e10396a903086b61288959d8968f13fdb86 If anybody has ideas, let me know.
-
[Plugin] CA Fix Common Problems
Hi all, I'm running the backup appdata plugin. The scan suggests to switch to the KluthR version, because the original has been deprecated. I've checked, and I am running the KluthR version. Any suggestions?
-
Forty Two started following 6.10.3 Web interface unavailable when MTU set to 9000
-
6.10.3 Web interface unavailable when MTU set to 9000
The web interface failed to respond when I set the MTU on my desktop to 9000. The server and the desktop both have a Mellanox connectx3 SFP+ (10 GbE) cards. The card on the server also has MTU set to 9000, but that didn't impact performance. All the other sites I visit ran fine.
Forty Two
Members
-
Joined
-
Last visited