DieFalse

Due to the new design, nope.

Yep, gonna have to nuke and reload it.

Login with your plex id and password

Any chance of UDEV being added to the Plex docker anytime soon? Last I heard the bug causing it not to install was fixed?

Forgive my sleepiness lastnight, modprobe it87 force_id=0x8655 then sensors

Jack: run this command: modprobe it87 force_id=0x8620 then: sensors

What do you get from a terminal window when you type: sensors sensors-detect

Type IT87 where LM78 is and click save. then check the drop downs.

Right now 32GB however, upgrading today to new board/cpu with 128GB. Damned VM's keep wanting more lol.

Does this still work or is there a better way? I have had my USB die off and the downtime was not fun nor was getting my backup to actually load correctly.

Perfect!!!! That got what was different. 'overwrite.cli.url' => 'https://my.xxxxxxxxx.com/nextcloud', needed to be 'overwrite.cli.url' => 'https://my.xxxxxxxxx.com', now this works as anticipated. No clue why that would cause it to revert to https://IP vs domain.... strange! Thank you for supporting and helping even though its not 100% identical. It was very helpful.

My config.php is not complicated.... its the one you posted.... Maybe you mis-read and thought the nginx site conf was also in the config.php? here is Just the config.php ( and I will simplify it even more by removing redundancies) Config.php which has the overwritewebroot in it already. <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'ocgu1s592brc', 'passwordsalt' => 'saltremoved', 'secret' => 'secretremoved', 'trusted_domains' => array ( 0 => '192.168.1.175:444', 1 => 'my.xxxxxxxx.com/nextcloud', ), 'trusted_proxies' => array ( 0 => '192.168.1.175', 1 => 'my.xxxxxxxxxx.com', 2 => 'my.xxxxxxxx.com/nextcloud', ), 'overwritewebroot' => '/nextcloud', 'overwritehost' => 'my.xxxxxxx.com', 'overwrite.cli.url' => 'https://my.xxxxxxxxx.com/nextcloud', 'overwriteprotocol' => 'https', 'dbtype' => 'sqlite3', 'version' => '13.0.0.14', 'installed' => true, MAIL INFO REDACTED );

My "Domain.com" is under a commercial SSL certificate. I am using LE for my.domain.com only. I can not use domain.com to create a wildcard through LE. I don't want to continue to derail the thread to figure that issue out as I am soon going to be registering a new domain for use solely for the server, so I will address that then. As for this config, here are the two files I modified: Config.php <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'ocgu1s592brc', 'passwordsalt' => 'saltremoved', 'secret' => 'secretremoved', 'trusted_domains' => array ( 0 => '192.168.1.175:444', 1 => 'my.xxxxxxxx.com', 2 => 'www.my.xxxxxxxx.com', 3 => 'cloud.xxxxxxxx.com', 4 => 'nextcloud.xxxxxxx.com', 5 => 'my.xxxxxxxx.com/nextcloud', ), 'trusted_proxies' => array ( 0 => '192.168.1.175', 1 => 'my.xxxxxxxxxx.com', 2 => 'nextcloud.xxxxxxx.com', 3 => 'my.xxxxxxxx.com/nextcloud', ), 'overwritewebroot' => '/nextcloud', 'overwritehost' => 'my.xxxxxxx.com', 'overwrite.cli.url' => 'https://my.xxxxxxxxx.com/nextcloud', 'overwriteprotocol' => 'https', 'dbtype' => 'sqlite3', 'version' => '13.0.0.14', 'installed' => true, MAIL INFO REDACTED ); LE-NGINX-siteconf-default server { listen 80; server_name my.xxxxxxxx.com nextcloud.xxxxxxxxx.com cloud.xxxxxxxxx.com; return 301 https://$server_name$request_uri; #enforce https } server { listen 443 ssl http2 default_server; root /config/www; index index.html index.htm index.php; server_name my.xxxxxxxxx.com nextcloud.xxxxxxxxx.com cloud.xxxxxxxxx.com; #add_header Strict-Transport-Security max-age=31536000 always; add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always; 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; #PLEX location /web { # serve the CSS code proxy_pass http://192.168.1.175:32400; } #Main /plex rewrite location /plex { # proxy request to plex server proxy_pass http://192.168.1.175:32400/web; } location /stats { #proxy plexpy to server proxy_pass http://192.168.1.175:8181; } location /jackett { #proxy jackett to server proxy_pass http://192.168.1.175:9117; } location /couch { #proxy couchpotato to server proxy_pass http://192.168.1.175:5050; } location /sonarr { #proxy sonarr to server proxy_pass http://192.168.1.175:8989; } location /nowshowing/ { #proxy nowshowing to server proxy_pass http://192.168.1.175:6878/; } location /nextcloud { proxy_pass https://192.168.1.175:444/nextcloud; } location /htpc { #proxy htpcmanager to server proxy_pass http://192.168.1.175:8085; } location /request { return 301 $scheme://$host/request/; } location /request/ { proxy_pass http://192.168.1.175:3579; proxy_set_header Host $host; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Ssl on; proxy_set_header X-Forwarded-Proto $scheme; proxy_read_timeout 90; proxy_redirect http://127.0.0.1:5000 https://$host; } if ($http_referer ~* /request/) { rewrite ^/dist/(.*) $scheme://$host/request/dist/$1 permanent; } }

