danimal_0119

Are you using Tailscale?

For me... Restarting the container did not do it. I had to remove it completely with the image, then use the template to bring it back AFTER I reset tailscale. Again, I have no idea what this did or how it worked, but I am now about a week or two with no issues with the GUI for Qbit or Tailscale.

I am local to my machine, but I also use Teamviewer to remotely access a machine that is local if I ever lose connectivity and am remote. If you depend on Tailscale for access, I wouldn't attempt to bring it down until you are on the same network to avoid disconnection. I'm sure there is a better expert to explain but in UnRaid, once you add the App using the built in app (not the docker) you have to run the Tailscale Up command with a couple flags depending on your setup. Then approve it in the Admin panel in Tailscale. What I found was Tailscale wasn't configured properly (pretty sure I over engineered the "Up" command with some flags I didn't need). In my case, I had too many things. The one that worked for me... so far ... was... tailscale up --reset --advertise-routes=192.168.0.0/22 This is advertising my router subnet. Now, I can access any LAN or the IP of the Tailscale page. For example, I can access the same applications in the following scenarios: On the same WiFi with Tailscale ON - 192.168.0.2:1111 & 100.1.1.3:1111 pull up the same page When outside the network - with Tailscale ON - 192.168.0.2:1111 & 100.1.1.3:1111 pull up the same page On the same WifFi with Tailscale OFF - only 192.168.0.2:1111 works When outside the network - with Tailscale OFF - neither works To achieve this, I basically, used the command above to reset all the exit-nodes and other garbage I initially configured. Then had to blow away the QbitVPN container and pretty much resurrect it from scratch. Not just Stop it and Restart. Something got out of whack between the two things and the subnet routing. I also had to make sure each client checked the box for "Allow LAN Access" and the check boxes for Use Tailscale DNS and Tailscale subnets were checked as well. I also turned on Magic DNS in the Admin Panel of Tailscale on their website. Again, I am not an engineer but like most, just know enough to keep learning and have been working on this for a couple weeks to triage.

I just had the same issue. The VPN was not connecting or connecting inconsistently. Are you running Tailscale? I found it I had an advertised route that was messing things up.

Wizards of digitry.... I am flummoxed. I cannot figure out what I do that fixed a problem that seems to be happening when I restart my server or complete a firmware update. Both scenarios. Here's what I have... UNRAID v.7.2.2 Running binhex-qbittorrentvpn with PIA and Privoxy enabled (has worked, does work most of the time) I am unable to access the WebGUI with vpn enabled after restarting the server with our without a firmware update. Logs do not show any errors. I get the usually connections and resolutions I would expect. But GUI no Loady. When I deactivate the VPN and set enabled to No, I can log in just fine as expected. I have restarted the Server, my PC, the network. No joy. I know I have fixed this before, and most recently it was last week it "fixed itself". But I have no idea why it is happening on restarts, what I am doing to fix it, or how to prevent it going forward. I tried removing the images, and using their templates. I replaced the ovpn files with new ones from PIA. Using port 8210 and have a WebUI_Port Variable setup and the Web Interface Port configured as well. Have the Lan_Network set to 192.168.0.0/22 HAve this in Extra Parameters: --sysctl="net.ipv4.conf.all.src_valid_mark=1" No Input Or Output ports listed either. Debug set to true At a loss on this and could use some assistance. What other information can I provide for anyone to see what I am not? Maybe something to do with Tailscale? Using local IP to access qbittorrent while local PC as part of Tailnet? How would rebooting and firmware changes affect both devices on the same Tailnet? Currently both IPs (local IP and Tailnet IP with the port work to access the WebGUI. But I have no idea what I did to make it work. Also, updated the container to pull the :latest image. Running qBittorrent v5.1.4 WebUI (64-bit)

Blew away the docker.img... System stable. New containers coming up slowly. Watching. Time will tell. Thanks so much @JorgeB . Appreciate the guidance.

New additional steps, Re-enabled all plugins Restarted the system All plugins loaded properly. Docker still disabled. System is stable and accessible over WebGUI So, it appears that the docker instance/img is corrupt. Is there a way to rebuild that? I have all container folders save for persistence, but want to blow away the whole thing and potentially recreate them from a template, one at a time. @JorgeB appreciate your help and input. This has been a learning experience for me.

Rebooted the system Started in Normal with GUI All plugins are disabled as well. Started the Array Stopped the parity check Disabled docker and have no VMs. System is stable. What are next steps? Start plugins one by one until something fails? Is there a way to rebuild docker if that is the issue without trying to remember all the docker particulars and ports, etc? Or am I in for a slog to recreate all the containers?

Additional Steps: Renamed all .plg files on flash in plugins folder to .bak. Ran a windows repair on the USB. Found problem, repaired it. Booted to Normal GUI - not Safe Mode. Array started. Cancelled parity check. Waited for Array to start and dockers to initialize. GUI Froze Appears to be 3 min after starting Could it be docker related? syslog attached. The WebGUI had a system message in the bottom left that said "Transferring from localhost..." syslog

Steps I took: Booted to Safe Mode (no plugins). GUI operational and functioning as I would expect. Started the array. Cancelled the parity check. Array started. GUI frozen and unresponsive. Cannot access terminal or any other system resource. I saw another comment you made to another user about renaming all the plug in files on the usb where you stated "You can just rename all .plg files to for example .bak in /config/plugins, if still good you can start renaming one or a few at a time and rebooting to see if you find the culprit." However, if the problem starts on array startup, what would the cause of that be? I can shut down the system and look at the logs. I set up the syslog to mirror to my flash. I just can't get to diagnostics since the system is unresponsive to generate another set.

Booting from the USB and not choosing Safe Mode leads to a frozen UI... can't login, system frozen. If I boot into Safe Mode, no array, no plugins installed. Are you suggesting booting into Safe Mode, then starting the Array without plugins? Or are you suggesting removing plugins somehow from the USB and booting straight up without Safe Mode?

v. 7.1.4syslogvader-diagnostics-20250914-1635.zip Most recent syslog and diagnostics attached. I have weekly backups of the flash and system. Couldn't find a guide on restoring the USB or resetting beyond grabbing the two files (key and super.dat). Is it as simple as formatting it, loading the fresh system OS, then copying those files over? I also have screenshots of my drive allocations on the MAIN page before I started the array in maintenance for the parity check. What else should I be looking at and considering? If this is a hardware issue, where does one begin trying to figure that out?

I am running Unraid 7.1.4: binhex-delugevpn without internal ports or other changes. Privoxy enabled via PIA on 8118 prowlarr running with indexers proxied to port 8118. prowlarr proxy set to same settings as indexer so I can do searches from within prowlarr. I have ignored my local IP in the proxy settings as well. Testing via curl ifconfig.io in the console for delugevpn shows the vpn ip address I expect. Testing in the console for prowlarr shows my public ip address. Why doesn't prowlarr console show the vpn address to confirm it is configured as expected? I was hoping to do the same proxy settings with all the arrs. If this isn't expected behavior, any ideas how to fix?