All Activity

I think it’s begin on Monday the 13th

No. Web app works fine. Only edge at windows is display ing this error

OK we'll take a look at it. What i would suggest doing in the meantime is using the portable download: https://emby.media/windows-server.html Please let us know if this helps. Thanks.

Right it just would help to know so that I can make sure to be looking at the right log file. And is this with the Emby web app?

It is very hard to say exact time, but I have that since two days maybe three days.

Can you please provide a log from the app? Thanks.

Can you please provide a log from the app? Thanks.

Yes

Hi, there's a lot of log files here. What time did the problem occur?

Is Windows fully up to date?

Hi, I haven't seen this before. Please let us know if you find anything. Thanks.

Hi, this is case insensitive. It does not matter whether you send username or Username or UserName.

Theme Maker · What's New Movies are now supported — via ChapterAPI intro markers Theme Maker builds a per-title theme video/music from an intro's IntroStart → IntroEnd span. Emby only auto-creates those markers for episodes, so movies were skipped. Now you can point it at a movie by setting the markers yourself — e.g. around a favourite scene — using the Chapter API / Chapter Editor. 01 Why movies needed a manual step Theme Maker is marker-driven: it reads an item's IntroStart/IntroEnd chapter markers and cuts exactly that span. Episodes get those markers from Emby's intro detection; movies don't. So for a movie you simply provide the span — mark the seconds you want the theme cut from — and Theme Maker treats it exactly like an episode. Delete the markers afterward if you like; the theme file stays. 02 How to make a movie theme 1 In Theme Maker settings, turn on Include movies (default: off, so existing series-only setups are unaffected). 2 On the movie, add two chapter markers via the Chapter API / Chapter Editor: one of type IntroStart and one of type IntroEnd, bracketing the scene you want as the theme. 3 Run Theme Maker: Preview (read-only) to confirm it sees the movie — the log shows '<Movie>' (movie): source intro … — then run Theme Maker: Generate. 4 The theme lands in the movie's own folder — backdrops/theme.mp4 and/or theme.mp3 — exactly like a series. You can remove the markers now; the theme file remains. Mind the length limits. The marked span must fall between Minimum intro length (default 8s) and Maximum intro length (default 150s) — a span outside that range is silently skipped. So a ~2-minute favourite scene works out of the box; if you want a longer theme, raise Maximum intro length in settings first. Standard Pad start / Pad end and fade settings apply to movies too. 03 Good to know Off by default. If you don't enable Include movies, nothing changes — series are processed exactly as before. One folder per movie is assumed (standard Emby layout). The theme is written to the folder that contains the movie file. No markers = skipped, cleanly. A movie without IntroStart/IntroEnd just logs "no intro markers" and is left untouched — no errors. Same encode pipeline. Movies use the identical ffmpeg cut, downscale, fade and audio-language handling as series — nothing to configure separately. TL;DR: Enable Include movies → set IntroStart/IntroEnd on the movie via Chapter API (8–150s span) → Generate → get backdrops/theme.mp4 + theme.mp3 in the movie folder. Download github.com/Oratorian/emby-theme-maker/releases Grab the latest EmbyThemeMaker.dll from the newest release. Source github.com/Oratorian/emby-theme-maker Source, README and issue tracker.

Thanks for the response. To clarify, after playback stops, it brings me back to the movie info screen and then if I try to play the movie again (even without subtitles enabled) it will freeze and force close the Emby app. Seems I have to give the server a bit of time before I try to play a movie again or else that happens.

Hi, send a message to @ebr

@Luke Sorry to poke you, but how do plugins get access to the emby Repo?

Ah, I see now you already did do that. Thanks. As I observed from the video, the server simply stops responding and that is why playback stops. The app is not "crashing". Playback is failing because the server stops responding. The question is why... failed to connect to /192.168.0.57 (port 8096) from /:: (port 54272): connect failed: ECONNREFUSED (Connection refused) Hopefully, Luke can spot something server side.

Hello ebr, The problem is happening on all movies with subtitles even if its just one track. Also all these movies subtitles were working fine just a few weeks ago. I just reproduced the problem again and sent the logs from the app. User: MartinVallejo Movie: 3:10 To Yuma Logs sent: 1:51pm ET

