yes on this page I found the search engine that I need. but I don’t understand instructions on how to install it in the interface
Correct. I’m running on an i7 NUC which usually runs at about 1 or 2% CPU usage, and 45C CPU temp. Starting this add-on causes the CPU usage to go up to 9% and the CPU temp straight up to 97~100C. I’m guessing the CPU isn’t really getting that hot so quickly, but it certainly thinks that it is and so runs the fan at full speed.
Will do. Thanks
Very weird, I don’t see how the docker should be able to influence the value measured by the temp probe! I’ll try to think a bit of what could happen
Thanks, I had not seen your reply above! So, steps are :
- Open Qbittorrent from url (http://YOURLOCALIP:8081)
- Go in VueTorrent options, in the webui section
- Un check use alternative webui
- Reload the page, you should see the original ui
- Follow this guide : https://github.com/qbittorrent/search-plugins/wiki/Install-search-plugins#steps-to-install-search-plugins-qbittorrent-version-3110-or-more-recent
Globally, by using the orignal ui instead of VueTorrent, you have an additional field in the search view (in View > Search Engines) where you can add new search engines downloaded manually from the Web. Normally, downloaded search engines should stay after reboot
Let me know if you need additional help!
I’ve been playing with several of your addons lately, and have a few questions.
- Default setup has the value 0 for both
PUID
andPGID
. Isn’t that a security concern? I see linuxserver uses the value 1000 for both, which seems to be the standard values for these. I’ve had some writing/access issues trying to set these to 1000 myself, but 0 works (root access?). - I see in your filename that it’s based on Ubuntu, but linuxserver seems to have moved from Ubuntu to Alpine on Jan 7th. Is that the case with your plugin aswell? Alpine should be more lightweight, no?
- For qBittorrent, I have 5
customUI
options, but the two first are blank. I think this is because of"customUI": "list(|vuetorrent|qbit-matUI|qb-web)?"
inconfig.json
where the first|
-symbol in the parentheses should not be there. Is there nodefault UI
-option?
For the record, I don’t use the mounting of external drives in these addons as I have applied the udev
80-mount-usb-to-media-by-label.rules to mount my external drive.
Hi,
- if you are within your own container, 1000 should be fine. However, this could cause issues with files stored in shared volumes (such as /share or /config) and options such as smb mount. So it’s easier to set 0:0 as default to make it work for most users if you set it to another value, you should then ensure all folders that you want to access have the set access rights
- indeed, 4.4.0 had a huge bug that prevented the scripts and custom UI to work. I see that 4.4.1 is out, I’ll align with this version and we’ll see how that goes
- The first two blanks correspond to the “default-ui”. The first blank is because this field is optional (so blank), the second is because a blank value must appear in the dropdown list. Indeed, this might be confusing - per your suggestion I’ll add a default UI setting. Beware however that it only impacts UI when accessing by IP:port, not the UI when using ingress (I’ve only managed to make ingress work with vuetorrent)
New version based on 4.4.1 will be up shortly so we can test if everything works
Thanks!
Looks like v4.4.1 introduces new issues (reasons why I had avoided 4.4.0) I’ll try to fix it ASAP
I finally logged this issue on GitHub, unfortunately Git is semi-blocked (it loads but without formatting so it sucks to use) at my work where I have been for the last 2 weeks. I don’t think my log really gives any insight as to why this is happening but I’m happy to post any other info that you need. Thinking about it now, I also had issues with Intel NUC’s (Itried this with 2 of them) running the MotionEye add-on where that too would cause excessive CPU temp rise even though the CPU usage was still really low.
Hi, 4.4.1 is back in business! A new version is pushed which allows to correctly set the download directory to the addon option.
@sparkydave : thanks for creating the issue. Honestly I’m not sure at all how to check this, my idea was more to see how an app could interfere with Temp probe reporting… And good to know it’s not specific to motioneye. Perhaps an issue in HA itself ?
Hi there,
I just installed Version release-4.4.1-ls173-2
on my raspberry.
Unfortunately the add-on won’t start-up. I tried it with the default settings, but the logs were not helpful - for me at least. Changed the SavePath or added an openvpn user, resulting in the same logs.
Could you help me here @alexbelgium? Thanks!
Logs:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-aaa_dockerfile_backup.sh: executing...
[cont-init.d] 00-aaa_dockerfile_backup.sh: exited 0.
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Add-on: Qbittorrent
qBittorrent is a bittorrent client
-----------------------------------------------------------
Add-on version: release-4.4.1-ls173-2
You are running the latest version of this add-on.
System: Home Assistant OS 7.4 (armv7 / raspberrypi3)
Home Assistant Core: 2022.2.9
Home Assistant Supervisor: 2022.01.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums
https://github.com/alexbelgium/hassio-addons
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 01-migrations: executing...
[migrations] started
[migrations] no migrations found
[cont-init.d] 01-migrations: exited 0.
[cont-init.d] 02-tamper-check: executing...
[cont-init.d] 02-tamper-check: exited 0.
[cont-init.d] 10-adduser: executing...
-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/
Brought to you by linuxserver.io
-------------------------------------
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid: 0
User gid: 0
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 30-nginx.sh: executing...
[cont-init.d] 30-nginx.sh: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 90-dns_set.sh: executing...
[15:48:16] INFO: DNS SERVERS set to 1.1.1.1 8.8.8.8
[cont-init.d] 90-dns_set.sh: exited 0.
[cont-init.d] 91-qbittorrent_configuration.sh: executing...
sed: no previous regexp
[cont-init.d] 91-qbittorrent_configuration.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
Sorry I see what happened. I’ll push a v3 ASAP. Thanks!
Thanks @alexbelgium!
I bypassed this error just with deleting the content from the qbittorrent.conf. Then it just started flawlessly. Now when I try to connect via openvpn I’ve got another error where I need some help. There’s something wrong the internet device. Could you take a look into the logs?
2022-02-21 19:23:28 ROUTE_GATEWAY 172.30.32.1/255.255.254.0 IFACE=eth0 HWADDR=02:42:ac:1e:21:06
2022-02-21 19:23:28 GDG6: remote_host_ipv6=n/a
2022-02-21 19:23:28 net_route_v6_best_gw query: dst ::
2022-02-21 19:23:28 sitnl_send: rtnl: generic error (-101): Network unreachable
2022-02-21 19:23:28 ROUTE6: default_gateway=UNDEF
2022-02-21 19:23:28 TUN/TAP device tun0 opened
2022-02-21 19:23:28 /sbin/ip link set dev tun0 up mtu 1500
2022-02-21 19:23:28 /sbin/ip link set dev tun0 up
2022-02-21 19:23:28 /sbin/ip addr add dev tun0 10.5.0.5/16
2022-02-21 19:23:28 /sbin/ip link set dev tun0 up mtu 1500
2022-02-21 19:23:28 /sbin/ip link set dev tun0 up
2022-02-21 19:23:28 /sbin/ip -6 addr add fdda:d0d0:cafe:443::1003/64 dev tun0
RTNETLINK answers: Permission denied
2022-02-21 19:23:28 Linux ip -6 addr add failed: external program exited with error status: 2
2022-02-21 19:23:28 Exiting due to fatal error
Seems it can’t setup some route or access tun0
same problem here
Hi, it’s solved in the v3, either you wait for your repo to update, or you go un the same place where you added the custom repo (in supervisor tab), click on the 3 little dots a top right and click reload! Then it will show as available to update
Thanks, I’m not using openvpn but I’ll set a temporary one tomorrow to check that
Looks like you’re using ipv6 and when doing the tests I only used ipv4. I’ll try to find a solution
BTW was it working in the past, and not anymore with the latest updated, or was it never working?
v3 is also no-go.
Here is what I’ve got in logs:
[cont-init.d] 91-qbittorrent_configuration.sh: executing...
[23:41:40] INFO: Downloads can be found in /mnt/shared/
[23:41:40] INFO: Whitelisted subsets will not require a password : localhost,127.0.0.1,172.30.0.0/16,192.168.0.0/16
[23:41:40] INFO: Alternate UI enabled : qb-web. If webui don't work, disable this option
curl: (3) URL using bad/illegal format or missing URL
[cont-init.d] 91-qbittorrent_configuration.sh: exited 3.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
My configuration is:
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
whitelist: localhost,127.0.0.1,172.30.0.0/16,192.168.0.0/16
customUI: qb-web
SavePath: /mnt/shared/
Username: ''
DNS_server: 8.8.8.8,1.1.1.1
PUID: '0'
PGID: '0'
networkdisks: //192.168.000.000/shared
cifsusername: nikodim
cifspassword: <<<<passwd>>>>
cifsdomain: HOME
TZ: ''
Can you please take a look?
And vuetorrent works? - EDIT : confirmed, all custom ui work except qb-web I’ll issue a v4 with corrected url
Sorry for all these issues but 4.4.1 is a really big change. Once that is ironed out it should be good for a long time
After container restart the error has changed (I’ve also put both qt-web and default web-UI), now it’s:
[cont-init.d] 30-nginx.sh: executing...
[cont-init.d] 30-nginx.sh: exited 1.
Probably I need to rebuild container to make it work with default UI.
Hi, normally you don’t need to rebuild. Could you please post the full log? Thanks!
I’ve removed qb-web from the next version as anyway it is very infrequently updated