sillstrybarn

Members
  • Posts

    15
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

sillstrybarn's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Is the problem only when using PCI or USB with RTL8125? Im runnning z790-p with onboard ethernet RTL8125. Can I still get problems?
  2. I have the exact same problem. I thought I did something wrong. It's working fine with my other server still running 6.11.5. It works if I use FF. So I guess brave on phone and 6.12.6 doesn't like each other...
  3. I tried uninstalling and disabling everything bound to WSL/wsl2, and then pasted my original xml for my win10, but it still wont start... Any ideas?
  4. So this is not fixed in latest unraid version?
  5. Thanks for the advice. Same happened to me with my new 13500. Ran 8700k before, and it was working just fine. Is this fixed in latest unraid version??
  6. Is there still problems with qbittorrent after 4.3.9 that makes unraid crash?
  7. Same thing happened now after reboot. Cannot access dockers on br0 from NPM on my custom docker network.
  8. I've rolled back qbit to 4.3.9 now. Hope that helps.
  9. Rolled back to qbit 4.3.9 now. Hope it will work until there's a fix.
  10. Maybe will try to rollback to that one first. Hoping it wont be a banned client on different sites...
  11. Thanks! But would love to skip all the work with setting up another docker with VPN and privoxy and run qbit through that... But if that's what I have to do.
  12. Running 6.11.5 and qbit 4.5.2 so I'm guessing this is my problem as well? What version of qbit should I downgrade to?
  13. I'm courious if anyone else got the same problem with this docker. I've been using it for a couple of years now and it happens from time to time. The docker seems to crash and the unraid webui becomes unresponsive. I've tried a couple of different methods to kill the docker, but it always ends with rebooting the server. I've been using it with Nordvpn before and now Im using mullvad vpn. Earlier I did not use privoxy, but now my prowlarr docker is connecting via the privoxy. Cannot see anything obvious in the logs what is causing the "crash". When this happened like two hours ago, I tried stopping docker service via ssh. It says something like "cannot stop docker qbit". But the service stops. And the webui gets responsive again. But then i cannot start the docker service bacause "docker.img is in use". So i tried to stop the array. But then the log said it "cannot unmount /mnt/cache because its busy". So I tried a command I read in another thread on the forums "lsof /mnt/cache". And it listed a few .lock-files in the qbit-appdata folder. My appdata is stored on the cache only. Then i tried reboot, but I guess that was not a clean one, because it started a parity sync on startup. Where to look for a solution? Is this what's causing me problem?
  14. Just ran into this. Running 6.11.5. But it took me like 2 hours before I found this thread and tested it. Was checking all docker logs to find out what was wrong. Then I saw that the problem was NPM could not route to dockers on br0. And after hours of googling, i found this thread. Thanks! But would be nice to get this fixed. I thought i broke something last night when I was fixing nextcloud php problem.
  15. Yes, I noticed my prowlarr indexer not working. But I've already removed the privoxy folder and changed the DNS in qbit docker. It worked like a couple of days, and now it's the same again...