I ran into a problem where my SSL is not valid for https://sub.vanitydomain.com as I use a ssl for https://my.vanitydomain.com so I have to use /nextcloud to use this SSL, also, with 1&1 hosting, I can not get https://nextcloud.vanitydomain.com to goto a "port" as I can only forward 443/80 to one IP in my network. If I put nextcloud.vanitydomain.com I have no way to point it to nexcloud directly. The ONLY thing from the guide that changed was pointing to the /nextcloud instead of x.y.z There has to be a setting or configuration that changes the domain call to the internal IP. I understand the not "supporting" but can you atlease point me to what would revert to internal vs external? I have the overwrite cli/web/host all set to the right endpoints. I followed the guide in the first post and the link to the "letsencrypt nginx settings page" which also spoke about /x and showed the example for it.

I followed the tutorial in the first post and all works on the local network. When accessing the reverse proxy outside of the network it changes my domain to my internal IP and fails. from: https://myvanitydomain.com/nextcloud to https://192.168.1.175/nextcloud/ If I am on VPN it works app and all, off VPN, it fails due to this. What would cause this?

Yes it is reverse proxies through nginx letsencrypt, I have read back to page 6 and only see one mention of a grey login screen but have yet to see what causes it or the proposed fix. I can access it locally non proxied so I can assume it's in the reverse proxy configuration and maybe a permissions of a resource it cant see, kind of like serving the plex css addition of /web to make plex work correctly. Am I atleast on the right track?

I've been using and love this docker for several months now, however with the latest update (now has backgrounds on login page) the page will not load on any mobile devices. It says "Loading...." and then blanks out. Has anyone heard or seen this problem yet?

