Heciruam

I'm a little confused on how to do this. So I have to go and add a config text file to the GO directory (where is this?). Then create a device for the hw transcoder and after that just go to the emby docker, click on add another device. and fill out as above. Is there more to do?

Well then it's working.

So I'm running the Binhex docker. Is the command the same?

I just didn't know how to fill out the template. It works now. Thank you again!

I got one last question: Did you add that container path as "/data"? I'm worried that nextcloud will start writing to that share.

So the share shows up within nextcloud. When I try to access it I get an error message: External mount error There was an error with message: Empty response from the server. Do you want to review mount point config in admin settings page? I'm guessing I need to create a path for that share(/external mount) in the nextcloud docker template right? Also do I enable "enable sharing" in the "advanced settings" to be able to share something via link for example? Thanks for your help. I appreciate it!

Is it possible to "hardlink" a different share (not the share where the nextcloud files are) and make them show up from within Nextcloud?

If you reach the webui the VPN is on, if you can't it's off. If you want to be sure, go to ipleak.net and check the "Torrent Adress detection" _______________________________________________________________________________________________________________________________________________________ I have a different problem. Ever since I updated to Unraid 6.5.0 (I am on 6.5.3 now) the privoxy stopped working for me. So I tried to delete Docker as well as deleting the appdata out of the appdata share and reinstalling it but I can't get it to work. Does anybody have any ideas how can fix that? I also have rtorrentvpn running. It used to work there as well but it also doesn't anymore. So I'm not sure where I would find the problem?! cheers

Ah ok. Yes I found the checkbox. Thanks

I'm also wondering where I can delete a share? I can't find a button.

Yep it wasn't a fresh pull. I have been trying to set this up before. If I delete the docker and the data in the appdata share, will that be enough for a fresh pull or do I have to delete something else (like something of the bootstick) as well? Edit: Ok a fresh pull helped! Thank you!

So followed Gridrunner's video and everything went fine until now. I'm just not sure why I'm getting this loop in the log: " nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 " Can I go ahead with the tutorial or is something wrong? ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=Europe/Berlin URL=MYDOMAIN SUBDOMAINS=nextcloud,emby,sonarr,radarr EXTRA_DOMAINS= ONLY_SUBDOMAINS=true DHLEVEL=2048 VALIDATION=http DNSPLUGIN= EMAIL=MYEMAIL STAGING= 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d nextcloud.MYDOMAIN -d emby.MYDOMAIN -d sonarr.MYDOMAIN -d radarr.MYDOMAIN E-mail address entered: MYEMAIL http validation is selected Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for emby.MYDOMAIN http-01 challenge for radarr.MYDOMAIN http-01 challenge for sonarr.MYDOMAIN http-01 challenge for nextcloud.MYDOMAIN Waiting for verification... Cleaning up challenges IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/nextcloud.MYDOMAIN/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/nextcloud.MYDOMAIN/privkey.pem Your cert will expire on 2018-11-04. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run "certbot renew" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le [cont-init.d] 50-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 Server ready nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7 nginx: [emerg] a duplicate default server for 0.0.0.0:443 in /config/nginx/site-confs/default.txt:7

Thank you that was it. I changed the ports to 444 and 84 and they are forwarded. The Docker does start now, but I can't reach the webui. I'm trying to follow the cyanlabs guide and I'm also cross reading the dockerhub documentation. But I can't figure out why I can't reach the webui. Is the cyanlabs guide still up to date?

Hello guys. I'm having a little trouble right from the start. So I installed the docker, but I get an execution error(server error) when I try to start it. When I try to change the ports I get this error message: /usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint letsencrypt (562d830479261e90e8ad0a784fb2d05da0e1e122aae19e393fab7bf4d4c5bcc8): Error starting userland proxy: listen tcp 0.0.0.0:445: bind: address already in use. The command failed. What am I doing wrong? (I am running on Unraid 6.5.0)

Hello, I have a question regarding the ratio groups. Now that I set up sonarr and radarr, I had to set up some ratio rules. And everything works great. My problem is that the ratio groups are set to default after the docker gets restarted (within rutorrent). I checked the config file if I can change it there so my ratiogroups survive a restart. What am I doing wrong? Or where can I make my ratio settings permanent? Thanks in advance. p.s. thanks binhex for your great dockers

Does this docker support hardware transcoding with a "generic" intel i-core (i3 7100 in my case). I have Intel Quick Sync enabled in the EMBY UI but is doesn't seem to work. Do I need to passthrough the igpu to the Docker?

Nevermind I figured it out.

So how do I go at this? I simply saved the usb flash drive data. Now I just wipe that clean. Then prepare the usb stick as if I was installing a fresh 6.5.0 and go for a trial version. Then Power down and replace the license and the super.dat file? I saw on the forums that other people had trouble using the same USB drive. Do I need to buy another one first? Edit: I am asking this now becuase I can't reach or ping the server right now. So I believe now must be the time to do the reinstall.

Well I want to completely reinstall Unraid since something is wrong and I can't fix it. Maybe I updated wrong which explains why I seem to be the only one here having this problem. So I would just erase the boot drive, install the newest version (6.5.0 I believe.) and then I'm not sure if and how I can tell this new install to use the drives that already have data with parity, to not write over that. Lastly install and confige all the dockers again.

Yep I found it. Thanks. To the bigger issue: It looks looks like all traffic is routed through my delugeVPN docker and I can figure out why. I can't find anything on the network settings that would indicate that. Might downgrading back to 6.3.5 solve it. Will the Dockers not like this at all since some of them got updated after the unraid update? If I reinstall, can I save my data on the array with the shares? (I could not find anything on the wiki about that.) cheers

Where would this be. Under the "main" tab under unassigned device. Or Do I need to this for each dockers template where I assigned the "path"? Do I need to activate "destructive mode" to get the setting?

Thats true. But I could use the dockers in the mean time if they work. Or if I have to do a fresh install of unraid, schedule it when I don't need the dockers and have the time to configure all of them again. Edit: OK I just overwrote the new image with the old one and the dockers are running at least.

Sadly it didn't help. So if I would overwrite /mnt/user/system/docker/docker.img with the one I have backed up (stopping docker service first of course), will I get the old dockers back that were functioning but not updateable?

Yes I had DelugeVPN as well as rTorrentVPN (with privoxy enabled) installed. But I did not route any traffic outside the dockers through Privoxy (except some clients on my network). Where would I find if unraid traffic is routed through any privoxy? This is the first time I hear about jumbo frames. So I'll read up on it if I did something there. Edit: I think I just remembered that I forgot to uninstall the preclear plugin before updating to 6.4.0. Might that be the cause of all of this?

Well I did not enable ssl after the update. I thought I wouldn't need it since I only connect to unraid locally, but I will try if that helps.