November 26, 20169 yr sorry if this is a silly question, but my installation always says I am xx commits behind - how do I update? (same problem with Lazy Librarian where I'm 154 behind!) Thanks Our containers are updated weekly. Just checking LazyLibrarian and mine is up to date.
November 26, 20169 yr sorry if this is a silly question, but my installation always says I am xx commits behind - how do I update? (same problem with Lazy Librarian where I'm 154 behind!) Thanks Our containers are updated weekly. Just checking LazyLibrarian and mine is up to date. Mine still is 154 behind (updated my dockers yesterday when the new ones came down) - do I need to do something other just update my dockers to stay up to date?
November 26, 20169 yr Is there a tutorial for setting this up with cp sonarr etc via a reverse proxy?
November 27, 20169 yr Is there a tutorial for setting this up with cp sonarr etc via a reverse proxy? No...
December 7, 20169 yr just heard about this docker app today and man i didn't know what i was missing till i installed this thing. makes managing app my containers so much easier having a one stop shop pretty much. kudos to everybody involved in making this
January 7, 20179 yr I configured this docker behind let's encrypt and secured with httpauth and its working great! Only issue is I am trying to configure the darn thing and everything I hit save and reload, the site doesn't do anything. Anyone else running into this?
January 7, 20179 yr I configured this docker behind let's encrypt and secured with httpauth and its working great! Only issue is I am trying to configure the darn thing and everything I hit save and reload, the site doesn't do anything. Anyone else running into this? What do you mean by site? It's not saving your config? Accessing via LAN or via the LE reverse proxy?
January 7, 20179 yr Correct. Everytime I make a setting change on the WebUI of Muximux (ex. Change the Title of the page) and I click Save + Reload, nothing changes or appears. I wait a bit, nothing - a page reload brings back all the default settings. My current setup is LE reverse proxy, port 3030. I have muximux set up on my root folder with authentication: server { listen 443 ssl 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 blahblah ssl_prefer_server_ciphers on; client_max_body_size 0; location / { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.1.51:8080; #try_files $uri $uri/ /index.html /index.php?$args =404; } location /muximux { rewrite ^/muximux(/.*)$ $1 break; proxy_pass http://192.168.1.51:8080; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto https; proxy_redirect off; } I've tried messing with the NGINX settings but the site is loading just fine under the reverse proxy URL. I've also deleted my app data, removed container and image, and rebuilt from scratch with no luck.
January 7, 20179 yr Correct. Everytime I make a setting change on the WebUI of Muximux (ex. Change the Title of the page) and I click Save + Reload, nothing changes or appears. I wait a bit, nothing - a page reload brings back all the default settings. My current setup is LE reverse proxy, port 3030. I have muximux set up on my root folder with authentication: server { listen 443 ssl 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 blahblah ssl_prefer_server_ciphers on; client_max_body_size 0; location / { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.1.51:8080; #try_files $uri $uri/ /index.html /index.php?$args =404; } location /muximux { rewrite ^/muximux(/.*)$ $1 break; proxy_pass http://192.168.1.51:8080; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto https; proxy_redirect off; } I've tried messing with the NGINX settings but the site is loading just fine under the reverse proxy URL. I've also deleted my app data, removed container and image, and rebuilt from scratch with no luck. OK, forget the reverse proxy and don't alter the Nginx settings, go back to a basic config and access it via IP:PORT not via the reverse proxy, can you edit the settings then? I don't use this but just pulled it and had no issues whatsoever. Try new appdata, new container and image. If it doesn't work then post your docker run command and logs.
January 8, 20179 yr Thanks for the help CHBMB! I am able to edit on the local IP! Strangely though, once I edited all the Muximux web urls for plexpy, sonarr, etc. I did a save and reload, it now doesn't allow me to make new changes. Must be due to HTTPS - I have everything the way I want now so it's fine now (once I have to make new changes I'll have to do some digging to get it working again though).
January 24, 20179 yr I've got everything set up and Muximux is working perfectly locally using my server IP. But, I want to be able to access Muximux externally from the web. So I've just setup a reverse proxy with the ls.io letsencrypt docker. I can setup so I can access for example https://couchpotato.domain.com without a problem. But how the heck do I setup Muximux to work with the reverse proxy? It works if I "Load unsafe scripts" but then I'm no longer using SSL. I've tried setting the adress in Muximux to https://couchpotato.domain.com but it won't load that page safely either. Anyone able to point me in the right direction?
January 25, 20179 yr Here is how I have it set up in LS.IO letsencrypt. Muximux is htpc.example.com and everything else is set up as htpc.example.com/XYZ In muximux I point to each htpc.example.com/XYZ address and not the internal one. #HTPC server { listen 443 ssl; root /config/www; index index.html index.htm index.php; server_name htpc.*; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers *REDACTED*; ssl_prefer_server_ciphers on; client_max_body_size 0; location / { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.*.*:1234; } location ^~ /tv { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.*.*:5678/tv; } location ^~ /movies { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.*.*:****/movies; } location ^~ /stats { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.*.*:****/stats; } location /deluge { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.*.*:****/; proxy_set_header X-Deluge-Base "/deluge/"; } location /transmission/ { proxy_pass_header X-Transmission-Session-Id; 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://192.168.*.*:****/transmission/web/; } location /rpc { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.*.*:****/transmission/rpc; } } Hope it helps.
January 25, 20179 yr Great, thanks! It helped a lot. Once I figured out that you set URL base in the settings of each application, everything (except Plexpy) works. My setup is: server { listen 443 ssl default_server; root /config/www; index index.html index.htm index.php; server_name servername.*; ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ssl_dhparam /config/nginx/dhparams.pem; ssl_ciphers 'XXXX'; ssl_prefer_server_ciphers on; client_max_body_size 0; location / { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.X.X:81; } location ^~ /nzbget { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.X.X:6789/nzbget; } location ^~ /sonarr { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.X.X:8989/sonarr; } location ^~ /cp { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.X.X:5050/cp; } location ^~ /plexpy { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.X.X:8181/plexpy; } location ^~ /web { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass http://192.168.X.X:32400; } I can't get Plexpy to work, though, even though I've followed the instructions for the proxying headers here: https://github.com/JonnyWong16/plexpy/wiki/Frequently-Asked-Questions-%28FAQ%29#q-why-does-plexpy-not-work-with-my-reverse-proxy-setup I don't relly need Plexpy to work right now, but it would be good so the setup is complete..
January 25, 20179 yr My /stats is your /plexpy The issue isn't in nginx. Check your plexpy settings. I have /stats in the HTTP Root of PlexPy Web Interface settings
January 25, 20179 yr Thanks for your help! Can't get it to work, even though I've set the HTTP Root in Plexpy to /plexpy. I get it to work when I go to server.domain.com/plexpy, but in Muximux when I go to the Plexpy tab I get an Unsecure scripts-warning. But it's not the end of the world, just slightly annoying.
January 25, 20179 yr Nevermind. Got it to work. Changed the address in Muximux from server.domain.com/plexpy to server.domain.com/plexpy/home and it works. Thanks again!
February 4, 20179 yr I noticed that UnRaid 6.3 doesn't want to display in Muximux anymore. Probably, it needs it cross site scripting loosened up a bit. Does anyone have a fix for it?
February 4, 20179 yr Replying to myself. To get Unraid 6.3 showing in Muximux on Chrome - add the Ignore X-Frame headers extension. However, would be nice to see a setting inside of Unraid that let us dial down the cross site security. https://chrome.google.com/webstore/detail/ignore-x-frame-headers/gleekbfjekiniecknbkamfmkohkpodhe
February 4, 20179 yr However, would be nice to see a setting inside of Unraid that let us dial down the cross site security. Won't happen
February 4, 20179 yr I don't know much about emhttp and how Unraid serves up its web pages - but maybe a plugin could modify the configuration to remove the X-Frames headers? Just a thought.
February 4, 20179 yr I don't know much about emhttp and how Unraid serves up its web pages - but maybe a plugin could modify the configuration to remove the X-Frames headers? Just a thought. I'm no expert on HTML headers, etc but should a plugin ever purposely open up a security hole within unRaid (ie: disable the csrf_tokens as an example), then the plugin would get blacklisted very promptly
February 4, 20179 yr I'm no expert on HTML headers, etc but should a plugin ever purposely open up a security hole within unRaid (ie: disable the csrf_tokens as an example), then the plugin would get blacklisted very promptly Good point. :-)
February 5, 20179 yr I can't see how it's possible to change the base url, but this is a workaround RewriteRule ^/muxi$ /muxi/ [R] <Location /muxi> ProxyPass http://UNRAID-IP:MUXIMUX-PORT/ ProxyPassReverse http://UNRAID-IP:MUXIMUX-PORT/ </Location> For reference here's the other bits of my setup.... RewriteEngine On ProxyPreserveHost Off Hey, does anyone know of an nginx equivalent to this?
February 9, 20179 yr Don't know if anyone else is experiencing this, but with the latest version of Chrome (Version 56.0.2924.87 (64-bit)) and the Ignore X-Frame headers extension active, MuxiMux slows to a crawl after a few minutes idle to the point where any frame or window you're loading through MuxiMux becomes unusable. Used to be fine on Chrome 55 and below. Loading those container web views and UI (like unRAID webGUI) outside of MuxiMux is fine. It's only when using MuxiMux where things crap out. Barring any fixes to MuxiMux, are there any viable alternative containers or plugins available that don't have this issue (or the security hole caused by using Ignore X-Frame)? Do HTPC Manager or Marschino work similarly without the performance or framing/security issues?
February 12, 20179 yr Deployed this today....and all I can get is a white screen that states loading with some blank boxes... I checked the logs container for muximux and they are blank. The logs from the unraid docker when it launchs are less than helpfull as well... [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... usermod: no changes ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 40-install: executing... [cont-init.d] 40-install: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done.
Archived
This topic is now archived and is closed to further replies.