Problems with SSL and Emby Connect

[dambrosioj 0]

So I got my reverse proxy working fine with emby whenever I manually type in the server for emby connect and everything works fine.

 

But when I send an invite to people the server shows up automatically and when they click on it, it says unable to connect.  Is this not possible with emby connect and ssl/lets encrypt?

 

 

Also here is my nginx config.

server {

        listen 443 ssl;

        server_name xxxxx.dns.org www.xxxxx.dns.org;

        ssl_certificate /etc/letsencrypt/live/xxxxxx.dns.org/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/xxxxx.dns.org/privkey.pem;

        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_prefer_server_ciphers on;
        ssl_dhparam /etc/ssl/certs/dhparam.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_session_timeout 1d;
        ssl_session_cache shared:SSL:50m;
        ssl_stapling on;
        ssl_stapling_verify on;
        add_header Strict-Transport-Security max-age=15768000;

        location ~ /.well-known {
                allow all;
        }

        # The rest of your server block
       # root /usr/share/nginx/html;
       # index index.html index.htm;

       # location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files $uri $uri/ =404;
                # Uncomment to enable naxsi on this location
                # include /etc/nginx/naxsi.rules
       # }
	location /emby {
		# Send traffic to the backend
                proxy_pass https://192.168.1.38:8920;
                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";
        }
	location /grafana/ {

        proxy_pass http://192.168.1.33:3000/;

    }
}

Edited January 3, 2017 by dambrosioj

[Luke 42085]

You're using https from nginx, not Emby, so you need to keep the Emby configuration at default.

[dambrosioj 0]

You're using https from nginx, not Emby, so you need to keep the Emby configuration at default.

 

Luke,  I set everything back to the default in Emby and no luck.  My users can go to app.emby and login and see my server show up but as soon as you click on it.  I get a connection failure message.  Will this not work with nginx? 

 

Also I do not have 8096/8920 open in my firewall since I am using nginx so maybe thats the issue?

 

I was hoping there was somewhere in emby we can tell emby connect to use our own domain names such as xxxx.dns.org and it will use that for emby connect.  Maybe a new feature?

Edited January 4, 2017 by dambrosioj

[ebr 16195]

I was hoping there was somewhere in emby we can tell emby connect to use our own domain names such as xxxx.dns.org and it will use that for emby connect.  Maybe a new feature?

 

Server Dashboard -> Advanced -> Hosting -> External Domain

[dambrosioj 0]

Server Dashboard -> Advanced -> Hosting -> External Domain

 

Well I did have that in there before as you can see from my attached screenshot in the OP and Luke told me not to use that and remove everything.  Either way it didnt work when it was in there .

[Luke 42085]

@@dambrosioj, you should customize the remote address but leave the ssl settings at default, since nginx is handling it.

 

Before you even worry about Emby connect, the first thing to try is connecting to your own web app remotely. have you tested that?