Samsung Smart TV can't play anything via remote access (http)

[parhamsan 17]

Hello,

I have a client who is having the same issue on his Samsung TV,

Below are the initial errors he got on his TV:

I am also doing Reverse Proxy on IIS and using emby.mydomain.com as the domain name ports 80 and 433. Also switched from Lets Encrypt to Zero SSL with no luck.

All the other clients have no issues on their Samusng TV. Also tried on Emby 1.7.0 (From store) and 1.8.7 From USB installation with same issue.

Can someone advise on what could be wrong.

Thanks.

embyserver.txt

[Luke 42077]

@parhamsanHi, for starters, what is being played?

[parhamsan 17]

He tried anything and nothing is getting played, it starts and then stops after like 5 sec, things he played:

The Boys - We'll Keep the Red Flag Flying Here on Samsung Smart TV

The.Boys.S04E03.Well.Keep.the.Red.Flag.Flying.Here.1080p.AMZN.WEB-DL.DD5.1.x265-FLUX.mkv

 

True Detective - Kiss Tomorrow Goodbye on Samsung Smart TV

True.Detective.S03E02.1080p.BluRay.x265-PEZ.mkv

 

I know this is related to SSL but how can I let him to connect to http since I am on reverse proxy; and on reverse proxy I am forcing to https?

I have forwarded the ports but cant access http using emby.mydomain.com:8096 or mydomain.com:8096.

Thanks.

 

[parhamsan 17]

If you need more information on the file codecs let me know, but as mentioned he wouldn't be able to play any file format (mkv, mp3, avi) with any audio codec (AAC, DTS, AC3, etc..), thanks! 

[Luke 42077]

Have you compared your reverse proxy settings to this:

 

[parhamsan 17]

I am using IIS Reverse Proxy from this guide:

 

[Luke 42077]

Oh, how did I miss this:

[parhamsan 17]

6 minutes ago, Luke said:

Oh, how did I miss this:

Luke,

I have another free domain name pointing to my WAN IP (from No-IP), which I use for http and I opened a port for unsecured connection and I have not changed anything on the Media PLayback section for him (not letting any user transcode video). As soon as he added the server with port 8096 and the other domain, now he can play everything. The odd thing is I am using ZeroSSL on the Certify the Web app for my certificates. I though only Some Samsung and LG tvs have issues with Lets Encrypt and not ZeroSSL???

What is you suggestion for this issue, as I don't want any unsecured connections!

Thanks.

[Luke 42077]

Hi, that's odd. Did you figure this out? @SamEShas researched SSL on these devices and may have some insight. Thanks.

[parhamsan 17]

Luke,

I have forced the user to buy a Firestick TV 4k  , also I have moved my subdomain to get managed by Nginx Proxy Manager on a rpi5 and used @pir8radio settings on the NPM. The user is currently out of city so when he comes back I will ask him to try again on his Samsung Tv and let me know of the result.

It is very odd since he is the only one having the playback dilemma. I have like 4 to 5 other users with older Model Samsung TVs that have no issues on the playback.

Thanks for following up on this, will keep you updated in the matter!

[SamES 1057]

On 02/08/2024 at 13:29, parhamsan said:

Luke,

I have another free domain name pointing to my WAN IP (from No-IP), which I use for http and I opened a port for unsecured connection and I have not changed anything on the Media PLayback section for him (not letting any user transcode video). As soon as he added the server with port 8096 and the other domain, now he can play everything. The odd thing is I am using ZeroSSL on the Certify the Web app for my certificates. I though only Some Samsung and LG tvs have issues with Lets Encrypt and not ZeroSSL???

What is you suggestion for this issue, as I don't want any unsecured connections!

Thanks.

My guess is that there is still something not quite right with the reverse proxy setup; or, there is something about the Samsung player which doesn't work correctly with the way your reverse proxy is setup. 

[parhamsan 17]

21 hours ago, SamES said:

My guess is that there is still something not quite right with the reverse proxy setup; or, there is something about the Samsung player which doesn't work correctly with the way your reverse proxy is setup. 

@SamES, below are my New Reverse Proxy settings that I used from this link for a while now:

 

