Jump to content

We're unable to connect to the selected server right now.


Recommended Posts

WingDog
Posted

I got the same problem with Samsung TV yesterday. App opens and nothing more than library titles (cached on the client as I suppose).

unable to playback, to reconnect to the server and so on.

log attached

embyserver-63905673600.txt

Posted

@WingDog what exactly happens? Can you capture A video?

visproduction
Posted

Of interest .txt log lines 1083+

K-PAX (2001) media content is perhaps a very large file, or some other codec issue causing encoding to time out after 5 seconds.

"Response completed after client disconnected"  occurs 124 times in this log.

Try playback of test demo media 1080P and 4K .mkv file, to see if the problem is with the K-PAX media copy

Quote

2026-02-02 18:22:45.036 Info DynamicHlsService-0HNIQOCK4NDCF:00000003: http/1.1 GET http://192.168.1.59:8096/emby/videos/70887/hls1/main/0.ts?PlaySessionId=6d5201f2a97c4353aaba482830299660. Source Ip: host7, Accept=*/*, Connection=Upgrade, Host=192.168.1.59:8096, User-Agent=samsung-agent/1.1, Accept-Encoding=deflate, gzip, Upgrade=h2c, HTTP2-Settings=AAMAAABkAARAAAAAAAIAAAAA


2026-02-02 18:22:45.037 Info DynamicHlsService-0HNIQOCK4NDCF:00000003: Starting transcoding because currentTranscodingIndex=null


2026-02-02 18:22:45.054 Info DynamicHlsService-0HNIQOCK4NDCF:00000003: ProcessRun 'StreamTranscode 2e3be2' Execute: C:\Users\Administrator\AppData\Roaming\Emby-Server\system\ffmpeg.exe -loglevel +timing -y -print_graphs_file "C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\logs\ffmpeg-directstream-2e3be210-9100-45db-98a9-d8135081a73c_1graph.txt" -copyts -start_at_zero -f matroska,webm -c:v:0 h264 -noautorotate -i "\\nas2\Films\FILMS\K-PAX (2001).mkv" -map 0:0 -map 0:1 -sn -c:v:0 copy -bsf:v:0 h264_mp4toannexb -c:a:0 copy -disposition:a:0 default -max_delay 5000000 -avoid_negative_ts disabled -f segment -map_metadata -1 -map_chapters -1 -segment_format mpegts -segment_list "C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\transcoding-temp\C2D82E\C2D82E.m3u8" -segment_list_type m3u8 -segment_time 00:00:06.000 -segment_start_number 0 -individual_header_trailer 0 -write_header_trailer 0 -segment_write_temp 1 "C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\transcoding-temp\C2D82E\C2D82E_%d.ts"


2026-02-02 18:22:51.446 Info VideoService-0HNIQOCK4NDCB:00000001: http/1.1 Response completed after client disconnected to host7. Time: 37706ms. GET http://192.168.1.59:8096/emby/videos/70887/original.mkv?DeviceId=f2c2b11c-d560-4ffb-8dfc-09a2c3a04c51&MediaSourceId=mediasource_70887&PlaySessionId=4c215372ed5c456e80a6446512c65d63&api_key=x_secret6_x. Headers: Content-Type=video/x-matroska, Server=UPnP/1.0 DLNADOC/1.50, Accept-Ranges=bytes, Cache-Control=private, no-transform, Content-Range=bytes 0-7135314441/7135314442, ETag="9492065ac5e6bc39f9371de120ead6e2", Content-Length=7135314442, Cross-Origin-Resource-Policy=cross-origin, Private-Network-Access-Name=WD's Home Server, Private-Network-Access-Id=61a379f5983a4cca957f6de036dae7e8


2026-02-02 18:22:51.447 Info VideoService-0HNIQOCK4NDCC:00000001: http/1.1 Response completed after client disconnected to host7. Time: 27693ms. GET http://192.168.1.59:8096/emby/videos/70887/original.mkv?DeviceId=f2c2b11c-d560-4ffb-8dfc-09a2c3a04c51&MediaSourceId=mediasource_70887&PlaySessionId=4c215372ed5c456e80a6446512c65d63&api_key=x_secret6_x. Headers: Content-Type=video/x-matroska, Server=UPnP/1.0 DLNADOC/1.50, Accept-Ranges=bytes, Cache-Control=private, no-transform, Content-Range=bytes 0-7135314441/7135314442, ETag="9492065ac5e6bc39f9371de120ead6e2", Content-Length=7135314442, Cross-Origin-Resource-Policy=cross-origin, Private-Network-Access-Name=WD's Home Server, Private-Network-Access-Id=61a379f5983a4cca957f6de036dae7e8


