Arcaeus

Ok so I figured out some of my issue. tl;dr I didn't have the current IP address set in my delugeVPN Privoxy, so the other programs routing traffic through there were just hitting a dead end. I went through and rewatched all of SpaceInvaderOne's setup videos one by one for Setting up a privoxy and setting up Radarr. I made sure all of my subscriptions were up to date and had the right information in them. Now, Sonarr keeps giving me an "Unknown exception: The operation has timed out.: 'https://192.168.2.87:8112/json'" error when trying to connect to Deluge, and an immediate "Test was aborted due to an error: Unable to connect to SABnzbd, please check your settings" error when trying to connect to SABnzbd. Both Sonarr and Radarr have the exact same Host, Port, and API settings. Radarr works but Sonarr doesn't. I've tried stopping and starting the container to see if that changes anything and it has no effect. Why would this be happening?

Hi all, I had setup my server awhile ago and it was working great. I let my NZBgeek, PIA, and Usenet.Farm subscriptions lapse and hadn't used Sonarr, Radarr, or SABnzbd in 6 months or so. I reactivated my supscriptions to all of those without otherwise changing anything. When trying to test the connection to NZBgeek indexer, I am getting the "Unable to connect to indexer, check the log for more details" error. Upon looking at the log, I see: 2020-06-04 17:49:11,444 DEBG 'sonarr' stdout output: [Warn] NzbDroneErrorPipeline: Invalid request Validation failed: This continues on the Download Clients tab, where testing the connection in Deluge gives me a "Unknown exception: The operation has timed out.: 'https://192.168.2.87:8112/json'". Testing the connection to SABnzbd gives this message in the log: 2020-06-04 18:00:35,989 DEBG 'sonarr' stdout output: [Warn] NzbDroneErrorPipeline: Invalid request Validation failed: -- Unable to connect to SABnzbd I went back to confirm that the current IP address setting were correct in each program, and that they matched the mappings in the Docker tab of Unraid. Everything that I can see matches, including all the API keys. I'm not sure what's wrong here or where to look to figure it out. Any help would be appreciated, and please let me know what else I can provide for you to help make this easier. Thank you!

I seem to be having an issue in the last few weeks of Radarr not being able to connect to my Newznab indexer. Sonarr however has no issues connecting to it with the same URL and API key. @trurl @Squid @binhex Any thoughts on why this may be?

@trurl Bumping this to see if you may know why it's doing this. I just downloaded Season 1 of a show, and that downloaded, renamed, and moved the files no problem. Clicked to download the second season, which it downloaded but the files are just sitting in the completed folder.

After looking in the folders, it almost seems like it's erroring out before it can complete everything as there are little files left over:

So I checked that and it seems to be ok because I see files coming through: The problem is, there are only some files that it is renaming and moving. If I look at my usenet_complete folder, I see this: What would cause only some files to be renamed and moved? And is there a way for Sonarr to scan for completed files to rename and move?

So I'm having an issue where my episodes are downloading, but Sonarr is not renaming and organizing them properly. SABnzbd seems to be downloading them fine, but then they just sit in my completed folder instead of being moved to the TV Shows directory so Plex can see them. I have the Media Management settings turned on here: But when I look in my completed folder, see this: And Sonarr should be able to move them to the correct directory (rather than copy) so I don't end up with duplicate files, correct?

...nevermind, apparently it fixed itself? Idk its working now.

So I was trying to run my SABnzbd traffic through privoxy. I put everything into Sonarr and Radarr fine. I put the same information into SABnzbd under the "Listening Port" section, and now I get this error: How do I revert back to the previous information, and set it up properly? @trurl or @Squid, you guys may know the answer to this too. Thanks in advance.

Nevermind, I solved it. I had the container path as /Media when it was mapped in Plex as /media. Thank you for your help!

@trurl So then rather than retrying all sorts of different paths, does it make sense to just delete the libraries in Plex and re add them? because all the files are the same and they've already been named properly and all that, the paths just need to be rebuilt so it can see it properly.

I just put the /Media mapping back as I thought that was all I needed. I didn't have the backup of my config file which was a mistake on my part, so I'm trying to remember exactly how I had the whole thing set up. Here is what I have for the template mappings:

I'm just having all of my media data on the array, and the Downloads share go to the array directly. My thinking is that the only things I would want on the cache drive would be the appdata share, and any other system related shares. It has seemed to work well for me in the past to keep the cache drive as open as possible so if I'm transferring files from my main computer, it has the space to do so. And shouldn't Mover also move files between the disks to balance the load out?

So these should all be set to cache:prefer? I was having issues originally with my cache drive filling up and then breaking my docker containers. However, these all seem like smaller system files and nothing that would take up 250gb. Edit: all shares listed above have been set to cache:Prefer

So I reinstalled this after my flash drive died. It installed and connected fine, but now when I try to play back my media, it can't find the file. I tried a Rescan of Library files, but that didn't seem to do anything. Here is the error I get: Thoughts?

So my flash drive died and I had to replace it. After I did, Mover seems to not run or do anything. I installed a fresh 4TB HDD that had been precleared, but every time I click to run Mover, it just refreshes the page and does nothing. Thoughts? diags posted just in case mediavault-diagnostics-20190420-1226.zip

So I've reassigned all of my drives in the exact same position as before. I have a message saying that "All existing data on this device will be OVERWRITTEN when array is Started" next to the parity drive. That should be fine right? That's just deleting the parity data and then rebuilding it?

As it stands right now, I can't access my old flash drive as it is not mounting when plugged into my computer. When I reassign my drives, I just have to make sure I assign the original drive letter that they had, right? What else should I be looking out for?

@trurl @Squid Ok, brand new flash with Unraid installed. Changed over the key to the new flash drive. I took a picture of my drives and their locations. So, it seems like I would install Squid's CA first, and then go through the process of re-adding all of the docker containers and everything. Is that correct?

@Cessquill Happy to break my stuff for your benefit haha

@trurl Awesome, thanks. I plugged my flash into my desktop and it won't mount, or is taking a long time to do so. I'll leave it for a bit and see if it figures it out. Is there any program that can run an automated backup of the flash every so often? Thank you so much for your help!

@Squid Just wanted to clarify, can I just wipe the existing one and start over? What is the best process you recommend for going through with this and saving what data I can? And how do you think this happened?

Ok, so is that a whole new flash drive or just wipe everything and start over? Is there a way to save whatever config data I have on there?

Ok, and would I have to go into my router and make sure it's assigning the same DNS to the Server? To change the network setting, I have to stop VM Manager and docker service. However when I go into Settings > Docker and change enable Docker to No and click Apply, it refreshes the page and it's still set to Yes. The same thing happens for VM Manager. All Docker containers are stopped.