AnnabellaRenee87

Got an odd problem. I can login with the local IP Address:port. But if i try to login with my WAN Address (Using a Reverse Proxy and a Subdomain) it just accepts the password loads for a second and brings up the password screen again. I've made sure the Daemon "Allow Remote Connections" is enabled and triple checked it in core.conf. I want to add that this had been working for years. I tried it on several browsers, thought it was a DNS issue, tried another PC because i was too lazy to flush the DNS on my main computer. Went to Cloudflare tried toggling proxied off

Not working for me for some reason, I'm on PFSense with UPnP turned on for the Servers IP. Here's the logs it generated. Command timeout 12 stdbuf -o0 upnpc -m br0 -l 2>&1 Status 0 Results upnpc : miniupnpc library test client, version 2.1. (c) 2005-2018 Thomas Bernard. Go to http://miniupnp.free.fr/ or https://miniupnp.tuxfamily.org/ for more information. List of UPNP devices found on the network : desc: http://10.0.0.2:8096/dlna/9b902c51-b640-4805-9413-713cac1323ab/description.xml st: urn:schemas-upnp-org:device:MediaServer:1 desc: http://10.0.0.2:8096/dlna

Updated to 6.9.2 as well, my HP branded Seagate drives aren't spinning down either but the Hitachi drives are. Here's logs in case you all need them. server-diagnostics-20210408-1550.zip

Will I need Internet to do that? I won't have internet if I can't do the RMRR patch for my PFSense VM.

I'm sorry to ask a dumb question, but Is the Unraid-Kernel-Helper not on CA right now? I'm still on 6.9 RC2.

@doron you should add a donation link to your signature, I totally wanna buy you a coffee or beer for this plugin. My system uses a mixture of SAS and SATA drives and with how inexpensive SAS drives are on the retired server parts market I've got more SAS than SATA, I just hated how they never spun down. You have helped me save money in electric (can see that I'm saving about 100 watts of power on average now), so the last I can do is throw you a few dollars ❤️

I'm gonna take another crack at it in a few days. When I was working on it last I ended up catching COVID-19. Was dead for about 2 weeks, when I got sorta better work exploded, cats and dogs..... Sorry. Sent from my SM-G975U using Tapatalk

So I've been crazy sick the last week, I was diagnosed with COVID-19, I just decided to try nuking out all the folders in the plugins folder except the theme folder with my backed up appdata folder and now it's working. I could have swore I tested that yesterday. I blame the fever I've been having on and off yesterday and today. I'm sorry, carry on! Ignore the ramblings of the sick girl!!!! lol

The plugin isn't there, if i go through the appdata share and look in the same folder I can literally take everything out of it and it will still put that file back at /usr/share/webapps/rutorrent/plugins/extsearch/engines/. I even tried removing the Docker, it's Image, going stock, it will launch the first time just fine completely stock (yes, I removed the ~/appdata/binhex-rtorrentvpn directory) and it will do it on the second start.

So a LOT of debugging later I figured out what's giving the error; If I go in to the docker via the shell and go to /usr/share/webapps/rutorrent/plugins/extsearch/engines/ I see that for some reason I have JPopsuki.php and jpopsuki.php. If I manually remove the lowercase one (rm jpopsuki.php) and go to the site for my rtorrent and hit F5 the interface loads up normally. If I restart the docker it will auto re-create the file and I will be in the same situation again. I manually created the Uppercase version from https://github.com/Novik/ruTorrent/blob/master/plugins

Any idea why I would be getting the 500 server error with these? supervisord.log

How did you get it patched? I've put my efforts on hold right now, was just confirmed to have COVID-19. Been too sick to look at it lol. Sent from my SM-G975U using Tapatalk

For some reason I'm not able to get in to the WebUI. I'm getting this in the logs.

Don't get excited, an update on 6.9. I'm currently looking, line by line in the kernel's source code trying to figure out how to patch it. I'm trying to find information mentioned by rafalz on the ProxMox forums at "https://forum.proxmox.com/threads/compile-proxmox-ve-with-patched-intel-iommu-driver-to-remove-rmrr-check.36374/post-313467" Who's got it working on a 5.X kernel. If you want to help, please DM me. An alternative is to downgrade your BIOS to something sub 2009ish but I don't feel that's a very good workaround.

Can someone help me figure out what's filling my rootfs? server-diagnostics-20200623-1712.zip