MagicMirror behind a NGinx Reverse Proxy

fbr1969 · Dec 23, 2019, 6:16 PM

@sdetweil @ember1205 Thank for your help.
I made a mistake ! My error is 404 (Cannot GET /mmirror)

I forgot to say :

My nginx server is fully fonctional with some other locations I’ve masqued in my exemple of configuration files… Like that :

    # Proxy to the Airsonic server
    location /airsonic {
        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_set_header X-Forwarded-Host  $http_host;
        proxy_set_header Host              $http_host;
        proxy_max_temp_file_size           0;
        proxy_pass                         http://192.168.10.30:8080/airsonic;
        proxy_redirect                     http:// https://;
    }

    location /calilivre {
        proxy_bind              $server_addr;
        proxy_pass              http://192.168.10.20:8080;
        proxy_set_header        Host            $http_host;
        proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header        X-Forwarded-Host $server_name;
        proxy_set_header        X-Scheme        $scheme;
        proxy_set_header        X-Script-Name   /calilivre;  # IMPORTANT: path has NO trailing slash
    }

    location /calibd {
        proxy_bind              $server_addr;
        proxy_pass              http://192.168.10.50:8080;
        proxy_set_header        Host            $http_host;
        proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header        X-Scheme        $scheme;
        proxy_set_header        X-Script-Name   /calibd;  # IMPORTANT: path has NO trailing slash
    }

    location /mmirror {
        proxy_bind              $server_addr;
        proxy_pass              http://192.168.10.60:8080;
        proxy_set_header        Host            $http_host;
        proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header        X-Scheme        $scheme;
        proxy_set_header        X-Script-Name   /;  # IMPORTANT: path has NO trailing slash
    }

So, airsonic, calibd or calilivre are fully fonctional in http (redirect to https) or https.
My 'domainename (ex:domain.com) is resolved by dns.
I can do my test on my private lan or on Internet. I’ve the same result (502 Bad Gateway).
Look the curl result :

curl -iL http://192.168.10.10/mmirror
HTTP/1.1 301 Moved Permanently
Server: nginx/1.14.2
Date: Mon, 23 Dec 2019 18:14:36 GMT
Content-Type: text/html
Content-Length: 185
Connection: keep-alive
Location: https://[MyDomain]/mmirror

HTTP/1.1 404 Not Found
Server: nginx/1.14.2
Date: Mon, 23 Dec 2019 18:14:36 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 146
Connection: keep-alive
X-DNS-Prefetch-Control: off
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=15552000; includeSubDomains
X-Download-Options: noopen
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Security-Policy: default-src 'self'

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot GET /mmirror</pre>
</body>
</html>

I think I have some problems with some "proxy_set_header " rules.

Best regards

fbr1969 · Dec 23, 2019, 6:07 PM

@fbr1969
And yes, Magicmirror is fonctional in direct connection with : http://192.168.10.60:8080

ember1205 · Dec 23, 2019, 6:16 PM

@fbr1969 said in MagicMirror behind a NGinx Reverse Proxy:

@sdetweil @ember1205 Thank for your help.

I forgot to say :

My nginx server is fully fonctional with some other locations I’ve masqued in my exemple of configuration files… Like that :

location /mmirror {
    proxy_bind              $server_addr;
    proxy_pass              http://192.168.10.60:8080;
    proxy_set_header        Host            $http_host;
    proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header        X-Scheme        $scheme;
    proxy_set_header        X-Script-Name   /;  # IMPORTANT: path has NO trailing slash
}

I think I have some problems with some "proxy_set_header " rules.

It appears that your X-Script-Name IS setting a trailing slash and isn’t inserting / removing mmirror. Shouldn’t that last line be

     proxy_set_header        X-Script-Name   /mmirror;  # IMPORTANT: path has NO trailing slash

??

sdetweil · Dec 23, 2019, 7:46 PM

@ember1205 its pretty clear tho

curl -iL http://192.168.10.10/mmirror
HTTP/1.1 301 Moved Permanently
Server: nginx/1.14.2
Date: Mon, 23 Dec 2019 18:14:36 GMT
Content-Type: text/html
Content-Length: 185
Connection: keep-alive
Location: https://[MyDomain]/mmirror

HTTP/1.1 404 Not Found
Server: nginx/1.14.2
Date: Mon, 23 Dec 2019 18:14:36 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 146
Connection: keep-alive
X-DNS-Prefetch-Control: off
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=15552000; includeSubDomains
X-Download-Options: noopen
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Security-Policy: default-src 'self'

Error
<pre>Cannot GET /mmirror</pre>

Cannot GET /mmirror

because that is on the client issuing the curl command, url with no ip address is same as localhost

what is this??
Location: https://[MyDomain]/mmirror

again this should be server.mydomain

if u go to client and do an nslookup domain.com
u will get an error
ping domain.com will fail

ember1205 · Dec 23, 2019, 8:42 PM

