SimplePete

It works! My 1070 now goes from P0 at 33W to P8 at 13W at idle (no transcoding in Jellyfin). I and my electric bill thank you!

Did you ever get this to work? I cannot get it into the P8 state either.

Thank you! I changed the bridge in the docker for the nextcloud container and upon restart it worked. I can now access it remotely, however I cannot seem to get it to work locally however. When I go the corect IP in firefox it tells me "The page isn't redirecting properly". I have changed in the config to add to the array the IP: '192.168.1.*' but still no luck. Do you have any suggestions as to what is causing this?

Hi there. I have an issue with using the reverse proxy set up for nextcloud. In the nextcloud.subfolder.config it says: ## Version 2020/12/09 # Assuming this container is called "swag", edit your nextcloud container's config # located at /config/www/nextcloud/config/config.php and add the following lines before the ");": # 'trusted_proxies' => ['swag'], # 'overwritewebroot' => '/nextcloud', # 'overwrite.cli.url' => 'https://your-domain.com/nextcloud', # # Also don't forget to add your domain name to the trusted domains array. It should look somewhat like this: # array ( # 0 => '192.168.0.1:444', # This line may look different on your setup, don't modify it. # 1 => 'your-domain.com', # ), When I try to do this for my docker container of nextcloud, if the line 'overwritewebroot' => '/nextcloud', is inserted it prevents me from accessing nextcloud locallay - it says that "The page isn't redirecting properly". And when trying to access remotely SWAG displays "502 Bad Gateway". My nextcloud config.php is as follows: <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'xxxxx', 'passwordsalt' => 'xxxxx', 'secret' => 'xxxxx', 'trusted_domains' => array ( 0 => '192.168.1.123:12345', 1 => 'MYSITE.duckdns.org', ), 'dbtype' => 'mysql', 'version' => '21.0.0.18', 'overwrite.cli.url' => 'https://192.168.1.123:12345', 'dbname' => 'nextcloud', 'dbhost' => '192.168.1.123', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'nextcloud', 'dbpassword' => 'xxxxx', 'installed' => true, 'trusted_proxies' => ['swag'], 'overwritewebroot' => '/nextcloud', 'overwrite.cli.url' => 'https://MYSITE.duckdns.org/nextcloud', ); If you could give me some advice as to what I am doing wrong I would be really greateful.

You were right, I had port forwarded it on my router without realising it *Doh* I have another issue with setting up photoprism, there isnt a sample file for that one. My set up is as the following: location /photos { return 301 $scheme://$host/photos/; } location ^~ /photos/ { # 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, also customize and enable ldap.conf in the default conf #auth_request /auth; #error_page 401 =200 /ldaplogin; # enable for Authelia, also enable authelia-server.conf in the default site config #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app PhotoPrism; set $upstream_port 2342; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } This makes it accessable via my domain name however the site is uninteractable - It just shows a large logo. There is a config file displayed on the site for setting up photoprism with nginx however I don't really understand it. How would I re-write mine? The sample config is as follows: http { server { server_name example.com client_max_body_size 500M; location / { proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $host; proxy_pass http://photoprism:2342; proxy_buffering off; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } } Any help would be appreciated. SP

Hi Saag, well why am I able to access the web gui via http? Shouldnt it be disabled then if it poses a security risk? SP

Good morning. Ok so what I mean by login section is this: I can access the above screen over https when the default file contains the code: location ^~ /login/ { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.222:80/login; #rewrite /login(.*) $1 break; } However it does not allow me to login to my server, on entering username/password it just refreshes the screen - I dont think its submitting the data as when entering incorrect login info it doesnt say that the data userame/pass was invalid. I can connect remotely to the login via normal http and it will submit the login details. However obviously I dont wish to do this over http so this is not currently a solution. Thank you!! I hadnt set up a custom bridge, that was the issue I was having with the 502 error. Jellyfin and deluge are now working as expected. Now if I can only get the login screen to work then I think I'm good with Unraid. SP

Hi everyone I'm currently testing out Unraid (havent yet purchased a license) I'm thinking that unraid might be what I'm looking for. The only issue I'm having is with accessing my docker containers outside of my network with SWAG. I'm currently running unraid version 6.9.0-rc2 I have been playing with the default file in site-confs folder of swag, but I'm not getting anywhere. I have managed to access the /login/ section over ssl however when entering in my credentials it doesnt foward me to the dashboard, even entering in the wrong details doesnt seem to do anything it just reloads the page. My default file contains the following: # sample reverse proxy config for password protected couchpotato running at IP 192.168.1.50 port 5050 with base url "cp" # notice this is within the same server block as the base # don't forget to generate the .htpasswd file as described on docker hub # location ^~ /cp { # auth_basic "Restricted"; # auth_basic_user_file /config/nginx/.htpasswd; # include /config/nginx/proxy.conf; # proxy_pass http://192.168.1.50:5050/cp; # } location ^~ /login/ { include /config/nginx/proxy.conf; proxy_pass http://192.168.1.222:80/login; #rewrite /login(.*) $1 break; } # location ^~ /deluge/ { # include /config/nginx/proxy.conf; # proxy_pass http://192.168.1.222:8112/deluge; # rewrite /deluge(.*) $1 break; # } } I have tried playing with getting deluge and jellyfin working however with no success, when using the template files (subfolder ones) I get a 502 Bad Gateway error. My deluge file is set up the following way - note changing of "set $upstream_app binhex-delugevpn;" to be the same as the docker container name as I found in a guide. ## Version 2020/12/09 # deluge does not require a base url setting location /deluge { return 301 $scheme://$host/deluge/; } location ^~ /deluge/ { # 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, also customize and enable ldap.conf in the default conf #auth_request /auth; #error_page 401 =200 /ldaplogin; # enable for Authelia, also enable authelia-server.conf in the default site config #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app binhex-delugevpn; set $upstream_port 8112; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; rewrite /deluge(.*) $1 break; proxy_set_header X-Deluge-Base "/deluge/"; } When running swag I dont get any error in the logs with the current set up as outlined above. Any help would be greatly appreciated. As I said I'm close to pulling the trigger and purchasing the Plus package for Unraid but need to get this sorted first. Thanks guys. SP