impalerware

Did the ddns-updater template disappear? Doesn't show up when searching anymore.

Anyone getting this when HDR tone mapping is enabled? This is on a i5 12400.

I love the flexibility unraid gives me with different drive sizes and swapping out smaller drives for bigger ones. For 2020 I would love to see a revamped cache pool management interface.

Just did a force update of the container from the unraid gui and started working again. Very strange.

Started getting a 502 Bad Gateway coming from the nginx on the docker. Has been working for for weeks. The nginx error log from the docker has: 2019/07/17 12:04:02 [error] 331#331: *58 connect() failed (111: Connection refused) while connecting to upstream, client: 10.8.0.2, server: _, request: "GET / HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.30.70:8443", referrer: "http://192.168.30.70/Docker" root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='nextcloud' --net='bridge' --log-opt max-size='50m' --log-opt max-file='1' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '8443:443/tcp' -v '/mnt/user/nextcloud':'/data':'rw' -v '/mnt/user/apps/nextcloud':'/config':'rw' 'linuxserver/nextcloud' 83f96cabb70714e96a1ac2c75894fe6917ca7bda9e30dfbd07f10c2b00d380de

Where do the logs go for this container? I have an empty logs folder inside the ombi folder. Trying to troubleshoot some newsletter issues.

I was getting the blank page as well. It looks like this container doesn't like having the default webui port changed. Setting the host port 3 parameter to anything other than 8080 produces the white page.

Mine didn't come back up. Well sorta. The logs showed that it came up fine but I couldn't connect. Almost like the port wasn't mapped/opened/working. A restart of unraid solved the issue though.

Does this container auto update? Mine is stuck on 1.7.2 while 1.7.4 is out. What's interesting is, I set this up yesterday for the first time and it did the 1.7.2 version instead of the 1.7.4 version which looks like has been out for a few days now.

Is anybody else's custom port keep getting turned off in the plex plugin after every plex restart or update?

I can't believe I missed the extra single quotes when I looked at the file. Removing them fixed it for me as well.

Password looks good. Where's the script that does the login? I can try running it manually.

I did change my plexpass password recently and went to set it on the page when I noticed the error. Maybe the password isn't getting stored properly in the new plugin?

Mine is throwing the same error for plexpass also.

Does it make sense to add the fstrim command to the end of the mover script? This way everything is moved off the cache ssd drive. Then the ssd gets trimmed.