mgladwin

Currently it's not possible in an easy way. What you could do is to add it yourself to the init file in /etc/service.d/tvheadend/run. Then append the http root switch at the end of the sv6 line. To get there you need to exec into the container with the command below. docker exec -it tvheadend bash Then if you don't want to use vi to edit the file install nano with the command below. apk --update add nano This should survive as long as you don't make any edits to the template or updates to the container. So make any changes to the template before doing the container changes above. Thanks saarg. I assume some sort of docker restart is required after? Can this just be done from the Docker WebUI as long as template is not changed and container not updated?

Is it possible to change the web_root parameter to get this working with nginx reverse proxy. I have tried everything (I can find on Google) but not sure if this is holding me back or not. I've tried adding the parameter in the docker template to --http_root /tvheadend and also tried --http_root="/tvheadend" but this command fails when I click done on the template page. My nginx code is:- location ^~ /tvheadend { include /config/nginx/proxy.conf; proxy_bind $server_addr; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Forwarded-Ssl on; proxy_pass http://10.1.1.12:9981; } I have omitted authentication (.htpasswd) as I figure tvheadend can handle this on its own using the users feature. Cheers.

Thanks for the quick reply mgladwin ! Yes, the app checks that the files have either a "rw-rw-rw-" or a "r--r--r--" permission. But I see an issue in the code: the check is inverted I'm uploading a release to fix this. Great work! All my warnings have gone. Thanks jbrodriguez!

Hi mgladwin, Hopefully you can help me look into this. In your log file (/boot/logs/unbalance.log), you should have a lot of lines starting with these messages: perms:User != nobody perms:Group != users perms:Folder perms != rwxrwxrwx perms:File perms != rw-rw-rw- or -r--r--r-- (mostly the last one, by what you're saying) Can you sample a couple of them and check the actual owner/permission on your disk ? Feel free to pm, if you need some assistance. Hi jbrodriguez, Thanks for your reply. Here are a couple of lines from my unBALANCE log as requested:- I: 2016/12/09 11:16:50 core.go:701: perms:File perms != rw-rw-rw- or -r--r--r--: [rw-rw-rw-]: /mnt/disk1/STORAGE/./AU D40/data/MENU2.TTF I: 2016/12/09 11:16:50 core.go:701: perms:File perms != rw-rw-rw- or -r--r--r--: [rw-rw-rw-]: /mnt/disk1/STORAGE/./AU D40/data/MENU3.DAH Here is the permissions as I see them on disk:- -rw-rw-rw- 1 nobody users 117028 Mar 31 2003 MENU2.TTF -rw-rw-rw- 1 nobody users 9578 Jul 5 2005 MENU3.DAH I hope this is what you meant. Are those lines in the log checking the file perms are either rw-rw-rw- or -r--r--r-- ? Or are the lines in the log the permission warnings?

Hi all, I have a similar problem with the permission errors in unBALANCE. I run a 'calculate' and it returns 12,000 "file" permission errors (no "directory" issues) such as:- 12000 files(s) with a permission other than '-rw-rw-rw-' or '-r--r--r--' I run the FCP 'Docker safe' permissions tool and it seems to do nothing to as far as unBALANCE is concerned. Running another 'calculate' returns the same amount of errors. I manually edited permissions using the command line and got it down to 100 or so 'file' permission errors but it created two new 'directory' issues. I then ran the FCP tool again thinking this might work now however it fixed the directory issues but returned the 12000 file permission errors again. I also found a couple of scripts from gfjardim on these forums and they were:- find /mnt/user/ -type f ! \( -user "nobody" -o -group "users" -o -perm "660" \) -exec chmod 660 '{}' \; -exec chown nobody:users '{}' \; find /mnt/user/ -type d ! \( -user "nobody" -o -group "users" -o -perm "770" \) -exec chmod 770 '{}' \; -exec chown nobody:users '{}' \; I cant follow exactly what the commands are doing (lack of knowledge) but i assume its 'find everything that isn't nobody:users and perms 770 for dirs (or 660 for files) and changes it to this. I ran these two commands on /mnt/disk1/ as going by the unBALANCE log this is disk with the 'offending' files on it. I also tried changing a portion of the scripts above to -exec chmod 666 as this is what i believe unBALANCE is looking for but this also didn't work. I don't want to run the move without correct permissions for obvious reasons and would love to get this working properly. I am sure this is user or configuration error my end but i just cant work it out. Any help appreciated. Cheers. I tried both of these and they also didn't remove the permission issues.