dyn.com > nginx > emby, problems with proxy config (I think)

[iburnthings 0]

my primary domain is a wordpress site, I also have a vhost for owncloud. My goal will be to use emby to host up publicly shared videos from owncloud into emby (if that is even possible idk yet)

This is hosted in CA from a windows machine with an ubuntu hyperv guest. Since it isn't a static ip I also have a Dyn.com DNS Pro for my domain name.

 

In Dyn.com I have an A record for my domain, this ip address updates whenever my ip changes thanks to a program on the windows host. (I have a script on the linux guest for some redundancy even though it's the same hardware, I know.)

 

I also have a CNAME for owncloud, webmail, and now for emby.  They all point back to the domain name.

 

On the linux guest I have nginx running.  It is responsible for sifting the traffic to the appropriate folders in /var/www/ and it's working for my worpdress site and owncloud.

 

Now I'm trying to get emby going.. since emby has it's own networking stuff going on it seems to be either hijacking my domain name completely OR getting too many redirects.

 

I know I'm doing something wron in the nginx vhost file because I don't know what I should be putting in the emby backend to make this all work

for example I think maybe proxy_pass http://domain.com:8096;should be proxy_pass http://127.0.0.1:8096; or something

server {
        server_name emby.domain.com;
        listen 80;

        rewrite ^ http://emby.domain.com permanent;
}

server {
        server_name emby.domain.com;
        #listen 443 ssl spdy;
	listen 80;
        #ssl_certificate                 ;
        #ssl_certificate_key             ;
        #ssl_prefer_server_ciphers       On;
        #ssl_protocols                   TLSv1 TLSv1.1 TLSv1.2;
        #ssl_ciphers                     'AES256+EECDH:AES256+EDH:!aNULL';
        #ssl_stapling                    on;
        resolver                        8.8.8.8 8.8.4.4 valid=300s;
        resolver_timeout                5s;
        #ssl_stapling_verify             on;
        #ssl_trusted_certificate         /etc/ssl/ca-certs.pem;
        keepalive_timeout               180;

        # This is for strict transport security HSTS
        # add_header                    Strict-Transport-Security max-age=31536000;

        client_max_body_size 1024M;

        location / {
                # Send traffic to the backend
                proxy_pass http://domain.com:8096;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-for $proxy_add_x_forwarded_for;
                proxy_set_header Host $host;
                proxy_set_header X-Forwarded-Proto $remote_addr;
                proxy_set_header X-Forwarded-Protocol $scheme;
                proxy_redirect off;

                # Send websocket data to the backend aswell
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
        }
}

[iburnthings 0]

This all appears to be working from my dads house in CA.. it's NOT working from my house in NM or my sprint or verizon cell phones.

 

It must be a DNS propagation issue or a caching problem here in NM.. I don't know why it would effect spring VZW and comcast though.

 

/sigh

 

i'm glad I'm not a bigshot network admin lol

[iburnthings 0]

It only works as desired inside my dads network. Outside requests all go to Emby.

[iburnthings 0]

seems this was some caching problem with my dads stupid router grr.

[Luke 42077]

Well done