blurb2m

Hey @ich777, have you given this any further look lately?

Updated to the latest this morning and I cannot load the history page. Getting these errors on the container logs: 2020-03-09 09:24:00 - ERROR :: CP Server Thread-13 : WebUI :: /home : Uncaught ReferenceError: page is not defined. (home:1016) 2020-03-09 09:24:00 - ERROR :: CP Server Thread-13 : WebUI :: /home : Uncaught ReferenceError: page is not defined. (home:1016) 2020-03-09 09:24:02 - ERROR :: CP Server Thread-13 : WebUI :: /history : Uncaught ReferenceError: page is not defined. (history_table.js:84)

@Hoopster @digitalformula Thank you guys so much!

I call my server skynet... anyone feeling froggy and want to help an unraider out?

Worked here. Hope you have a speedy recovery!

@Big Wig This was the first problem I was having setting TS back up yesterday. Edit your docker for teamspeak and click the "Add another Path, Port, Variable or Device" Config type: Variable Name: TS3SERVER_LICENSE Key: TS3SERVER_LICENSE Value: accept But now we are having a permissions issue, so I'd say add the variable and you will have to wait for another update to fix the next issue.

Ditto.

@sgt_spike Did the above help?

@sgt_spike oh! change that LE docker setting where it says "only subdomains" to "true". you only want to generate certs for bacnet that should definitely help, if not you do have another issue about a missing variable. hmm your settings look different, mine has Email, Domain Name, subdomain(s), only subdomains change Domain Name: "duckdns.org" (without quotes) click the button at the bottom that says "Add another Path, Port, Variable or Device" Config type: Variable Name: Subdomain(s) Key: SUBDOMAINS Value: bacnet Description: Subdomains you'd like the cert to cover (comma separated, no spaces) ie www,ftp,cloud, This should tell LE which certs to generate and not try to generate them for the duckdns main domain since you don't own that.

@sgt_spike My duckdns docker has my subdomain listed under SUBDOMAINS (your's would be bacnet) and the token is from the duckdns webpage. That is the only 2 edits I have ever made to duckdns docker. Within the LE docker settings I have my host port set to 9443 and that forwards to 443 inside the container. In my router, I have a port forward that forwards 443 WAN to <unRAID IP>:9443 So from the outside it looks like: subdomain.duckdns.org:443 -> router forwards this to <unRAID IP>:9443 -> to inside LE docker 443 Hope this helps.

@sgt_spike does duckdns.org have your updated IP when you log into duckdns website?

I tried the above for plexpy location ^~ /plexpy { proxy_pass http://192.168.99.224:8181/plexpy; include /config/nginx/proxy.conf; proxy_bind $server_addr; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Forwarded-Ssl on; auth_basic "Restricted"; auth_basic_user_file /config/.htpasswd; } Without the auth_basic it works and I can get in with plexpy login, but with the auth_basic in there I get a pop up for u/pw. I put in my username and password from my .htaccess file which is stored in /config/ directory but it takes me to a 403 Forbidden page. Thoughts? My .htaccess file only has username:hashedpw does it need to have the other stuff in there as well? *Edit: ran docker exec -it letsencrypt htpasswd -c /config/nginx/.htpasswd <username> to generate the .htaccess file and it works now.

location /sonarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.224:8989; this is mine

@aptalca it is a ubiquiti edge router lite. Every other one (radarr, sonarr, unifi, plexrequests) that I have setup through reverse proxy is accessible through IP:port I have hairpin NAT enabled "Nat loopback" Who know what madness I have done to my default file in nginx/site-confs.

@NeoDude I'm using LE, duckdns, nginx with my nextcloud docker. I can access from https://<server>.duckdns.org/nextcloud but internally I cannot access NextCloud. Driving me nuts! https://192.168.1.224/nextcloud/ brings me to a blank page within my unRAID webUI?? https://192.168.1.224:444/nextcloud/ redirects me to https://server.duckdns.org/nextcloud Anyone's help would be greatly appreciated!