@sdetweil said in MagicMirror behind a NGinx Reverse Proxy:

@ember1205 its pretty clear tho

curl -iL http://192.168.10.10/mmirror
HTTP/1.1 301 Moved Permanently
Server: nginx/1.14.2
Date: Mon, 23 Dec 2019 18:14:36 GMT
Content-Type: text/html
Content-Length: 185
Connection: keep-alive
Location: https://[MyDomain]/mmirror

HTTP/1.1 404 Not Found
Server: nginx/1.14.2
Date: Mon, 23 Dec 2019 18:14:36 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 146
Connection: keep-alive
X-DNS-Prefetch-Control: off
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=15552000; includeSubDomains
X-Download-Options: noopen
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Security-Policy: default-src 'self'

Error
<pre>Cannot GET /mmirror</pre>

Cannot GET /mmirror

because that is on the client issuing the curl command, url with no ip address is same as localhost

what is this??
Location: https://[MyDomain]/mmirror

again this should be server.mydomain

if u go to client and do an nslookup domain.com
u will get an error
ping domain.com will fail

He stated that he is masking details of what he’s posting, so it’s definitely something to check.

However…

The error is delivered from nginx

Server: nginx/1.14.2

Which means that it isn’t attempting to retrieve the URL from localhost.

The missing directive that I mentioned prior is where I believe the issue is… The client IS connecting and requesting /mmirror, but that is not defined on the nginx host. As a result, it’s being processed by the default host configured there which will be on a different back-end server and that server does not have a /mmirror path available to serve. So, 404.

sdetweil · Dec 23, 2019, 8:46 PM

@ember1205 said in MagicMirror behind a NGinx Reverse Proxy:

but that is not defined on the nginx host.

but it is as a server entry in the nginx.conf

I have just set one up and see the same…

but the proxy doesn’t explicitly ask to pass the uri too

sdetweil · Dec 23, 2019, 8:52 PM

@ember1205 so, if u take off the mmirror part of the 1st server and use the / location to proxy pass it works, so you are correct… it passed the uri portion along too…

ember1205 · Dec 23, 2019, 8:57 PM

When using a proxy server like this, it functions mostly like a content switch. In other words, you can redirect specific paths to different back-end hosts - this is commonly done when you have different servers holding different kinds of content.

When you have a VIP acting as a Content Switch, anything not explicitly defined for a particular path will be handled by the default VIP. In this case, he has not actually defined the /mmirror path, so appending that to his domain will result in the DEFAULT server getting the traffic as opposed to the mirror. That’s why the 404.

I believe that the directive I mentioned earlier is all that needs to be defined in order to get the nginx proxy handling that path accordingly…

fbr1969 · Dec 24, 2019, 3:14 PM

Re: MagicMirror behind a NGinx Reverse Proxy

I watched my Nginx error file and found :

2019/12/24 10:20:45 [error] 2341#2341: *1 open() "/var/www/html/socket.io/socket.io.js" failed (2: No such file or directory), client: XX.XXX.XX.XXX, server: mydomain.com, request: "GET /socket.io/socket.io.js HTTP/1.1", host: "mydomain.com", referrer: "https://mydomain.com/mmirror/"```

So, I tried to modify my nginx config file.
Here’s the final configuration, working fine (don’t forget to change ‘mydomain.com’), and your private IP adress.
Magic Mirror will be avaiable by : https://mydomain.com/mmirror :

server {
    listen      80;
    server_name mydomain.com;
    return      301 https://$server_name$request_uri;
}

server {

    # Setup HTTPS certificates
    listen       443 default ssl;
    server_name  mydomain.com;
    ssl_certificate /etc/letsencrypt/live/mydomain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/mydomain.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    # Access to Magic Mirror
    location /mmirror/ {
        proxy_pass              http://192.168.10.60:8080/;
        #proxy_redirect          http://192.168.10.60:8080 /mmirror;
        #proxy_set_header Host $http_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 $scheme;
        proxy_pass_request_headers on;
        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 $scheme;
        proxy_set_header X-Forwarded-Host $http_host;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $http_connection;
        # Disable buffering when the nginx proxy gets very resource heavy upon streaming
        proxy_buffering off;
    }

        location /socket.io {
                # Proxy Magi Mirror Websockets traffic
                proxy_pass http://192.168.10.60:8080;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
                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 $scheme;
                proxy_set_header X-Forwarded-Protocol $scheme;
                proxy_set_header X-Forwarded-Host $http_host;
        }

    location / {
        root   /var/www/html;
        index  index.html ;
    }
}

ember1205 · Dec 24, 2019, 3:14 PM

@fbr1969

A couple of questions about your configuration…

It seems that you configured ONLY for access to the mirror with a /mmirror path as well - is this accurate? I can’t tell where the ‘default’ VIP might be pointing to.
It appears that you have to handle the /socket.io path independently of the of /mmirror path, and that leads me to wonder if there is javascript code being returned to the browser that ALSO needs to be rewritten inline?