Mlatx

Gluetun was working great routing Prowlarr and Qbitorrent traffic. Both those apps are not working anymore. I can get out to the Internet on Firefox when I use Gluetun as a proxy. Is this a recent update issue? If so, what is the working previous version?

Hi All, I need to understand why I am getting the errors shown here. I have binhex sonnar installed with the exact same settings and no errors. Can someone help point me in the right direction?

If you are having issues with updating to the latest zwave docker, do this to fix it. Edit the container and use this as the repository: zwavejs/zwave-js-ui:11.3.1. It will pull the last version. The devs have identified the issue and are working on a fix.

I'm not sure what is happening, but I'm getting the same ERR Module not found. I restored the past 4 backups without success. I'm not sure what happened that backups don't work.

Thanks for pointing out the bug.

I am not routing it through a vopn container network using vpn_inout_port. My Radar container has its own IP address. It uses privoxy from QBitTorrent as shown in my screen shot. I don’t see why I shouldn’t be able to access the webui from the docker tab. It worked in this setup about 6 months ago.

I can access it via IP address and port. I cannot access it by left clicking the container and selecting webui. I get this in the browser address: about:blank#blocked. It's kind of a pain to have to remember the IP address versus the other method.

It's been a while since I've been able to access the webui for radarr and sonarr. I switched to qbittorrent from delugevpn, but the problem was happening with deluge. I have my lan networks defined in qbittorrent. The proxy setting are shown in the attached file. My docker containers run their own vlan with an IP address assigned. I'm not getting any port mappings on the docker page, and I used to get those. What could be causing the port mappings to disappear and me not get access to the webui? Or is it some other problem?

HI All, As of today, I just started getting an error that says my instance has been rate limited. The logs say it's a 503 CAPTCHA Error. F'ing Google. There doesn't seem to be a fix. I've read that this will eventually happen to self-hosted instances. Any ideas from the group? Mark

Yup this is it. Thank you for responding. I can drag it down to see the content. I'll check out the other UI's.

Thank you.

Hi All, Over the years, I've raised my docker disk size to 60GB. It's currently using 40GB. This started to not make sense. I've always cleaned up orphan images with cleanup appdata. I think I've used most of the scripts and command line entries to help clean it up. When I run Spaceinvaderone's check docker script, I get the output shown below. It doesn't make sense why it's high in usage. Does the output look off? Where should I go next? dockeruse.txt

Hi All, I'm trying to make the switch from delugevpn to qbittorrentvpn. I'm having a couple of issues. When I add a torrent link, it shows as active in the status bar. However in the main screen it does not show the torrent. The log says it was added. What would cause this to happen? Also, I'm seeing this error in the logs. UPnP/NAT-PMP port mapping failed. Message: "could not map port using UPnP[10.69.199.142]: no router found". I'm using mullvad vpn, and all containers using this as a proxy work fine. Should I ignore this, or is this causing the issue above?

Something is broken with the container. I use fixed IP's on all my dockers without issue. This one worked correctly up until a month ago. Something broke in a recent update where the webui link doesn't work. It works under bridge mode but does not work under a custom network with fixed IP, which it did for the past couple of years.

I did not try that. I never had this issue until the last update.

I mistyped it. There is no curly bracket. They are all square brackets. All my dockers use custom IP's and do not have this problem. This was an issue on page 216 and 217 of this thread with others. The fix was to force update the app. That did not help. This is only happening with binhex dockers. Also, there are no allocated ip's on the docker tabs. Please see the photo.

I tried this, and I still can't get to the web ui by left clicking the docker icon. I get a blank page using Chrome. Safari says can't open the pat "[IP}:[PORT:8112]" because the page address isn't valid. I can get to binhex containers using the actual IP address and port. I'm on a custom docker network with an assigned IP address. Any suggestions?

Hi All, I’ve been using whoogle through reverse proxy for a while now. Over the last several months, it randomly freezes, and I have to restart the docker. Has anyone else had this issue? There are no errors in the logs. I wonder if a reinstall would help.

Hi All, It was the processor. Replacement came today, and all is booted up.

I had to download and run memtest from memtest86.com because I needed a UEFI boot. Unraid's memtest, based on that, needs legacy CSM enabled. I needed my monitor and let it run 2 cycles. No issues were found. I updated the bios and still have boot problems. I tried each ram stick individually, and the problems persist. I doubt 2 ram sticks would go bad at the same time. It's either the motherboard or CPU. This is not going to be fun. I figure I'll start with the motherboard as CPU's have a lower failure rate. New mobo arrives tomorrow.

Update so far. I was trying to use a linux live cd to pull the last 6.12.x backup I had. All the live distros I've tried lock up after a few minutes. I installed the 6.11.5 backup to a flash drive. It got stuck at the bzfirmware checksum. So I put it into another usb port. It move passed the error but then got stuck on a plugin coral-driver/packages/5.19.17/._Coral... md5 error. I tried a another usb with this version and was able to boot in after a couple of attempts. The array didn't start because the license wasn't valid on the new disk. The UI eventually locked up, and I had to restart it. I figured the other usb slot might work for getting 6.12.3 working. I got past the checksum but then through an error "eth0" not detected. It went through the process of booting but did not assign IP addresses. Out of 3 USB's, I had all types of issues. Random restarts. Lockups at different points. I'm lost at this point. I'm going to run a memory test. Is it possible the motherboard is bad? Here are 2 pictures I took. One was interested because it was saying something about lack of communication between processors. This is the generic named photo. The other was after the UI froze when I got in. Any other suggestions?

That didn't work. Something in the configuration got corrupted in the downgrade. I can either find the backup on the disk (not optimal), or I have a backup of the last 6.11 I can go back to. If I did that, would it affect my dockers in anyway?

I copied the stock config files to the old usb. It got stuck in the same place. I copied my configuration files to the new usb, and now it gets stuck at bzmodules checksum Ugh. I'm going to try installing 6.12.4 and copy my files over and see if that works. At least this way I can get to my backup and restore it.

That's a good idea. Although if that is the case, this is going to suck to fix, meaning I'll have to find the backup on the drive.

The new usb worked. I'm assuming I put the config folder back on and all should work.