I have re-installed htpcmanager now 3 times. It will work for 2-3 days and then fails to start. I have psutil and smartctrl disabled in the docker as it can't find it however it errors out with this in the logs: 2018-03-10 15:26:38 :: root :: INFO :: Welcome to Hellowlol's HTPC Manager fork 2018-03-10 15:26:38 :: root :: INFO :: Loglevel set to info 2018-03-10 15:26:38 :: htpc.updater :: INFO :: Using GitUpdater engine 2018-03-10 15:26:38 :: apscheduler.scheduler :: INFO :: Added job "Updater.update_needed" to job store "default" 2018-03-10 15:26:38 :: modules.kodi :: WARNING :: No configured kodi-Servers. 2018-03-10 15:26:38 :: modules.newznab :: WARNING :: No configured Indexers. 2018-03-10 15:26:38 :: modules.stats :: ERROR :: Required package 'smartmontools' is not installed, or 'smartctl' component is not on the system path. Please install and try again.The current env path is: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 2018-03-10 15:26:38 :: htpc.server :: INFO :: Starting up webserver ******************************************************************* Starting HTPC Manager on port 8085. Start your browser and go to http://localhost:8085 ******************************************************************* 2018-03-10 15:26:38 :: cherrypy.error :: INFO :: [10/Mar/2018:15:26:38] ENGINE Listening for SIGHUP. 2018-03-10 15:26:38 :: cherrypy.error :: INFO :: [10/Mar/2018:15:26:38] ENGINE Listening for SIGTERM. 2018-03-10 15:26:38 :: cherrypy.error :: INFO :: [10/Mar/2018:15:26:38] ENGINE Listening for SIGUSR1. 2018-03-10 15:26:38 :: cherrypy.error :: INFO :: [10/Mar/2018:15:26:38] ENGINE Bus STARTING Info: SIGTERM received, exiting. 2018-03-10 15:26:40 :: cherrypy.error :: INFO :: [10/Mar/2018:15:26:40] ENGINE Caught signal SIGTERM. 2018-03-10 15:26:40 :: cherrypy.error :: INFO :: [10/Mar/2018:15:26:40] ENGINE Bus STOPPING 2018-03-10 15:26:40 :: apscheduler.scheduler :: INFO :: Scheduler has been shut down [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. 2018-03-10 15:26:40 :: cherrypy.error :: INFO :: [10/Mar/2018:15:26:40] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('192.168.1.175', 8085)) already shut down 2018-03-10 15:26:40 :: cherrypy.error :: INFO :: [10/Mar/2018:15:26:40] ENGINE Bus STOPPED 2018-03-10 15:26:40 :: cherrypy.error :: INFO :: [10/Mar/2018:15:26:40] ENGINE Bus EXITING 2018-03-10 15:26:40 :: cherrypy.error :: INFO :: [10/Mar/2018:15:26:40] ENGINE Bus EXITED Pre-work: root@NAS:# find /usr -name smartctl /usr/local/sbin/smartctl /usr/sbin/smartctl /usr/bin/smartctl

Hello MarkusMcNugen, First and foremost, Thank you for these! It's nice to see alternatives! Having used binhex's dockers, I have been able to verify that there is zero traffic going out if the VPN drops with his. How can I be sure of this with your qbittorrentvpn client? I like qbittorrent better than deluge and would love to use it, but I want to be certain it can not leak info.

Thank you, I have deleted your docker until this is implemented. My empty libraries are built in for automation needs. (uploads from cell phones/tablets etc for processing.) It sounds like Version 2.0 will work better for me as not all of my libraries are for every user. IE Adult is not available to all, nor is UserXUpload or Anime is not for all either.

I am receiving an error, I have confirmed config.yaml and advanced.yaml. root@NAS:~# docker exec nowshowing webreport -t -vvv /usr/local/sbin/webreport:128:in `block in getMovies': undefined method `each' for nil:NilClass (NoMethodError) from /usr/local/sbin/webreport:106:in `each' from /usr/local/sbin/webreport:106:in `getMovies' from /usr/local/sbin/webreport:377:in `main' from /usr/local/sbin/webreport:398:in `<main>' root@NAS:~# docker exec nowshowing emailreport -t -vvv /usr/local/sbin/emailreport:128:in `block in getMovies': undefined method `each' for nil:NilClass (NoMethodError) from /usr/local/sbin/emailreport:106:in `each' from /usr/local/sbin/emailreport:106:in `getMovies' from /usr/local/sbin/emailreport:377:in `main' from /usr/local/sbin/emailreport:397:in `<main>' root@NAS:~# docker exec nowshowing cat /opt/config.yaml ---

Yep.. I broke something. After getting the LE challenge fixed and server up, no response on http or https. [cont-init.d] 50-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Server ready *** Found it. default had the old ports in it. updated and all is back online.

Yea, I got that part after you said it was a separate process. I don't know what broke, Its on port 80 and 443 with forwarding. I checked by moving the mapping of another process to port 80 and 443 and its not blocked by isp. Maybe I need to hose it. strange.

Got ya... I must have broke something then. (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain ::