DZMM

setting up a pfsense VM and passing through NICs is very easy. I've just done a screenshot of the VM setup page for a new pfsense VM. After start, you just setup pfsense as normal and treat it like a normal machine

http_user = xxxxx http_pass = xxxxxxxxxxxx

Copy the files from the instructions into your home-assistant appdata folder e.g. appdata/home-assistant/www and then add the config elemenets to your config file. If you're stuck I'd ask on the HA forum for more help as it's standard HA fare to be honest and not docker/unRAID related.

Excellent - thank you

I'm on 6.4.1 so the script doesn't work anymore. Do you mean pass through a sata port or add the drive unassigned? If the former, I didn't know you could do that

Could I pass a new drive through to a VM and test? I don't have a 2nd system anymore. I guess it should work

does /mnt/user/Warehouse/cablecutter/Inbox/ match the directory name in Deluge? Also, what happens when you click on post-processing in books? I used to use LL to import my books, but I now use Calibre to manage the library Here are my settings that work with Calibre: I'd recommend switching to the bookstrap interface (choose on the interface tab) as the settings are much better laid out

is anyone else having problems with file permissions with this docker? When I try to delete or move completed files in windows, I can't until I run the docker safe permission tool

I'm a bit confused about renewals as I'm getting emails from Let's Encrypt saying my cerys are expiring soon. Do I just ignore if the docker is working? I made changes to my domains just last week and in the logs it said obtaining new certificate, but I'm still getting warning emails???

