Closed antonio1475 closed 1 year ago
A side effect of this is that Sonarr/Radarr can't connect to qBittorrent.
But, I just added my HA IP to the qbit config whitelist and goes straight in. I hadn't set it up properly with the IP subnets (I don't understand how that works). I had whitelisted 192.168.0.0/16 but my HA IP is 192.168.3.77
Sonarr/Radarr can now connect to qBit too.
This didn't happen before the last add-on update though, so not sure if the bug still stands. Thanks :)
Hi, actually some addons configs were not properly sent to the qbittorrent.conf in the previous version... So if the addons options are correctly reflected in the qbittorrent config then it would seem that things are working as expected
Shouldn't 192.168.0.0/16 cover 192.168.3.77?
Interesting.
I just removed 192.168.3.77 and left the previous config from the OP. It works.
Maybe something got hung up with the update and I just needed to re-save the config?
Anyway everything seems fine now, so feel free to close this if you think all is okay! At the very least opening this made me re-save the config and it's solved... :)
Great to know if works again! Just to try, I've updated the exec code with upstream to see if this improves something. In theory, qbittorrent could launch in a more stable manner
Which addon?
Describe the bug
Login from HA / Ingress fails with the last update. Using default user/password, restarted a few times.
But via ip:port works
To Reproduce
Steps to reproduce the behavior:
Full addon log
Full addon config
DNS_server: 8.8.8.8,1.1.1.1 PGID: "0" PUID: "0" SavePath: /mnt/EXT4/Downloads Username: admin certfile: fullchain.pem customUI: vuetorrent keyfile: privkey.pem ssl: false whitelist: localhost,127.0.0.1,172.30.0.0/16,192.168.0.0/16 localdisks: EXT4 openvpn_enabled: false System
System: Home Assistant OS 9.5 (amd64 / generic-x86-64) Home Assistant Core: 2023.3.5 Home Assistant Supervisor: 2023.03.1