2026-02-02 18:22:51.447 Info VideoService-0HNIQOCK4NDCD:00000001: http/1.1 Response completed after client disconnected to host7. Time: 17681ms. GET http://192.168.1.59:8096/emby/videos/70887/original.mkv?DeviceId=f2c2b11c-d560-4ffb-8dfc-09a2c3a04c51&MediaSourceId=mediasource_70887&PlaySessionId=4c215372ed5c456e80a6446512c65d63&api_key=x_secret6_x. Headers: Content-Type=video/x-matroska, Server=UPnP/1.0 DLNADOC/1.50, Accept-Ranges=bytes, Cache-Control=private, no-transform, Content-Range=bytes 0-7135314441/7135314442, ETag="9492065ac5e6bc39f9371de120ead6e2", Content-Length=7135314442, Cross-Origin-Resource-Policy=cross-origin, Private-Network-Access-Name=WD's Home Server, Private-Network-Access-Id=61a379f5983a4cca957f6de036dae7e8

 

WingDog
Posted
On 2/4/2026 at 9:54 PM, Luke said:

What about when clicking on other libraries?

all the same

WingDog
Posted

any updates? ideas?

WingDog
Posted

@Luke

does this version 

 has a autoupdate via Samsung tv store? or this version requier manual update via github? 

FrostByte
Posted (edited)
1 hour ago, WingDog said:

@Luke

does this version 

 has a autoupdate via Samsung tv store? or this version requier manual update via github? 

FYI Your 2021 TV is getting close to, if not already reached the point where Samsung no longer supports it.  After which you will need to stick with the last one you see in the store, or update via usb every month.

Edited by FrostByte
WingDog
Posted
29 minutes ago, FrostByte said:

FYI Your 2021 TV is getting close to, if not already reached the point where Samsung no longer supports it.

have you seen any EOL announcement?

30 minutes ago, FrostByte said:

or update via usb every month.

thanks for the answer even not direct  - I supposed something like this because of very uninformative message box a couple weeks later that forced me to roll-back to the Store version.

FrostByte
Posted
2 minutes ago, WingDog said:

have you seen any EOL announcement?

thanks for the answer even not direct  - I supposed something like this because of very uninformative message box a couple weeks later that forced me to roll-back to the Store version.

It's been Samsung's policy for a while now to no longer test apps for TVs once they reach a certain age.  It used to be 5 years, but recently @Luke has been saying 4 years of app support.  Him, or @SamES can say for sure.  Just wanted to let you know that could be why you don't see an update, or it will be soon.

Posted

We have an update for older models currently in Samsung review.

  • Like 1
FrostByte
Posted
1 hour ago, Luke said:

We have an update for older models currently in Samsung review.

So this is a one-off release for older models.  Thanks

Typically, WingDog's TV won't get the updates now since it's 5 years old, correct?

Posted
1 hour ago, FrostByte said:

So this is a one-off release for older models.  Thanks

Typically, WingDog's TV won't get the updates now since it's 5 years old, correct?

For now at least we have some ability to update older models although the review process is separate and takes much longer.

  • Like 1
WingDog
Posted

thanks for the deepdive about lifecycle policies, but the topic is about Emby (current) doesn't work at my TV (not EOL at this moment).

any updates about this issue?

 

WingDog
Posted (edited)

And anyway, I don't see any connection between the TV and software lifecycle policies—the end of the TV lifecycle only means the end of Tizen OS updates, which, in turn, only simplifies software maintenance, which remains unchanged for this platform. This isn't a particular problem either, because the Emby client is just a client, pardon the tautology, and runs with Client-Server model.
Like everyone else, I have old iPhones and iPads on which the software has been running for well over five years.
Overall, this isn't a topic issue.

Edited by WingDog
Posted
Quote

which, in turn, only simplifies software maintenance, which remains unchanged for this platform.

Hi, not necessarily because when the whole world is constantly being updated around the TV, and the TV still needs to be able to communicate with it, then that's how these kinds of things can happen.

Anyway the Emby app version that you have installed is 2.2.5 which is not very old, however we are trying to get to the bottom of your issue, and since we don't yet know the cause it would be helpful to know the result of what happens with the latest version.

WingDog
Posted
9 hours ago, Luke said:

Can you try installing the latest version via usb?

https://emby.media/emby-for-samsung-smart-tv.html

Something weird happens now.

first I did a USB flash and plugged it to a TV but nothing happens. I remembered that I have previous version installed from that topic (I call it White for the GH version and Black for the TV Store version), but it has been broken for sometime - as far as I understand version from the GH has some time restrictions. so I switched to the Samsung Smart Hub but accidentally launched Black instead of deleting it - and it runs fine, the version was 2.2.5. I deleted White version and replugged the USB flash - at this time new unattended installation launched and installed new White version (2.3.2). at this moment I have White and Black versions both are 2.3.2 and both works fine.

I attached the log if it can assist you ti understand something more.

embyserver.txt

  • Thanks 2
FrostByte
Posted (edited)

Both icons are starting the same app, this happens when you don't delete an old app before switch from usb to store versions, etc.  You can't have both.

Edit: if you check the latest version in the store did that change?

Edited by FrostByte
WingDog
Posted
11 hours ago, FrostByte said:

Both icons are starting the same app,

Yes, I realized that yesterday.

 

11 hours ago, FrostByte said:

if you check the latest version in the store did that change?

no

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...