All Activity

Thanks for sharing.

HI, doesn't support what exactly?

Thanks for sharing.

HI, not yet, sorry.

How did you determine that they're closed?

Apparently my ports are closed. I don't know why that would be? The rules still appear in my router's settings, and I've touched nothing...

#2 to start #1 changes made close and restart goes back to #2 plus have to log in everytime #3

Hello again! Any ways to fix this? Everything was working fine until the end of 2025, and then something broke

I saw in another thread that someone had made a library that's a help section for their users, with instructions on how to do different things in Emby. I thought that was a good idea so here is a home screen graphic for that type of library The icon is from https://www.flaticon.com/free-icon/help_1660114?term=help&page=1&position=6&origin=search&related_id=1660114

Wie Luke schon gesagt hat, Du musst die Versionen in ein Verzeichnis packen. Dann kannst du vor dem Start die Version die Du abspielen willst auswählen. https://emby.media/support/articles/Movie-Naming.html#multi-version-movies Die Auswahl sieht dann in der Web Ansicht so aus.

It's sad when people take what should be a good thing and abuse it. I loved the notifications for direct play vs. transcoding, because it helped me to know when I need to adjust something, or why I may be having an issue. Maybe the emby devs can roll that into the core server.

But is is just as likely to make the experience much worse when a bunch of new shows come in and then all the stuff you are actually watching is buried. There are discussions about this in a couple places out here. Personally, I think new season Premieres should be called out in a separate line.

@soderlundI've added some of the features you requested in the latest update! Pre-filter submissions before media segment scan Add per file/folder selection for scan Add API key test https://github.com/TheIntroDB/emby-plugin/releases/tag/v1.0.3.0

Oui c'est bien le bouton cast de Emby et oui tout est sur mon réseau Wifi. J'ai ouvert les ports dans mon pare feu et la box

There are other tools/plugin out there that do the same thing., Just need to look for them.

There are similar solutions out there just need to look.

3-4 hours is way to long for a refresh. Have you check your connections speed if using external links.

Google says cgnat has a specific ip range and that my wan ip is not part of cgnat...so i may have been given a bum steer by my isp. I have opened a ticket on the alexa forum to discuss the alexa issue specifically.

Segment Reporting 1.5 is out, adding full screen-reader and keyboard accessibility (WCAG 2.1 AA) across every page and chart. As with 1.4.0.1, grab the download that matches your server: segment_reporting_emby_4.9x.zip for Emby 4.9.x or segment_reporting_emby_4.10x.zip for 4.10.x. https://github.com/sydlexius/Segment_Reporting/releases/tag/v1.5.0.0

HI, if you're willing to put them in the same library, then the server has features to merge them together.

Description: My Emby Server running on an Nvidia Shield (Android 11) is experiencing frequent and predictable crashes the past couple of monthes. The crashes happen in a tight loop and always seem to correlate with a client requesting a specific missing image asset. (Apple TV on remote location) After running the logs through an AI analyzer I followed its suggestions and de-installed and re-installed the client app on the Apple TV to exclude this first and in the hope the issue is now resolved. Maybe this is already a known issue, not sure, but I sure would appreciate any advice or further suggestions that could pinpoint the error may it still consist later on. I will be monitoring it further. Note on the attached logcat (crash_log.txt): The logcat contains continuous logging spanning multiple days. While the file starts with timestamps from June 2nd, the actual crashes being analyzed here occurred on June 4th and can be found towards the bottom of the log file. PS. I tried to look up item ID 132993 via the server's web interface and by querying the '/emby/Items?Ids=132993' API endpoint (with my admin API key), but it returns {"Items":[],"TotalRecordCount":0}. This indicates that the item does not exist in the database anymore. It appears to be a stale/ghost ID being requested by a client's cache. Conclusion: The server should gracefully handle a request for a non-existent asset by serving a 404 error back to the client, rather than letting the image-processing / fallback handler trigger a native runtime crash (SIGSEGV). kind regards, Ronald Vrijsen Emby Server Version: 4.10.0.13 (Android Arm64 / .NET 8.0.27) Hardware: Nvidia Shield TV (Darcy) Sequence of Events & Analysis: When monitoring the Emby server logs alongside the Android logcat (attached), a fatal pattern emerges down to the exact millisecond. A client (e.g., Apple TV) requests a Thumb image for a specific Item ID (in my logs, this is ID 132993). The Emby Server handles this and logs a ResourceNotFoundException. Exactly 4 to 25 milliseconds later, the server process terminates abruptly due to a Segmentation Fault (signal 11 (SIGSEGV)) handled by Android's runtime, forcing a Fatal signal 6 (SIGABRT) to kill the process. Querying the /emby/Items?Ids=132993 endpoint returns {"Items":[],"TotalRecordCount":0}, confirming that the requested ID no longer exists in the server's database (a ghost/stale ID cached on the client). Logcat Backtrace Snippetcrash_log.txt 06-04 19:11:46.987 3758 6237 F libc : exiting due to SIG_DFL handler for signal 11 06-04 19:11:46.987 3758 6237 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 6237 (.NET TP Worker), pid 3758 (emby.embyserver) ... 06-04 19:11:47.588 6940 6940 F DEBUG : backtrace: 06-04 19:11:47.588 6940 6940 F DEBUG : #00 pc 000000000004e2cc /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) 06-04 19:11:47.588 6940 6940 F DEBUG : #01 pc 000000000000506c /system/bin/app_process64 (art::SignalChain::Handler(int, siginfo*, void*)+1112) 06-04 19:11:47.588 6940 6940 F DEBUG : #02 pc 0000000000000690 [vdso] (__kernel_rt_sigreturn) 06-04 19:11:47.588 6940 6940 F DEBUG : #03 pc 000000000002c334 <anonymous:2d89fb4000> 04-06_embyserver-63916197567.txt 04-06_embyserver-63916192833.txt 04-06_embyserver-63916193086.txt 04-06_embyserver-63916195806.txt 04-06_embyserver-63916197111.txt

