munit85

I'm running unmanic on both servers now. My second server is a dual xeon setup. Can you think of a reason unmanic would only use one processor? I'm pegged at 100 percent usage on half my cores leading me to believe it's only utilizing one processor.. i did add "--cpu-shares=2" to extra parameters in an attempt to set unmanic at lower priority so it doesn't choke out my system.

click on the docker and click logs. It will show you the completed percent as it works along.

testing this out now. Am I able to adjust the monitored container extensions? I'm wondering about having it only look for .avi's and re-encoding them for better compatibility with remote players.

How hard would it be to setup a minimum file-size target for this? I'm imagining pointing this at my library of tv shows and having it re-encode all files greater than 3GB or whatever in an attempt to get the largest files encoded to smaller file size first.

I'm getting the following error: Dec 9 10:34:45 Jefflix nginx: 2018/12/09 10:34:45 [error] 10760#10760: *3860986 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.13, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "jefflix", referrer: "http://jefflix/Main" I believe this is due to me rebooting my second unraid server which this server has an smb share mapped to. Right now unassigned devices is just showing an endless refreshing dialog and smb shares won't load at all. It's just on the brink of locking the whole server up. Is there something I can reload to fix this error?

Is there a way to only have handbrake process .avi files? I imagine it would require a bit of code in the preconversion hook? my real goal is to point handbrake at my media folders and have it convert and replace any .avi files with .mp4 files to facilitate direct streaming in plex. Thanks

thanks for the followup. I've just been restarting it every few days. looks like they'll sort it out in due time.

same here.

I'm not getting what you mean about using cloudflare with dns. edit// Made a cloudflare account. added my website. went to namecheap and pointed nameservers to cloudflare servers as indicated updated file in dns-conf named cloudflare.ini with cloudflare email and api key, which i grabbed through their site updated docker values with dns validation and 'cloudflare' in dns-plugin field keep port 80->81 forward to route incoming connections correctly restarted docker and we're in business. double edit// Was working perfectly. Now I'm getting error 522 (cloudflare) when trying to connect.

thanks binhex. Been having the same trouble with PIA. At least I know its them and not the container.

Is there a way to adjust the system time for the camera's? Mine is off by several hours, as though its set to a different time zone. thanks!

I'm using it with some laview ip poe cams which are really hikvision cams. Working perfectly for me. records as I have it set. creates folders for each camera's recordings. I did add a raspberry pi camera that is running motion as a test and that also worked for me.

I'm always afraid to modify my config because I tend to break things since I don't really know what does what. It would be nice to increase security though.

Dragon the movie format change fixed the recording issue for me. anyone able to get this to run under a reverse proxy? Without a base url setting it just gives me an error when viewing over remote proxy. edit// I got it to work. I was missing two back slashes.

Thank you. The app deprecated the base url and instead stopped using absolute url's which they say solves the problem. I'll have a look around for solutions. edit// turns out the trailing slashes are very important. for anyone who comes across this. cams needs that trailing slash as well as the trailing slash after the port # location /cams/ { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.17:8765/; }

I have a question about multiple local ip's working with my website. eg. i have unraid on two servers. one at 192.168.1.11 running most dockers. and a second unraid server at 192.168.1.17 running a few more dockers (cameras mostly) Is it possible to connect to both internal ip's using letsencrypt on my 192.168.1.11 server? I have all dockers on 192.168.1.11 working fine, but i tried to add a *.17 and it doesn't seem to work. let me post my config file. it's the /security entry specifically. I'm trying to connect to motioneye for my cameras. server { listen 443 ssl default_server; listen 80 default_server; root /config/www; index index.html index.htm index.php; server_name _; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; 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; location = / { return 301 /htpc; } location /sonarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.11:8989/sonarr; } location /radarr { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.11:7878/radarr; } location /ombi { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.11:3579/ombi; } location /plexpy { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.11:8181/plexpy; } location /booksonic { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.11:4040/booksonic; } location /airsonic { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.11:5050/airsonic; } location /security { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.17:8765; } #PLEX location /web { # serve the CSS code proxy_pass http://192.168.1.11:32400; } # Main /plex rewrite location /plex { # proxy request to plex server proxy_pass http://192.168.1.11:32400/web; } location /nextcloud { include /config/nginx/proxy.conf; proxy_pass https://192.168.1.11:4343/nextcloud; } #NZBGET rewrite-command location ~ ^/nzbget($|./*) { rewrite /nzbget/(.*) /$1 break; proxy_pass http://192.168.1.11: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; } location ~ ^/nzbget$ { return 302 $scheme://$host$request_uri/; } location ~ /netdata/(?<ndpath>.*) { 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; proxy_pass http://backend/$ndpath$is_args$args; proxy_http_version 1.1; proxy_pass_request_headers on; proxy_set_header Connection "keep-alive"; proxy_store off; } }