Is it still writing its own NFO, or does it now write to the media's existing NFO? What's the best way for me to go about handling my existing backups and intros? I have some intros that aren't backed up, because they were marked after Cheese's plugin stopped working, and I don't want to lose those, but I also want to restore the intros I did have backed up with Cheese's plugin and have since lost. I'm still on .17 for now, so I can't install this until I have time to do a full server update.

Hi Emby community, I think there is a login bug in Emby server 4.9.5.0. The web login fails for me across multiple devices and browsers, and the server log shows Value cannot be null. (Parameter 'name') on POST /emby/Users/authenticatebyname. After checking the network request, I found that Emby Web sends the form body as Username=myuser&Pw=mypassword, but the server seems to expect UserName=myuser&Pw=mypassword with a capital N. I tested this manually: Username=test&Pw=test returns HTTP 400 with the null name error, while UserName=test&Pw=test reaches normal login handling. As a temporary local fix, I changed the bundled web client from Username:name to UserName:name, and login started working again. Could you please check this casing mismatch?

Hi. From the app perspective, it looks like your server stops responding during the attempt to switch to those subs. Do all of the problem items have 25+ subtitle tracks? Can you also reproduce that and then follow the instructions to send a log from the app? Thanks.

The beta was just for testing, not a solution. A new stable with the new ARM64 package will be out in the new 2 days if all goes well. Thanks

and I forgot the Emby Plugin → Com Skipper

Thanks for the prompt responses. Please see below information: User: MartinVallejo Logs sent: 12:30 ET Problem: Tried to activate subtitles while watching 2001: A Space Odyssey mkv (happens with all movies) I have attached a video and what I think are the correct logs from the web app. Please let me know if there is anything else I can provide. embyserver-63919888164.txt ffmpeg-transcode-e6103ed0-bae5-401a-847d-7adc43d88a24_1.txt hardware_detection-63919888172.txt 20260717_123245.mp4

Manually installing an Emby plugin on Synology — DLL drop For plugins that aren't in the catalog — a third-party plugin shipped as a .dll (sometimes inside a .zip). Drop the DLL into Emby's plugins folder and restart. The only Synology-specific trick is finding that folder. Native or Docker? The steps are the same — only the plugins-folder path differs depending on whether you installed the Emby .spk package from Package Center or you run Emby in Container Manager / Docker. Both paths are below. Step 1 — Find your plugins folder The plugins folder sits directly below Emby's data folder. Don't guess the path — Emby tells you where it is: open Dashboard → 3-dot menu → Get Server Info (or check the Paths section) and note the data folder, then look for plugins just under it. native .spk → typically /volume1/@appdata/EmbyServer/plugins/ (a hidden system folder — reach it over SSH or WinSCP; confirm the exact path from Dashboard first) Docker → inside the folder you mapped to /config, e.g. /volume1/docker/emby/config/plugins/ (a normal shared folder — just browse to it in File Station) Step 2 — Drop the DLL in and restart Stop Emby Server before copying anything — Package Center for a native install, Container Manager for Docker. If the plugin came as a .zip, unzip it and locate the .dll. Copy the .dll into the plugins folder from Step 1. Replacing an older copy? Rename the old one to .dll.old first. Fix ownership/permissions — the step people miss on a NAS. Make the new .dll match the owner and permissions of the other .dll files already in that folder, or Emby won't load it. Start Emby Server again. Confirm it under Dashboard → Plugins → My Plugins. Docker tip: because the plugins folder lives in a normal shared folder, you can do the whole thing from File Station — no SSH needed. The native package hides its data under @appdata, so SSH (or WinSCP) is the practical way in. If the plugin doesn't show up Server wasn't fully stopped when you copied the DLL — stop it, recopy, start. Wrong ownership/permissions on the .dll — match it to the neighbouring plugin files. Wrong folder — re-check the data-folder path in Get Server Info; the file belongs in plugins, directly below it. Check the server log for a load error mentioning the plugin. In short: stop the server, drop the DLL into the plugins folder below your data folder, match the file's permissions to its neighbours, start again.