Thanks @hatharryi dont see anything like that in the log. 2026-06-04 19:34:14.642 Info SessionManager: Creating new access token for user 1 username 2026-06-04 19:34:14.643 Debug Notifications: Sending notification to Activity Log Activity Log: username has Authenticated on X99 2026-06-04 19:34:14.643 Debug ConnectService-0HNM0S8DL8O6I:00000001: http/1.1 Response 200 to ‌3.90.164.233‌. Time: 2ms. GET https://‌xxx.xxx.xxx‌/emby/Connect/Exchange?api_key=‌3a948cdd9b974d448c4e043c51af6d72‌&ConnectUserId=165. 2026-06-04 19:34:14.736 Info SessionsService-0HNM0S8DL8O6I:00000002: http/1.1 POST https://‌xxx.xxx.xxx‌/emby/Sessions/Capabilities/Full?api_key=‌68f6efbc75c54761a1f1d60ae5edbbd8‌&Id=22f1fa656fbfeae53f386bd4cc34bf89. Source Ip: ‌3.90.164.233‌, UserAgent: node-fetch/1.0 (+https://github.com/bitinn/node-fetch) 2026-06-04 19:34:14.737 Debug AuthenticationRepository: UpdateCapabilities id: 181 2026-06-04 19:34:14.737 Info SessionsService-0HNM0S8DL8O6I:00000002: http/1.1 Response 204 to ‌3.90.164.233‌. Time: 1ms. POST https://‌xxx.xxx.xxx‌/emby/Sessions/Capabilities/Full?api_key=‌68f6efbc75c54761a1f1d60ae5edbbd8‌&Id=22f1fa656fbfeae53f386bd4cc34bf89. 2026-06-04 19:34:18.629 Debug ActivityLogService-0HNM0S8DL8O6J:00000001: http/1.1 GET http://‌192.168.4.162‌:8096/emby/System/ActivityLog/Entries?StartIndex=0&Limit=10&MinDate=2026-05-28T18:34:18.625Z&hasUserId=true&EnableTotalRecordCount=false&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=85c51e9e-c5ca-4e70-93ab-b84e0cfc0ae2&X-Emby-Client-Version=4.10.0.13&X-Emby-Token=‌08ee0c9906974dccaa8b70809aa33763‌&X-Emby-Language=en-gb. Source Ip: ‌192.168.4.162‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36 2026-06-04 19:34:18.629 Debug ActivityLogService-0HNM0S8DL8O6K:00000001: http/1.1 GET http://‌192.168.4.162‌:8096/emby/System/ActivityLog/Entries?StartIndex=0&Limit=4&MinDate=2026-05-28T18:34:18.626Z&hasUserId=false&EnableTotalRecordCount=false&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=85c51e9e-c5ca-4e70-93ab-b84e0cfc0ae2&X-Emby-Client-Version=4.10.0.13&X-Emby-Token=‌08ee0c9906974dccaa8b70809aa33763‌&X-Emby-Language=en-gb. Source Ip: ‌192.168.4.162‌, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/148.0.0.0 Safari/537.36 2026-06-04 19:34:18.641 Debug ActivityLogService-0HNM0S8DL8O6K:00000001: http/1.1 Response 200 to ‌192.168.4.162‌. Time: 11ms. GET http://‌192.168.4.162‌:8096/emby/System/ActivityLog/Entries?StartIndex=0&Limit=4&MinDate=2026-05-28T18:34:18.626Z&hasUserId=false&EnableTotalRecordCount=false&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=85c51e9e-c5ca-4e70-93ab-b84e0cfc0ae2&X-Emby-Client-Version=4.10.0.13&X-Emby-Token=‌08ee0c9906974dccaa8b70809aa33763‌&X-Emby-Language=en-gb. 2026-06-04 19:34:18.657 Debug ActivityLogService-0HNM0S8DL8O6J:00000001: http/1.1 Response 200 to ‌192.168.4.162‌. Time: 29ms. GET http://‌192.168.4.162‌:8096/emby/System/ActivityLog/Entries?StartIndex=0&Limit=10&MinDate=2026-05-28T18:34:18.625Z&hasUserId=true&EnableTotalRecordCount=false&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=85c51e9e-c5ca-4e70-93ab-b84e0cfc0ae2&X-Emby-Client-Version=4.10.0.13&X-Emby-Token=‌08ee0c9906974dccaa8b70809aa33763‌&X-Emby-Language=en-gb. 2026-06-04 19:34:26.486 Info SessionsService-0HNM0S8DL8O6L:00000001: http/1.1 POST https://‌xxx.xxx.xxx‌/emby/Sessions/Capabilities/Full?api_key=‌68f6efbc75c54761a1f1d60ae5edbbd8‌&Id=22f1fa656fbfeae53f386bd4cc34bf89. Source Ip: ‌3.90.164.233‌, UserAgent: node-fetch/1.0 (+https://github.com/bitinn/node-fetch) 2026-06-04 19:34:26.487 Debug AuthenticationRepository: UpdateCapabilities id: 181 2026-06-04 19:34:26.487 Info SessionsService-0HNM0S8DL8O6L:00000001: http/1.1 Response 204 to ‌3.90.164.233‌. Time: 1ms. POST https://‌xxx.xxx.xxx‌/emby/Sessions/Capabilities/Full?api_key=‌68f6efbc75c54761a1f1d60ae5edbbd8‌&Id=22f1fa656fbfeae53f386bd4cc34bf89. 2026-06-04 19:34:26.574 Debug ItemsService-0HNM0S8DL8O6L:00000002: http/1.1 GET https://‌xxx.xxx.xxx‌/emby/Users/6cc6d0fa039849af8147592f5da46188/Items?api_key=‌68f6efbc75c54761a1f1d60ae5edbbd8‌&Fields=Id,Name,AlbumArtist,MediaType&SortBy=Random&IncludeItemTypes=Audio&Recursive=true&GenreIds=&ArtistIds=&ParentId=&Limit=400&EnableTotalRecordCount=false&EnableImages=false&EnableUserData=false. Source Ip: ‌3.90.164.233‌, UserAgent: node-fetch/1.0 (+https://github.com/bitinn/node-fetch) 2026-06-04 19:34:27.003 Debug ItemsService-0HNM0S8DL8O6L:00000002: http/1.1 Response 200 to ‌3.90.164.233‌. Time: 428ms. GET https://‌xxx.xxx.xxx‌/emby/Users/6cc6d0fa039849af8147592f5da46188/Items?api_key=‌68f6efbc75c54761a1f1d60ae5edbbd8‌&Fields=Id,Name,AlbumArtist,MediaType&SortBy=Random&IncludeItemTypes=Audio&Recursive=true&GenreIds=&ArtistIds=&ParentId=&Limit=400&EnableTotalRecordCount=false&EnableImages=false&EnableUserData=false. Alexa on phone gives a bit more feedback. "media type audio is unsupported on amazon echo, please change to a supported device" If i dont see "Info UniversalAudioService" does that say the issue is with the server rather than how alexa is using the info..or does that bit of the log only show up once the client requests the URL it has been sent? So are some ddns not liked? i am using mywire.org from dynu systems. is there a known good ddns i should test? Edit: I dont think its related but the other change i made a few months ago was to change the Emby username of my main emby account. But i have since disabled and relinked the skill using my email address and password.

Hi, did you try clicking the 3-dot button on the series screen?

New Emby server Beta release, v4.10.0.14.