Foxy

Hello! I've been using your qbittorrent container for a few weeks without issues now. However now I can no longer login into the web-ui. When I submit my username + password, the login page reloads and nothing happens. No error message, nothing. However when I enter a wrong password, I still get the error message that uname/pw is wrong What I did before the problem occurred: - Not sure if it's related to the problem, but I installed + ran unraid ClamAV to scan my torrent directory. I set it to check the folder which contains the sub-folders for finished torrents, in-progress torrents, torrent files and the input/consume folder for new torrent files. ClamAV ran without error and didn't find anything. A while later I couldn't log into the qbittorrent WebUI anymore. -> A restart of the qbittorrent container temporarily allowed me to login again. However a few hours later the login problem reoccurred and now no amount of restarting will allow me to login again. What I have tried to solve the problem: - Check container logs - no entries besides the startup entries from a few hours ago - restart container - restart unraid server - Use different browser (firefox / edge) - check username / pw in qbittorrent config file - no changes, still my username and pw - force update container - change pw in qbittorrent config file. Restart container and try to log in with new password. Now I get the "wrong password" error message for the new password. Original password still produces reload with no error message, login fails with both passwords. Restored original config file to undo my changes. EDIT1: supervisord.log contained the following section: DEBG 'start-script' stdout output: [warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN [info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle' Executing the recommended command in the UnRaid cli solved the problem for now. Don't know whether it'll survive a reboot, but the workaround is good enough for me. EDIT2: Great. After a reboot the login is broken again, same way as before. However the supervisord.log does not show any errors related to the UI anymore, and executing "/sbin/modprobe iptable_mangle" does not fix the problem anymore either. Back to square one I guess.