"Custom Locations"

    location / {
        proxy_pass http://SERVER-IP:8096;  ## Enter the IP and port of the backend emby server here.
        client_max_body_size 1000M;  ## Allows for mobile device large photo uploads.

        proxy_hide_header X-Powered-By;     ## Hides nginx server version from bad guys.
        proxy_set_header Range $http_range;  ## Allows specific chunks of a file to be requested.
        proxy_set_header If-Range $http_if_range;  ## Allows specific chunks of a file to be requested.
        #proxy_set_header X-Real-IP $remote_addr;  ## Passes the real client IP to the backend server.
        proxy_set_header X-Real-IP $http_CF_Connecting_IP;  ## if you use cloudflare un-comment this line and comment out above line.
        proxy_set_header Host $host;  ## Passes the requested domain name to the backend server.
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;  ## Adds forwarded IP to the list of IPs that were forwarded to the backend server.

    ## ADDITIONAL SECURITY SETTINGS ##
    ## Optional settings to improve security ##
    ## add these after you have completed your testing and ssl setup ##
    ## NOTICE: For the Strict-Transport-Security setting below, I would recommend ramping up to this value ##
    ##         See https://hstspreload.org/ read through the "Deployment Recommendations" section first!   ##
        add_header 'Referrer-Policy' 'origin-when-cross-origin';
        add_header Strict-Transport-Security "max-age=15552000; preload" always;
        add_header X-Frame-Options "SAMEORIGIN" always;
        add_header X-Content-Type-Options "nosniff" always;
        add_header X-XSS-Protection "1; mode=block" always;

     ## WEBSOCKET SETTINGS ## Used to pass two way real time info to and from emby and the client.
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $http_connection;
        }

 

"Advanced Tab"

    include       mime.types;
    default_type  application/octet-stream;
    server_tokens off;
    sendfile        off;  ##sendfile not used in a proxy env
    proxy_buffering off;

    gzip on;   ## Compresses the content to the client, speeds up client browsing.
    gzip_disable "msie6";

    gzip_comp_level 6;
    gzip_min_length 1100;
    gzip_buffers 16 8k;
    gzip_proxied any;
    gzip_types
        text/plain
        text/css
        text/js
        text/xml
        text/javascript
        application/javascript
        application/x-javascript
        application/json
        application/xml
        application/rss+xml
        image/svg+xml;

    proxy_connect_timeout 1h;
    proxy_send_timeout 1h;
    proxy_read_timeout 1h;
    tcp_nodelay on;  ## Sends data as fast as it can not buffering large chunks

----------------------------------------------------------------------------------------------------------------------------------

Again I have not tested the TV with the new Proxy Settings so have to wait for my client to come back and see if his Samsung TV plays with the current settings!!!

[SamES 1057]

1 hour ago, parhamsan said:

Again I have not tested the TV with the new Proxy Settings so have to wait for my client to come back and see if his Samsung TV plays with the current settings!!!

Let's wait until we get these results.

[Moreje 16]

I have the same issue with my Samsung daughter's TV!

She can't play remotely from my server, browsing the library is OK, but stream does not launch

(yesterday, although, for unknown reason, she could play 2 episodes, and then the issue came back

when using her laptop from the same connection, no issue

so it is TV related....

today's Tests say: no compatible stream....

I'm behind reverse proxy (nginx docker), with LE certificate

all other remote clients play OK

can't find what to do...

Edited September 12, 2024 by Moreje

[SamES 1057]

What model Samsung TV?  Older models had issues with LE certificates

[Moreje 16]

It is a recent model TQ65Q60C

 

[Moreje 16]

I see there is a recent update for TV available (manually ,not by network), i'll ask her to do it, maybe it could correct root certs....

[SamES 1057]

15 minutes ago, Moreje said:

I see there is a recent update for TV available (manually ,not by network), i'll ask her to do it, maybe it could correct root certs....

Worth a try.  2023 models should be fine for LE.

Are you connecting using Emby Connect, or did you manually put the server name/ip and port in the server entry screen? 

[Moreje 16]

it is a manual setting. should We try Embyconnect?

 

[SamES 1057]

2 hours ago, Moreje said:

it is a manual setting. should We try Embyconnect?

 

Manual is fine, but did you put https:// in front of the server name/ip and also use the correct port number for https?

[Moreje 16]

maybe it is related to this:?

- my user should have put https:// and the correct port. i'll check with her

- related to my nginx conf? : it is configured to redirect my duckdns domain to my emby server following http scheme. do I need to use https?

- if yes, emby should have its own certificate? or can I use the same that used in nginx ?

I can't find what's wrong....

for every other clients android, PC, windows.... there is no problem at all

[SamES 1057]

BTW, I don't think the clients support using a path like https://server.name/emby. (ie : with a path on the end). Not sure if that is what you are also trying to do

I remember that this has come up before as an issue, but can't remember the outcome, or if it now works as expected.

I'm assuming you've also been through this

and check this