casperse

I updated the files again and removed the set the Container Variable: ENABLE_PRIVOXY: no I got a complain about not setting the "Container Variable: VPN_OPTIONS?" But the UI started up again! :-)

Hi All I absolutely love this docker and the all in one approach making it secure! Installed this some time ago, and for some reason during the installation I was told to set the branch to: binhex/arch-delugevpn:2.0.3_23_g5f1eada3e-1-03 I have just removed this and updated it to the normal one: binhex/arch-delugevpn And I need a little help on how to get up and running again :-) (I USE PIA!) Some new arguments in the docker settings: Container Variable: VPN_OPTIONS? (I have looked but havent found what this should be filled out with?) Also in the log file I can see the following errors I have downloaded the new set of files from PIA: openvpn-nextgen.zip: And extracted the: ca.rsa.2048.crt DE Frankfurt.ovpn crl.rsa.2048.pem credentials.conf (Mine) Also set the Container Variable: STRICT_PORT_FORWARD: no What am I missing? As always thanks for a great forum and so many great people helping each other

Strange only when I list them in sepereate lines it works and I dont get the below error nginx: [emerg] could not build server_names_hash, you should increase server_names_hash_bucket_size: 64 nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html) server_name photo.domain1.dk; server_name photos.domain1.dk; server_name piwigo.domain1.dk; It works no errors (Even if the syntax is not right)

