All Activity

Good evening. I have a problem with this series. The metadata doesn't match the files. In the first screenshot, the file name and episode number are correct after viewing the file with VLC. See screenshot. However, when I open EMBY and view the season, even after correcting it by refreshing the metadata, it doesn't fix the problem. Thanks

If i move the main source selection of collection and playlist, into the "smart playlist" filters, would that do it?

+1 to this

Has anyone had success on the WebStreams plugin with regards to VOD's from Apollogroup TV via Startup Show? Thank you.

i bought the cert from xolphin and it is a comodo cert

Thanks for your reply. The thing is, even after disabling outside connections, new attempts occured. And same pattern (6 attemps per existing user), same time (around 11:50 am). Both accounts already had passwords. Is there any way to check what distant IP tried to connect? Per the log and Emby alerts, no weird IP is shown.

Hi, usually lowering the quality setting will help with this kind of issue. Yea this is not good. This will undoubtedly blow up resource consumption on your server.

If it's a failed login attempt then probably not. It looks like someone is trying to login to your server. I would suggest making sure that your users have passwords. What you can also that will help (but possibly temporarily), is you could change the public facing router port to something different than the default. It just depends on who is trying to login and how determined they are. If they do a port scan then eventually they'll find the new port.

Mostly. I think the password was correct, but the device settings set it up for success.

@S0ldy Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

Hi, how does searching for the same content in the Emby web app compare?

Hi, what do you mean by dots?

Hi @Brucevankesselwhere did your server SSL certificate come from?

Great So it was a combination of issues - multiple routers - port forwading issues - wrong password - device access restriction

sooo i have this problem to.. cant connect .. and yes i did renew my cert. and i also did the pcks#12 thingy during a browser session (on samsung tv) it said : wrong ssl cert in the app it wont connect but all other devices will connect .. also my LG tv connects perfectly i reinstalld the emby app etc.. still no luck

The ts chunks are taking ~2 seconds to be delivered, which is a very long time considering that later on it takes only a few ms to deliver. This probably means that it's transcoding at full speed for the whole file and then stops, but having said that 2 seconds is still fast enough to deliver without buffering since each chunk is 3 seconds long (-segment_time 00:00:03.000). Looks like your system is pretty slow to handle this, and there's no log entries for Theater to compare with, which should be able to direct play this file. Please include the ffmpeg transcode log as well. BTW, why did you configure your transcoding temp folder to /data/radio/transcoding-temp when you have /data/radio as a library path? This is causing constant rescans of that folder - probably RTM is enabled for this library.

Hello, Few days ago I noticed random connection attempts on my Emby server. Then, 3 days after, the same thing happened : 6 connection attempts for each user. One of the user being me, always connected, and the other being a spare account not connected since a month. You can see the IP is from a local network (managed by Docker). After the failed attempts, Emby locks the users, but I have no issue using Emby afterwars, as if nothing at all happened. After the first attempts, I disabled outside connections just in case, but after 3 days it happened again. During the first instance of attempts, no one was using the server. During the second instance of attempts, I was watching something (with the Emby Windows app). So I'm wondering if this is an internal bug or if the API key used by other services (Seerr and Homarr) could cause this. Not sure about the API because it wouldn't try to log in with the available users, it doesn't work like that (to my understanding). Any idea what could explain this behaviour? Attached is a log extract highlighting the issue. Thanks for your help! embylog.txt

I've run into the exact same problem. VTT subtitles in MKV files aren't being detected on Windows Emby Server. Apparently, this issue hasn't been resolved yet. I really hope our talented developers will be able to fix this. Thanks for your hard work, Developers.

this happens on both Emby Theater and web app in Linuxmint 22.3

Hello, I am currently in France. I have an echo dot that is connected to my US home and US Amazon account I have Emby running as my media server When I try to get my dots to play music from emby, it tells me it is having trouble accessing my emby skill. Any suggestions? Thank you

I am trying to determine whether something changed in the way Emby handles local people images. On 4.8.0, this used to work properly for me. I could place the person image in the person’s folder under metadata/people, and if I later replaced that image, a metadata refresh would pick up the change and the updated image would display. I'm now on 4.10.04. That no longer seems to be the case. What I am seeing now is this: If I manually add a person photo through the web UI, Emby saves it as folder.jpg in that person’s folder under metadata/people. That appears to confirm the location is correct. However, if I then overwrite that same folder.jpg on disk with a different image, Emby does not display the replacement image. Instead, the person image goes blank again. So at least on my system, this no longer behaves the way it used to. Previously, replacing the local image and refreshing metadata was sufficient. Now it is not. Has something changed in how local people images are cached or refreshed? Is directly replacing folder.jpg no longer expected to work? If so, what is the current recommended method for updating local people images outside the web editor?

@madevilCould you let me know if the problem is still arising with the latest beta build. The current beta is 3.5.31 - download link available here

hi guys any news on this? Z

Has this been fixed at all?