drawmonster

Has the recently released directory bug been fixed? I rolled back to 4.3.9-2-01 and have been there since the bug came out.

Well, I thought I had figured out my issue, but I'm getting timeouts and webgui freezes with private tracker torrents now as well. But I did get an error message in container logs now, finally. 2020-02-18 18:37:07,030 DEBG 'rutorrent-script' stderr output: 2020/02/18 18:37:07 [error] 687#687: *212 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.18.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.227:9080" Anyone seen this one before?

There are some fixes in those topics I linked too about the GUI freezing up on public torrents. Is it possible to use those on this container? Maybe from the command line or something? @binhex Also, anyone else reading this, are you able to use public torrents without the GUI freezing up constantly? I can recreate my issue very easily by adding any Linux iso torrent using the RARBG trackers. Upon adding, the GUI will quickly start becoming unresponsive. Trying to refresh it will hang and load for a few seconds or minutes or longer. Removing the torrent fixes the issue instantly. Curious if anyone else is experiencing this.

I'm not having any luck searching this thread for the answer I need. Basically, got everything up and running fine. VPN works. GUI works. But as soon as I add a single torrent, the GUI starts freezing up and becomes unresponsive. If I refresh the GUI, it will sit on "Loading" for a random amount of time. A couple minutes sometimes, others it never seems to load the GUI at all. Only changes I've made are the listening port to the one specified by my VPN. Is there something simple that I'm not finding in my searches to fix this? Edit: This appears to be related to "stuck" trackers. Found these threads for reference: and this github issue: https://github.com/rakshasa/rtorrent/issues/180 For me, a certain public tracker would immediately freeze the UI as soon as a torrent using that tracker was added. Removing that torrent would fix the issue. @binhex Have you ever dealt with this sort of issue in the past?

You know us. "PANIC, PANIC, FIRE, DEATH, PANIC, BEES!!!"

Completely removing and reinstalling CA also doesn't work.

Same here. MD5 error and no more apps tab.

Got this up and going with my reverse proxy. Got a couple issues though. I can't set a message for services directly. Global works, but messages, for say Plex, just don't appear. Also the time is off for the messages. If I set it for 3 p.m. my time, the message will have a time of 6 p.m. on the main page. Anyone else seeing these issues?

Diagnostics attached unraid-diagnostics-20200122-1651.zip

I added an external USB hard drive last night. It’s plugged directly into my Unraid server. The partition is named “Seeding”. Now I’m getting the above messages via email hourly. So it seems like the hard drive is being seen as an SSD possibly. And it’s trying to take SSD related actions on it. I did find and turn off the “discard” option in Unassigned Devices. I then rebooted the server. Still getting the error though. Anyone had this or know how I can fix it?

Two servers updated without a hitch.

Just had my certificates expire. Restarted the LE container several times, but it never tried to renew the cert. I also backup my appdata every night, so the container gets restarted nightly. Ended up having to run the renew command manually. I had gotten some emails saying the certificates were set to expire today, but I just assumed that was normal and that they would get renewed automatically. Guess not. cronjob running on Sun Nov 17 02:08:00 CST 2019 Running certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/mydomain.com.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert not yet due for renewal - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The following certs are not due for renewal yet: /etc/letsencrypt/live/mydomain.com/fullchain.pem expires on 2019-12-26 (skipped) No renewals were attempted. No hooks were run. I found this repeated over and over in the letsencrypt logs. So it new it was expiring, but never renewed it. Is there anything glaringly obvious that would keep the LE container from renewing the certificates automatically?

Anyone else getting this error in bottom left corner next to the "Array Started" text? Warning: unlink(/tmp/unassigned.devices/credentials): No such file or directory in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1088 I'm getting it on two seperate Unraid servers. Started a couple days ago with an update and still happening. unraid2-diagnostics-20191203-1235.zip

Has anyone got Organizr Server Authentication working with NPM? https://docs.organizr.app/books/setup-features/page/serverauth Also, I'm coming from using the Letsencrypt container. For my wordpress site, I just dropped it's folder into the "www" directory to get it going. How does that work with NPM? Thanks.

Yeah, 6.8 on the server with the files, 6.7.2 on the one mounting and trying to access the files. Is there anything I can check in regards to this being a network issue? Both are physically next to each other and I never got this issue until I upgraded the main server to 6.8. I was having very slow array performance with 6.7.2, but appears that 6.8 fixed it. I had the client server, that is doing the mounting, on 6.8 as well. I thought it may have been causing issues, so downgraded it to 6.7.2. I use pfSense for my firewall if that means anything.