Tuumke

Don't have DNS anymore. Updated my docker this morning. Not sure if its because of install docker pihole, or update of container Have tried several things like: - --dns=ipadressofpihole - add variable in template (Key3, DNS1, ipaddressofpihole) I can't use apt-get update, no DNS resolving Also nog ping or nslookup command available in the container itself...

This is just the Unifi controller right? I thought there was a standard config file for it in the letsencrypt docker from ls.io? I checked my docker, it has this file: user@TOWER:/mnt/user/dockers/letsencrypt/nginx/proxy-confs# cat unifi.subdomain.conf.sample # make sure that your dns has a cname set for unifi and that your unifi container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name unifi.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_unifi unifi; proxy_pass https://$upstream_unifi:8443; } location /wss { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_unifi unifi; proxy_pass https://$upstream_unifi:8443; proxy_buffering off; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_ssl_verify off; } }

I also have configured letsencrypt reverse proxy for subdomain nessus.subdomain.conf Note1: include /config/nginx/auth.conf points towards my Organizr setup. You might not want to use this server { listen 443 ssl; listen [::]:443 ssl; server_name nessus.*; include /config/nginx/ssl.conf; client_max_body_size 0; include /config/nginx/auth-location.conf; location / { include /config/nginx/auth.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_nessus w.x.y.z; ## Change to IP of HOST proxy_pass https://$upstream_nessus:8834; } }

I guess compiling plugins takes a long time?

Looks cool. Will give this a go later on

See: Note: This reply is specific to nextcloud, but it concerns the entire LE docker container. So it's harmless.

I got it working now Will post my config later -edit- I got my subdomains working with OrganizrV2 auth

Am on 6.7.0. Didnt notice FTP wasnt working since i personally dont use it. Buddy of mine said that his Kodi wasnt working anymore. Had to install the beta and copy over my proftpd.conf modifications. Works fine now.

Thats cool. Didnt know that. But does the community applications plugin support this?

Arrghh.. im trying to get subdomain working for Sonarr but i have troubles with setting it upo with Organizr authentication. The authentication part works, but the UI wont load api/config/ui gives a 404, same with api/config/status Everything else loads just fine. server { listen 443 ssl; listen [::]:443 ssl; server_name sonarr.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { auth_request /auth-0; error_page 401 =200 https://organizr.domain.tld/; location ~ (/sonarr)?/api { auth_request off; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_sonarr sonarr; proxy_pass http://$upstream_sonarr:8989/api; } include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_sonarr sonarr; proxy_pass http://$upstream_sonarr:8989; } location ~ ^/auth-(.*) { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_organizrv2 organizrv2; proxy_pass http://$upstream_organizrv2/api/?v1/auth&group=$1; proxy_pass_request_body off; proxy_set_header Content-Length ""; } The login to the domain.tld login page of Organizrv2 works fine. Auth works fine but i just can't seem to load the: https://sonarr.domain.tld/api/config/ui https://sonarr.domain.tld/api/system/status Any ideas? Sonarr doesnt have a url base configured... -edit- With the default sonarr.subdomain.conf.sample without organizr auth, it works fine..

meh... this is making it tempting to switch to docker-compose, does it not?

This! For security options, it would be nice to be able to put fo example MariaDB in a 'gapped' network that is not connect to internet, and have a nginx/apache/django/whatvere webservice that needs a DB have 2 networks

Slow as in health says that response time is 1000ms =/ also have a DEV setup with dockers and traefik, but that is on a Ubuntu VPS i rend. MS = 4~6 there..

Just upgraded, no issues so far.

Anyone else having issues that traefik is really slow?

Replaced the disk, parity is rebuilding now. Thnx for the help guys

TY

Ordered a new disk. Should arrive todat. Is it correct that replacing a parity disk is still this: https://wiki.unraid.net/The_parity_swap_procedure 1. Stop the array (if it's started) 2. Unassign the old drive (if it's still assigned) 3. Start the array (put a check in the Yes I want to do this checkbox if it appears (older versions: Yes, I'm sure)) 4. Stop the array again 5. Power down 6. [ Optional ] Pull the old drive 7. Install the new drive 8. Power on 9. Stop the array 10. Unassign the parity drive 11. Assign the new drive in the parity slot 12. Assign the old parity drive in the slot of the old data drive being replaced 13. Go to the Main -> Array Operation section 14. Put a check in the Yes I want to do this checkbox (older versions: Yes, I'm sure), and click the Copy button 15. Put a check in the Yes I want to do this checkbox (older versions: Yes, I'm sure), and click the Start button

Still ongoing with SMART extended self-test. It's the parity disk but i think it's going to need replacement if it takes this long =/

Still running?! self-test in progress, 30% complete

Running an extended test now.

Hey guys, I'm getting disk erros on my parity disk. All disks i have a pretty old by now and have ben running a long time. I'm suspecting they will need to be replaced in the near future, but i hope there is another way to fix these errors? Running on v6.6.6 Attached smart report from the disk with errors. nas-smart-20190116-0808.zip

Ofcourse . My bad i didnt report back.

I just found out, that you can set the community plugin to also check on dockerhub. Testing now

Never mind. I'm using FTP with TLS now, hope that's secure enough. Is it possible to have mod_shaper added to ProFTPd? http://www.castaglia.org/proftpd/modules/mod_shaper.html So we can limit bandwith per user? @SlrG ?