server { listen 443 ssl; listen [::]:443 ssl; server_name photo.doamin.dk,photos.domain.dk,piwigo.domain.dk,piwigo.domain2.dk; I tried combining them but got a strange error afterwards? nginx: [emerg] could not build server_names_hash, you should increase server_names_hash_bucket_size: 64 nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised

Maybee a stupid Q But is it okay to add multiple subdomains like this? server { listen 443 ssl; listen [::]:443 ssl; server_name photo.doamin.dk; server_name photos.domain.dk; server_name piwigo.domain.dk; And could I just add a piwigo.domain2.dk also? It might work but I dont want to go against the approved structure

Ok did a separate install and so far so good... pretty fast on my cache drive One thing I think there need to be some seperate setup og write access to the config file? Warning: mkdir(): Read-only file system in /config/www/gallery/plugins/piwigo-videojs/include/function_sync2.php on line 157 Any input on how to solve this?

Hi All Trying to find alternatives to the "DS Photo" page on my Synology using Unraid and dockers Looking here there are only 3 pages for this docker, is most people using something else? or does this just work great!? I have Nextcloud installed with MariaDB and it okay but not really a solution for a large TB photo/Video collection 😞 So if this is the solution, would it be okay to create a secound DB in my existing MarisDB docker for the needed DB to be used with Piwigo? Or better to install a separate Mariadb docker to only be used for this? I haven't really found any videos about the installation or usage of this, so please share your experiences Thanks

That did it thanks!

Yes its the same thing.... 🙂 set $upstream_app 192.168.0.12; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; I just used the variable in the last line proxy_pass http://192.168.0.12:8123; But I can see that it is sort of working seem to be some difference between this reverse proxy and the one Synology sets up I get to the webpage Looking at the log from my app I can see a new error message: shared.webhookError 1 Very strange? I made this for the Synology VM: server { listen 443 ssl; listen [::]:443 ssl; server_name mydomain.dk; include /config/nginx/ssl.conf; # add_header X-Frame-Options "SAMEORIGIN" always; add_header Strict-Transport-Security "max-age=15768000; includeSubDomians; preload;"; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; proxy_pass https://192.168.0.10:5001; proxy_max_temp_file_size 2048m; } } Synology domain looks to be working perfectly, any changes that I need to make? Its for a domain not a sub domain and I used the template for NextCloud as a base

Yes I see the docker name should be the IP (Making this to complicated) I tried but it doesn't seem to work include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app 192.168.0.12; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; I tested and its working accessing: http://192.168.0.12:8123/lovelace/default_view (The domain is getting cert. log file and I tried doing the mysub.* wildcard but with no effect

Hi All I am moving my last reverse proxy from my Synology box (Built in funct. with lets encrypt) Already have it working for all my dockers! and the instruction to setup and use the special "Proxynet" in Docker But my last servers are running as VM's not dockers so I cannot use the Network type: "Proxynet" I have two servers running as VM left with fixed IP's (Both virtual lan on Br0) Found the template for Home assistant: # make sure that your dns has a cname set for homeassistant and that your homeassistant container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name home.mydomain.dk; 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; # enable for Authelia #include /config/nginx/authelia-server.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 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app homeassistant; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } But not sure how to point it to a specific mysub.mydomain.dk? Or adding the IP (I would prefer not to have any mysub.* as wildcard have 4 different domains added (The work fine) Tried looking through the posts but so far have not succeeded getting this working (Trial & Error) Hooping to adjust the above to work with Synology port 5001 https running as a VM Thanks!

I did notice a big improvement in speed (Fast NVMe!) having Plex metadata and thousands of covers scrolling through a media library I have a near instant load - I also like the animation of scrolling through e media file (Generated for each media file if you have it enabled - hundred of Gigs). I can recommend buying the biggest NVMe you can afford - I went through 3 increasing the size (Would do it again if it was possible! but 2TB is max today) @mgutt is correct I have now have placed the following on my NVMe cache drive: appdata domains and the /mnt/cache/system/docker/docker.img Works great!

Anyone who can explain above situation? what would happen, is this the drawback of getting"overflow" from cache to array if you use static /cache/ path?

UPS! Thanks @trurlfor reminding me! - Just checked and after my last server migration I forgot I changed it back so it was set to 4 hours! So back to 1 hour now (Which I think is the default value)

I just have "Use default" I think that's 1 hour, so should be plenty

Since this only monitor the Plex service I think its ok to spin-up all drives up for a person accessing the system (Its a VIP service ) I was wondering what the timeout of this "Spin-up state" was? Since I can see accessing the Plex service and any library folder in Plex will draws +10% CPU every time! Even just accessing my Tautulli app on my iphone would push the script to activate wich is ok and by design! But what happens after you have accessed the library and you start to scroll through titles (They are all on the cache and loads to the browser cache) so the %CPU would go down again - how long time using "browsing titles" before it would spin down again? I use your test script to monitor activity of the script (4%): while true; do plex_cpu_load=$(docker stats --no-stream | grep -i plex | awk '{sub(/%/, "");print $3}') echo $plex_cpu_load if awk 'BEGIN {exit !('$plex_cpu_load' > 4)}'; then echo "Container's CPU load exceeded threshold" fi done It's a great way to see how and when it triggers

Finally - Thanks for all your help! - I think it's finally where I can use this script without spinning my drives up 24/7 But maybe I should make it around 4-5% - I still get some spikes after 3 min: 3.71 - Container's CPU load exceeded threshold And I think Plex activity of any user going into any media library will go way above 4%...even 10% in my testing Could be interesting to see if this actual have any noticeable impact on my electric bill since all 22 drives (Not including the 2 x parity drives) would be spin up during any playback of any movie. I actually did the separate UAD drive for frequent access in order not to do spin ups but that was 24/7 I think this is reasonable trade off... Thanks again Shouldn't it keep them spinning 2-3min between getting threshold again? keeping the drives spin-up?

WOw = 3 min! Script Starting Oct 24, 2020 11:59.04 Full logs for this script are available at /tmp/user.scripts/tmpScripts/Plex Preloader v0.9/log.txt Available RAM in Bytes: 11931406300 Amount of Videos that can be preloaded: 195 ....*.mkv*.srt tr: write error: Broken pipe tr: write error cut: write error: Broken pipe Script Finished Oct 24, 2020 12:02.09 Would like to do a test of the impact doing this but struggling how to do accomplish it? Needs to be "remote" for transcoding to kick in, how did you go about this during your dev/testing? Also some people have "remote transcode settings" fixed, would they overrule this? like 720P 4Mb/s and make the Preloader obsolete? Sorry for the many Q's again great work! your work in so many ways are really moving the "Media tweak" post forward!

Oh yes Stuff happens especially when we like us - go and do special tweaks (Stuff also happened for me, but the backup script from @mgutt is great and I use that for both emby and Plex (Appdata is huge! incremental backup is great) and of course the VM/Docker backup apps from the Unraid app community) This issue got me thinking, what would happen if you have the appdata folder as: And you have all your Appdata path in the docker changed to /cache/ But you do have the global share settings set: And you have a overflow of Plex metadata to appdata? (Prefer setting!) Would it write to the array? The path from the docker would only see the cache drive, so new data would not be available? How would this work? (Don't really want to test this in practice ) Sorry if this is a stupid Q...

Yes I pretty much have /Cache/ written everywhere now :-) Funny I said that it looked like a heartbeat didn't know there actually was one! (I will disable it when there is no traffic and test again) Thanks!

Maybe it's not the size of the srt files but the fact that they are located across 24 drives? Anyway your code is solid my server doesn't crash and it still run perfectly! just take some time LOL (I kept it at default 50%)

All of the srt files? for Movies & TV shows?! WOAW I have a average of 3-4 srt files (Nordic TV sometime also german close to DK - for each TV show and most movies) how does it have enough space left for loading the right subtitles? Just did a count on TV shows alone and I have around +40K srt files - so now I understand why it did run "forever" Average srt file is 30-45K = 1G Ram (TV only)

So I did the change to all appdata path to /cache/ (If I ever update my cache drive I need to remember to change this back before moving it back to the array! LOL) I then started to shutdown every docker! and every VM down! so only Plex docker was left running: And I keep getting these Bump as a heartbeat? So only thing left is Unraid Apps (Can not stop them, but I can start to uninstall them?) Or its the Plex inc Docker? that somehow are different than the others? (I could try another one?) Almost given up now! :-)

I got this one: Samsung SSD 970 EVO Plus 2TB the fastest I could get around a year ago! (Plex poster scroll loading ) So this should help I/O wait

I see what you mean! I only went into the dockers of Plex/Emby and changed the path to /cache/ I should do that for all of the running dockers /appdata/ path! I come back and report my findings when that's done