a_n_d_y

1. Yes 2. If Disk1 is part of the array, it will constantly be writing to the Parity drive. You might look into the Unassigned Devices plugin to add a disk outside of the array (you'll need another spare disk for this) and then move your completed download to the array. 3. Edit the docker, then click "Add another Path, Port, Variable, Label or Device" Change Config Type to "Path" Enter a Container Path, ex. /new_download_location Enter a Host Path, ex. /mnt/Disk1/Downloads Click save The path /new_download_location will show up inside of the container and it points to /mnt/Disk1/Downloads. Go into the qBittorent webui, Tools > Options > Downloads. Change Default Save Path to /new_download_location.

Edit the docker container and put this into the repository field: binhex/arch-qbittorrentvpn:4.1.9-1-01 You can roll back to any release. Go to the Github page for the docker container and replace the text after the colon with the release number: binhex/arch-qbittorrentvpn:[release_number] If you want the latest release once an update that resolves these issues is available, change to: binhex/arch-qbittorrentvpn:latest

If the docker is running, but the gui is not accessible, give this a try. Edit the container, change to Advance View and in the Extra Parameters, enter this: -e HOMEBRIDGE_CONFIG_UI=1 I don't think you actually need the variables HOMEBRIDGE_VERSION, CONFIG_UI_VERSION, HOMEBRIDGE_CONFIG_UI, HOMEBRIDGE_CONFIG_UI_PORT if you do the above. They don't seem to do anything after the initial installation.

That stinks. Working over here fine. Might try removing the docker and image and then reinstalling with all the setting as is. Since the Config UI is just a plugin, if you have a running another Homebridge docker, could try just re-installing that plugin manually inside the docker container. Would be nice if someone was able to just port over OZNU's docker to be more Unraid compatible.

OK I think I figured it out. Config UI X installs as a Homebridge plugin. It defaults to port 8080. You should update config.json manually for the port of the UI and then it should work.

I happen to be using Network Type as Host instead of Bridge. You can either change it to Host or you'll have to pass the appropriate ports to the docker container (Homebridge service, GUI, possibly other stuff...) I believe that should do it.

I'm not 100% sure since I have not had to debug anything. In the UI if you click on the docker icon (top right) > Settings, there are some options to Debug and run in Insecure. Looks like DEBUG=Alexa* is just filter? Might be something you could ask OZNU about.

I can't directly help you with your question above. However, if you want to make using and managing Homebridge painless, including installing plugins, you should consider using the OZNU Homebridge docker. It has Homebridge Config UI X included: https://www.npmjs.com/package/homebridge-config-ui-x Community Apps > Search for "homebridge" > click "Click Here To Get More Results from DockerHub" Install oznu/homebridge Changes to Make: Repository: oznu/homebridge:latest Variables: /homebridge = homebridge appdata folder, ex. /mnt/cache/appdata/homebridge Enable UI: Add these variables HOMEBRIDGE_CONFIG_UI, set to 1 to enable HOMEBRIDGE_CONFIG_UI_PORT, set to 8080 or whatever port you want Then you can access the UI at the configured port above.

Anyone with experience running Node JS in docker? I tried using the official docker, but its not running. Not sure where to go from here.

Ah yes, thats the error I was getting using server authentication before.

Yes and no. I ran into problems with Sonarr and Radarr specifically. I can't remember exactly what the problem was, but I think it was permission denied errors when clicking on certain areas of those apps... might've been error 500 though. I changed to the cookie based authentication method instead. I believe the only thing you can't do is restrict a specific user to certain tabs. Works well otherwise in my use case.

Would you mind posting your settings.json and a screen shot of your docker configurations? Maybe we can spot the problem.

I'm really sorry, I mistyped above with this statement about your JSON file: If its "download-dir": "/downloads" then use "/downloads" as your Host Path. I meant "/downloads" should be your Container path, not Host Path! My bad. Anyways, if you're using this in Transmission now: "download-dir": "/downloads/complete","download-queue-enabled": true, "incomplete-dir": "/downloads/incomplete","incomplete-dir-enabled": true, Its looking for a folder "downloads" (with a lower case "d") in the docker container: /downloads --> /mnt/user/downloads/ If you already have a downloads share created named "Downloads" with a capital "D", then use this for Transmission (you should also have "Downloads" referenced in Sonarr): /downloads --> /mnt/user/Downloads/ When you set it as this: /downloads --> /mnt/user/downloads/ It created the share "downloads" with a lower case "d" Make the changes above to reference "Downloads" with a capital "D" and then delete the "downloads" share with the lower case "d" If you're using Windows to find the share on the network, I don't think it can distinguish between "Downloads" and "downloads". I think that should do it!

Just to be clear, you did not have a Downloads share already created? I would check the export settings of the share to make sure your SMB is exported.

If this is any help, from what I can remember I did this to setup: JSON "download-dir": "/downloads/complete", "download-queue-enabled": true, "incomplete-dir": "/downloads/incomplete", "incomplete-dir-enabled": true, "umask": 2, In /mnt/cache/Downloads/ I let Transmission create the "complete" and "incomplete" (torrent.part files) folders. Transmission /downloads --> /mnt/cache/Downloads/ Sonarr /downloads --> /mnt/user/Downloads/

Just verifying, what is your "download-dir" path in your settings.json file? If its "download-dir": "/downloads" then use "/downloads" as your Host Path. If your downloads folder is on your cache drive, ex. "/mnt/cache/Downloads" , try using "cache" in the path vs "user" We'll get this figured out!

I was having some minor issues with Sonarr and Radarr with the web server authentication. I changed it to cookie authentication and now they're working so far without issue. # redirect traffic to https://[domain.com] server { server_name [domain.com] www.[domain.com]; listen 80 ipv6only=off; return 301 https://[domain.com]$request_uri; } # redirect traffic to https://[domain.com] server { server_name www.[domain.com]; listen 443 ipv6only=off; return 301 https://[domain.com]$request_uri; } # main server block server { server_name [domain.com]; listen 443 ssl ipv6only=off; # SSL certificates and keys ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; # SSL settings add_header Strict-Transport-Security "max-age=31536000; includeSubdomains"; ssl on; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; proxy_buffering off; # Custom error pages error_page 400 401 402 403 404 502 /error.php?error=$status; # Organizr location / { proxy_pass http://192.168.1.3:82; include /config/nginx/proxy.conf; } # Handbrake location ^~ /handbrake/ { if ($cookie_cookiePassword != "[cookiePassword]") { return 403; } proxy_pass http://192.168.1.3:8083/guacamole/; } location ^~ /handbrake/websocket-tunnel { if ($cookie_cookiePassword != "[cookiePassword]") { return 403; } proxy_pass http://192.168.1.3:8083/guacamole/websocket-tunnel; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; add_header X-Frame-Options "SAMEORIGIN"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } # MakeMKV location ^~ /makemkv/ { if ($cookie_cookiePassword != "[cookiePassword]") { return 403; } proxy_pass http://192.168.1.3:8081/guacamole/; } location ^~ /makemkv/websocket-tunnel { if ($cookie_cookiePassword != "[cookiePassword]") { return 403; } proxy_pass http://192.168.1.3:8081/guacamole/websocket-tunnel; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; add_header X-Frame-Options "SAMEORIGIN"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } # MKVToolNix location ^~ /mkvtoolnix/ { if ($cookie_cookiePassword != "[cookiePassword]") { return 403; } proxy_pass http://192.168.1.3:8082/guacamole/; } location ^~ /mkvtoolnix/websocket-tunnel { if ($cookie_cookiePassword != "[cookiePassword]") { return 403; } proxy_pass http://192.168.1.3:8082/guacamole/websocket-tunnel; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; add_header X-Frame-Options "SAMEORIGIN"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } # Plex location ^~ /web { if ($cookie_cookiePassword != "[cookiePassword]") { return 403; } proxy_pass http://192.168.1.3:32400/web; add_header X-Frame-Options "SAMEORIGIN"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } # PlexPy location ^~ /plexpy/ { if ($cookie_cookiePassword != "[cookiePassword]") { return 403; } proxy_pass http://192.168.1.3:8181; add_header X-Frame-Options "SAMEORIGIN"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } # Radarr location ^~ /radarr { if ($cookie_cookiePassword != "[cookiePassword]") { return 403; } proxy_pass http://192.168.1.3:7878; add_header X-Frame-Options "SAMEORIGIN"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } # Sonarr location ^~ /sonarr { if ($cookie_cookiePassword != "[cookiePassword]") { return 403; } proxy_pass http://192.168.1.3:8989; add_header X-Frame-Options "SAMEORIGIN"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } # Transmission location ^~ /transmission/ { if ($cookie_cookiePassword != "[cookiePassword]") { return 403; } proxy_pass http://192.168.1.3:9091/transmission/web/; add_header X-Frame-Options "SAMEORIGIN"; proxy_pass_header X-Transmission-Session-Id; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } location ^~ /rpc { if ($cookie_cookiePassword != "[cookiePassword]") { return 403; } proxy_pass http://192.168.1.3:9091/transmission/rpc; } }

D'oh, some of my code formatted weird when pasting... just gotta deal. I setup the web server authentication so you can't access any of apps without logging into Organizr. More info here: https://github.com/causefx/Organizr/wiki/Authentication-|-Server-Based And then for Fail2Ban, add the organizer-auth.conf filter and add the appropriate code to jail.local: AppData/LetsEncrypt/fail2ban/ More info here: https://github.com/causefx/Organizr/wiki/Fail2Ban-Integration For Fail2Ban to work it needs to see the loginLog.json file, located here: AppData/Organizr/www/Dashboard/ Just pass that path through the Let's Encrypt docker and make sure the jail.local has the correct path. There's one issue with the Fail2Ban, it currently only see's the docker's IP address, ex. 172.17.0.2. To see the IP address from the originating source, gotta add a bit of code to Organizr's default site file: AppData/Organizr/nginx/site-confs/ server { listen 80 default_server; root /config/www/Dashboard; index index.html index.htm index.php; server_name _; client_max_body_size 0; # get real IP real_ip_header X-Forwarded-For; set_real_ip_from 172.17.0.0/16; real_ip_recursive on; location / { try_files $uri $uri/ /index.html /index.php?$args =404; } location ~ \.php$ { fastcgi_split_path_info ^(.+\.php)(/.+)$; # With php5-cgi alone: fastcgi_pass 127.0.0.1:9000; # With php5-fpm: #fastcgi_pass unix:/var/run/php5-fpm.sock; fastcgi_index index.php; include /etc/nginx/fastcgi_params; } } That should do it! If anyone sees any corrections or has suggestions, let me know.

Sure, I'll post what I've done to get Organizr to show up as the homepage. In LE's config folder: AppData/LetsEncrypt/nginx/site-confs/ I duplicated the default site file and created a new one. See attached for what I used for settings. The top 2 server sections are just so http and https traffic redirect to https://domain.com. This is just my preference so the URL looks a little cleaner. Then put the docker information in the "location /" section. # redirect traffic to https://[domain.com] server { server_name www.[domain.com]; listen 80 ipv6only=off; return 301 https://[domain.com]$request_uri; } # redirect traffic to https://[domain.com] server { server_name www.[domain.com]; listen 443 ipv6only=off; return 301 https://[domain.com]$request_uri; } # main server block server { server_name [domain.com]; listen 443 ssl ipv6only=off; # SSL certificates and keys ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; # SSL settings add_header Strict-Transport-Security "max-age=31536000; includeSubdomains"; ssl on; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; proxy_buffering off; # Custom error pages error_page 400 401 402 403 404 /error.php?error=$status; # Authorization location /auth-admin { internal; rewrite ^ /auth.php?admin; } # Organizr location / { proxy_pass http://192.168.1.3:82; include /config/nginx/proxy.conf; } # Guacamole # location ^~ /guacamole/ { # proxy_pass http://192.168.1.3:8084/guacamole/; # } # location ^~ /guacamole/websocket-tunnel { # auth_request /auth-admin; # proxy_pass http://192.168.1.3:8084/guacamole/websocket-tunnel; # proxy_http_version 1.1; # proxy_set_header Upgrade $http_upgrade; # proxy_set_header Connection "upgrade"; # add_header X-Frame-Options "SAMEORIGIN"; # proxy_set_header Host $host; # proxy_set_header X-Real-IP $remote_addr; # proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; # } # Plex location ^~ /web { auth_request /auth-admin; proxy_pass http://192.168.1.3:32400/web; add_header X-Frame-Options "SAMEORIGIN"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } # PlexPy location ^~ /plexpy/ { auth_request /auth-admin; proxy_pass http://192.168.1.3:8181; add_header X-Frame-Options "SAMEORIGIN"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } # Radarr location ^~ /radarr { auth_request /auth-admin; proxy_pass http://192.168.1.3:7878; add_header X-Frame-Options "SAMEORIGIN"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } # Sonarr location ^~ /sonarr { auth_request /auth-admin; proxy_pass http://192.168.1.3:8989; add_header X-Frame-Options "SAMEORIGIN"; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } # Transmission location ^~ /transmission/ { auth_request /auth-admin; proxy_pass http://192.168.1.3:9091/transmission/web/; add_header X-Frame-Options "SAMEORIGIN"; proxy_pass_header X-Transmission-Session-Id; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } location ^~ /rpc { proxy_pass http://192.168.1.3:9091/transmission/rpc; } }

Just got this working with Let's Encrypt. Pretty slick.

Are you able to better explain the problem? Just a little hard for me to follow. I'd like to help if possible.

IIRC, rpc-whitelist needs to be changed in the Docker container and not in settings.json. Setting it there will overwrite what is in settings.json. Other settings can be directly updated in settings.json. Just make sure the docker container is stopped, edit settings.json (might need to change permissions on that file first), and then restart the docker. Its a little finicky getting everything up, but once it is, its solid.

That did the trick, thank you.

How do I install an earlier version of this docker? 0.38.4 is giving me trouble.

I had similar problems, but adding the additional variables required resolved it: https://lime-technology.com/forum/index.php?topic=48899.msg534306#msg534306