• Content Count

  • Joined

  • Last visited

Community Reputation

16 Good

About deusxanime

  • Rank
  • Birthday July 3


  • Gender

Recent Profile Visitors

1020 profile views
  1. Thanks, this fixed it for me! The next time I reboot (eventually) will be to install v6.9.2, or whatever is available at the time, so that will be my "permanent" fix. This got it going for now though.
  2. I updated mine to the latest build yesterday (or maybe day before?... recently anyway) and it looks like the issue is fixed. Not sure what caused it, but I can open the webpage in Chrome now again. Hopefully working again for you as well!
  3. I installed the latest update this morning, started the Duplicati container up after, and now I cannot get to the admin web page for it. It just loads forever but nothing ever comes up (just a blank page). Oddly, even Chrome just keeps trying to load forever and isn't timing out. The log doesn't show any errors or anything suspect that I can see. ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by ------------------------------------- To support LSIO projects visit: https:/
  4. Glad you were able to figure it out. Myself and some others have run into similar problems with that setting enabled. Has anyone acknowledged it even yet?
  5. I noticed a possible bug/issue with WireGuard on unRAID. I have a docker container that runs on a custom network and I needed it to talk to a container on bridge so I went into docker settings and enabled "Host access to custom networks". After doing so (and all the required stop/start/reboot), the containers could talk on the network and I thought all was well. Later that week I tried to use my WG VPN tunnel access (LAN access and tunnel through server to my home internet WAN) on my laptop and phone, which I'd used previously and worked great then, since I was on an untrusted Wifi
  6. As a counterpoint, I used to run the Plexpass/latest version and it screwed up things a few times for me. I can't remember exactly what, but it got annoying enough that I just set mine back to run the public version instead to avoid the early adopter headaches and it has been better in that regard. Honestly there's very little difference and usually only a short amount of time before changes and updates get pushed down to public from plexpass, assuming they don't break things. Plex itself is pretty stable, so unless there is a bug that made it into public that is affecting me, or s
  7. Shoko new version is out and looks like they've changed the docker path.
  8. Most likely nobody here is going to be a person who codes for the project directly, including @binhex. He just bundles and creates the docker template/container, not the application itself. You'll want to go to their github and create an issue there if you want someone to look at it. You could also look into trying Airsonic-Advanced instead as I believe they forked Airsonic and are more aggressively developing it, including performance enhancements. Perhaps that's something they've fixed. There is a docker template out there for it for unRAID in Community Apps.
  9. Plex internally makes it's own backups of the db as well I believe. In the same directory as the main db but appended with the date, like "com.plexapp.plugins.library.db-2020-05-02". Have you tried to go back to one of those using these instructions? Hopefully the backups aren't corrupt as well.
  10. I ran into a couple annoyances with the update over the weekend (v0.3.13) and thought I'd post here to let others be aware of them: 1. I had a download that didn't seem to be getting processed. It turns out there was a bug with the scheduler that it seems like the frequency you set to post-process your completed download directory was ignored and just sets to run every 24h instead. Manually forcing a post-process worked though. Github issue thread. Looks like they've already put up a new release v0.3.14 with a fix and it has been applied to the docker image. Just run another update
  11. Not sure what happened but seems like since I updated over the weekend that Medusa is no longer letting me log in with my credentials. Is there something that could have reset them or caused some issue with the latest update? Edit: No idea what caused it, but I shut down the container, went into config.ini and blanked out the web_password, logged in with no pwd, and then re-set the same password in Settings again. Seems to be working for now anyway.
  12. Good to know, I thought it was only Samsung drives affected. Definitely want to do some research before purchasing new ones then to be sure they'll work correctly. I blew $600 (at the time) on two 850 EVO 1TB drives specifically to use as my unRAID cache drives in a mirror and was quite frustrated that it didn't work (and still doesn't a couple years later!). Hopefully others will be spared the pain and expense.
  13. If you were planning to use them for this specific purpose and have the option to return them still, I'd say to do that. Right now there is no idea if/when this issue will be resolved. As far as what to replace them with, I think anything non-Samsung will do. I believe the issue is specific to their drives, but someone correct me if I'm wrong.
  14. I use rTorrent-VPN from binhex which also includes Privoxy and I use it with JDownloader. I just went under Settings in JDownloader, went under Connection Manager, and added the Privoxy address (same as my unRAID server since I'm not doing anything fancy with my docker network settings) with port 8118. That's what it is set to use in rTorrent-VPN, not sure if that is default or would be the same address/port for you. Also make sure to uncheck the "No Proxy" entry so it doesn't try to download stuff without the proxy/VPN.
  15. Just having a VPN isn't quite enough. What you need is a proxy to direct it through. If you are using binhex's DelugeVPN container, I believe he usually includes the Privoxy proxy host as part of that. If so, you should be able to go into JDownloader's Settings and look under Connection Manager. You'll want to add the Privoxy proxy there using your unRAID server's host/IP address (or the DelugeVPN container's IP if you have it set to use a different one from the unRAID server, which is uncommon) and port 8118, with user and password left blank. Also make sure to uncheck the No Proxy line so it