strike

@Biloxi_1 , @eb3k Have any of you tried nuking the docker image and re-download all your containers? This can solve many weird issues, so if you haven't tried it you might wanna give it a go. With CA's previous apps you'll be up and running as it was in about 3 min. If this doesn't work you'll have to post full debug logs which I can't see either of you have done. Without logs you most definitely won't get any help.

Regading privoxy there has been a couple users reporting the same. I don't remember the exact detalis, but I think it was something about deleting the privoxy.conf file or something. Use the "site" option in a google search an you should find it

Yeah, I think so. Should be the same setup as this container I believe. Though I havn't tried it so don't quote me on it

Can you give an example? Like filename and what medusa reports as quality vs what you think it should be. Also, have you tried to rescan your shows? Go to mangae->mass update->select the shows under the rescan column and submit

Do you have this many torrents seeding? Then that's probably your issue. Deluge does not handle many torrents well, you should try rtorrentvpn instead which are reported to handle many torrents much better. If your container is stored on a cache pool, this can also part of the issue. Try switching to a single cache drive instead or use an unassigned device to store this container. I've had this issue myself on a cache pool, when I went back to only a single cache drive the issue was solved.

Are you running the container with "privileged" mode ON? If not you should turn it on or else it won't work.

By default, it's just the root user that can log in via ssh, with the ssh plugin you can allow other users to login via ssh as well. You can also block root access if you wish. For security, it would be best to block root access and just give normal users access. That's what the user list is for, so you can configure ssh access on a user level.

@ashman70 The way to deal with this in medusa is to add the particular release group to the global ignored words. That will stop medusa from grabbing them. If those eps don't have a release group in the name try to find some other word/words that are specific to those releases you don't want and add them to the ignored list.

No, but I think you can do it on the router level. If your router supports that. I haven't tried it tho, since I got everything working fine and don't need to. Edit: I see now that there is a routing table in the unraid network settings. Maybe you can play with that.

I'm happy to provide logs or whatever if it helps others to get it to work

That's by design. If you want your dockers to be able to communicate with each other they either all have to be on the normal bridge or all on a custom bridge with fixed ip's.

But it does work, I've used a custom bridge with a fixed IP for a while now :) Does the provider come in to play at all? I don't think it should, but then again I'm not a network guru.. And there must be others then me got this working, for sure

What is the purpose of this 2nd server, is it just for backups? If so I would just run a script which utilizes rsync over ssh. Then your backup will run over an encrypted ssh tunnel. The script will power on the server, run the backup, send you an e-mail with the log after it's done then power off the server. You can use the user script plugin to set up a cron job so it runs once a week or something. You can take a look at these threads. https://lime-technology.com/forums/topic/52830-syncronize-servers-using-rsync-over-ssh-next-door-or-across-the-world/ https://lime-technology.com/forums/topic/68886-unraid-as-a-rsync-targetserver/

On ESXi are you sure you had an incoming port configured? If not, that could be why the speed was so low. From the FAQ:

Have you tried my suggestion a few posts up?

Yeah, this looks to be an emby issue. There's several post about it on the emby forums, and it looks like the devs are looking into it. It looks like you haven't enabled debug logging in the emby settings (you should see debug entries in the log), you should do this an post a new debug log in the threads on the emby forums where you have posted. You can also try to add one library at the time to try to find out if you successfully are able to add/scan a library without the container crashing. In doing so you'll also find the offending library causing the crash which could be helpful information.

@wgstarks didn't read the whole log, he was just seeing the top part. It all looks good from here Sometimes there can be weird issues happening with a container which there is no obvious solution for, your issue seems to be one of those. The one thing that can help (I'm not saying this is always the case) is to delete not only you docker container, but the whole docker image. This is the image which stores all your docker containers. I've seen many cases where weird issues are solved by doing this. By doing this all your containers will be deleted. Fortunately, in unraid it's very easy to get all your containers back exactly as they were without even have to fill out the container template again. As long as you don't delete the appdata everything will be exactly as it was before you nuked the docker image. Here's what you do: 1. On your unriad webui go to settings->docker, set "Enable docker" to "NO", click the button on the top right to switch from basic view to advanced view. Now there will be an option to delete the docker image, and you'll want to do that. 2. To recreate the docker image simply set "Enable docker" to "YES" 3. Now go to the apps tab and hover over the "hamburger menu" to the left and click on "previous apps", here you'll find all of your previous apps and you simply install all of them by selecting them and click install selected applications. 4. Now you have all your apps back as they were with no settings/data lost I have done this myself with a weird issue with deluge where the label plugin got disabled all the time and after I did this it never happened again.

Btw to all having issues with setting a static IP on a custom network, edit the container and set "Privileged" to ON, then Voila!

Oh, then my bad.. Doesn't say on their website, at least what I could see

I doubt he'll respond today, he normally doesn't work weekends. You'll just have to chill til tomorrow if nobody else will take a shot. Why do you use slickvpn anyway? From what I can see they don't support port forwarding so torrenting is gonna be slow and peers can't really connect with you. You and everybody else would be better off if you switch to another provider which supports port forwarding.

If that doesn't help you should search the thread and you'll find at least a couple users having the same issue. I don't remember how/if they solved it tho. If all else fails nuke your docker image and reinstall all your containers, usually helps with weird issues.

Then I'm stumped. You better wait for the expert @binhex to chime in

@Odessa you shouldn't be using the NL endpoint anymore see https://lime-technology.com/forums/topic/44109-support-binhex-delugevpn/?do=findComment&comment=433617

I'm using br0 with a static ip with no issues. Only thing I did was to set it in the template

idk actually, but mine is anyway You should change your password tho as you forgot to redact that in your last log. Good news is that the warnings from your last log are gone. But I think you're missing some files in your openvpn folder. If it's not baked into your .ovpn file you usually have to have a .crt file and a .pem or .key file in your openvpn folder. You'll get them form your vpn provider. The other thing that could be an issue is your username. If you are able to change it you should, please use only 0-9, a-z, A-Z if you're able to change it.