Thanks got it all sorted by adding my keys: server { listen 80; listen 443 ssl http2; server_name qbit.domain.com; # Ensure these lines point to your SSL certificate and key ssl_certificate /config/etc/letsencrypt/live/domain.duckdns.org/fullchain.pem; ssl_certificate_key /config/etc/letsencrypt/live/domain.duckdns.org/privkey.pem; location / { proxy_pass http://192.168.50.84:8080/; proxy_set_header X-Forwarded-Host $host:$server_port; proxy_hide_header Referer; proxy_hide_header Origin; proxy_set_header Referer ''; proxy_set_header Origin ''; add_header X-Frame-Options "SAMEORIGIN"; } }

ok, I tried doing this via Let's Encrypt. I did a bit of googling and I found a config file that 'works' - I can edit docs in Nextcloud, but I can't access the collabora docker at office.mydomain.com although I can via the docker url. Happy as I can meet the primary objective, but if anyone can explain why config file for office is wrong please I'll be even happier: server { listen 443 ssl; server_name office.mydomain.com; # SSL settings ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_protocols 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; client_max_body_size 0; # static files location ^~ /loleaflet { proxy_pass https://192.168.50.74:9980; proxy_set_header Host $http_host; } # WOPI discovery URL location ^~ /hosting/discovery { proxy_pass https://192.168.50.74:9980; proxy_set_header Host $http_host; } # main websocket location ~ ^/lool/(.*)/ws$ { proxy_pass https://192.168.50.74:9980; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $http_host; proxy_read_timeout 36000s; } # download, presentation and image upload location ~ ^/lool { proxy_pass https://192.168.50.74:9980; proxy_set_header Host $http_host; } # Admin Console websocket location ^~ /lool/adminws { proxy_pass https://192.168.50.74:9980; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $http_host; proxy_read_timeout 36000s; } }

How did you do stage 2 and install the Apache bit? https://nextcloud.com/collaboraonline/

Has anyone got Collabora or Onlyoffice working with this docker?

1. Changes shares to array only 2. Run mover 3. New config change pool drives 4. Change shares back as required (prefer, use cache) 5. Run mover

Thanks - sorted unifi. Very happy as I can't use the unfi cloud access due to my firewall.

Thanks I wasn't aware of this - I've just gone this route

I'm back. The app feed was failing, so I tried deleting and reinstalling - but it won't install. I'm not sure if there's anything useful in here: Jan 25 14:32:16 Highlander root: plugin: creating: /boot/config/plugins/community.applications/community.applications-2018.01.20b.txz - downloading from URL https://raw.github.com/Squidly271/community.applications/master/archive/community.applications-2018.01.20b.txz Jan 25 14:33:01 Highlander crond[3039]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &>/dev/null Jan 25 14:33:03 Highlander ool www[8791]: /usr/local/emhttp/plugins/advanced.buttons/script/plugin 'install' 'https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg' &>/dev/null & Edit: Reboot did the trick. No idea what's going on with my connection - think my ISP is playing up

I think I did it all right (but obviously not!): #UNIFI CONTROLLER server { listen 80; server_name unifi.MY-DOMAIN.com; return 301 https://unifi.MY-DOMAIN.com; } server { listen 443 ssl; server_name unifi.MY-DOMAIN.com; # SSL settings ssl_certificate /config/etc/letsencrypt/live/MY-DOMAIN.duckdns.org/fullchain.pem; ssl_certificate_key /config/etc/letsencrypt/live/MY-DOMAIN.duckdns.org/privkey.pem; ssl_session_cache shared:SSL:10m; ssl_session_timeout 10m; keepalive_timeout 300; 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; proxy_cache off; proxy_store off; # Organizr auth # include /config/nginx/serverauth.conf; location / { auth_request /auth-admin; proxy_cookie_domain unifi.MY-DOMAIN.com $host; sub_filter unifi.MY-DOMAIN.com $host; proxy_cookie_domain $server_name $host; sub_filter unifi.MY-DOMAIN>COM $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header HOST $http_host; proxy_pass https://192.168.50.97:8443; proxy_hide_header X-Frame-Options; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /ws/ { auth_request /auth-admin; proxy_pass http://192.168.50.97:8443/ws/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } I get a privacy error on my LAN, and nothing off LAN. For qbittorrent, it loads...but, I can't use the menus e.g right-clicking to stop seeding etc. Is there a change I'm supposed to make in QBT, or should your config work ok? # QBITTORRENT CONTAINER location /qbt { return 301 /qbt/; } location ~ /qbt/(?<url>.*) { proxy_pass http://192.168.20.73:8080/$url; proxy_set_header X-Forwarded-Host $host:$server_port; proxy_hide_header Referer; proxy_hide_header Origin; proxy_set_header Referer ''; proxy_set_header Origin ''; add_header X-Frame-Options "SAMEORIGIN"; } PS I have my qbut config in default and unifi in site-confs/unifi which is a bit different to you - don't know if this matters

wow that site's a potential treasure trove - thanks! I've got QB working - thanks. For bonus marks, I tried to copy your unifi implemention but I'm getting security errors when i go to unifi.domain.com - do I need to do more than amend your https://github.com/gilbN/Nostromo/blob/master/Server/nginx/site-confs/unifi file?

Hi would you mind posting exactly what you've added for qbit please as I can't get it to work. Thanks

I've been using V18 for a few months now and it's good enough for production. The builds this month have really got quite polished, I think thanks to V17 development stopping. If you've got an Android TV you'll love the leanback and the search integration. It has better artwork support and performance seems a lot sharper to me - hard for me to tell though as I've been on V18 for so long, I've forgotten what v17 was like!

Following the above guide I managed to connect my printer to Cloud Print, but my jobs are failing - any ideas? *** Running /etc/my_init.d/00_config.sh... usermod: no changes usermod: no changes usermod: no changes *** Running /etc/my_init.d/01_config.sh... *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 21 Setting up watches. Watches established. Polling for jobs on Canon_MG6800_series Establishing connection to xmpp server talk.google.com:5223 xmpp connection established Polling for jobs on Canon_MG6800_series Job Google Cloud Print failed - Will retry Polling for jobs on Canon_MG6800_series ERROR Google Cloud Print Also, how do I add the printer to W10? Do I need to add users to CUPS? In windows I keep getting messages that I don't have enough permission to add my printer (https://192.168.50.74:631/printers/Canon_MG6800_series) thanks in advance

if you've assigned an IP to LE e.g mine is 192.168.50.80, then you have to assign an IP to all the dockers you want it to connect to e.g. I have 192.168.30.86 for nzbget. Then you reference that IP in the config file: location /nzbget { proxy_pass http://192.168.30.86:6789; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; you can't use dockers on Bridge anymore - they need to have a unique IP to be able to communicate with each other

I just tried to upgrade the plugin and I think it failed. So I uninstalled and tried a fresh install but no joy - help pleasehighlander-diagnostics-20180122-1934.zip Edit: Just tried again and ok - must have been a network problem

@bonienl I was a bit surprised by the extra addresses setup for the unraid server by the VLANs which affected my transfer speeds - is this normal?