sillstrybarn

So I've had some vpn(?) issues a while now. It feels like it started when I was running 4.3.9 together with ovpn. Sometimes it worked a few days, sometimes about a day. Didn't work to just restart the container. Had to generate new config and new port. I thought it would be better to update qbit. So now im running 5.0.3 and also changed vpn to Proton. But seems like kind of the same problem now. It works for maybe a day, and sometimes a few days. Then it gets stuck. Can manually restart to get it working. But after a few restarts, I try another server. But always the same problem. I thought it maybe had something to do with my unifi udmp and ids/ips. So I tried to exclude my unraid server ip. But still the same problem. Seems to be similar to this: https://github.com/binhex/arch-qbittorrentvpn/issues/298 How to best solve this? Try hotio instead?

I'm currently running 4.3.9-2-01. Mostly because the issues with earlier unraid version. Now I'm wondering about protonvpn port forward will work with this version of qbit? Or do I have to update to a later version? I know I read somewhere you can manuelly update the docker template and add Proton. But will this work?

Started to get DNS failure every other day... DNS failure, creating file '/tmp/dnsfailure' Im using ovpn. Its been working great for a long time, but all of a sudden I have to replace wg0.conf to get it working.

Is it a bad idea to use the flash backup taken when the drive was already failing?

Thanks! Will do that then

Just saw this in the logs today. I guess my usb flash drive is failing? Anything I can do to fix it or do I need to replace the usb? Jul 12 11:36:28 unraid kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Jul 12 11:36:28 unraid kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x7 [current] Jul 12 11:36:28 unraid kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x27 ASCQ=0x0 Jul 12 11:36:28 unraid kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 00 00 7a a3 00 00 01 00 Jul 12 11:36:28 unraid kernel: critical target error, dev sda, sector 31395 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jul 12 11:36:28 unraid kernel: Buffer I/O error on dev sda1, logical block 29347, lost async page write Ive created a flash backup. And downloaded diagnostics. I tried shutting down and took the usb to my computer trying to run chkdsk. But no success. The USB is in raw and cannot be checked. unraid-diagnostics-20240712-1134.zip

Is the problem only when using PCI or USB with RTL8125? Im runnning z790-p with onboard ethernet RTL8125. Can I still get problems?

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...

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?

So this is not fixed in latest unraid version?

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??

Is there still problems with qbittorrent after 4.3.9 that makes unraid crash?

Same thing happened now after reboot. Cannot access dockers on br0 from NPM on my custom docker network.

I've rolled back qbit to 4.3.9 now. Hope that helps.

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?