All Activity

Emby apps will direct play whenever possible to avoid transcoding, so there is nothing extra that you need to do to disable it.

I think you have either the Docker container or Emby Server configured in such a way that all it sees for the client ip address is 172.18.0.1‌. That's going to cause the server to think all connections are local, thereby causing the remote access option to not work. I would suggest re-enabling remote access, getting the network configuration right so that the server sees the original ip address. Then once you've done that, then you can turn off remote access again. But I would leave remote access on until you figure that out just in case you end up with a situation where the opposite happens, and then you end up getting locked out of your server due to that option.

can I disable transcoding, for whole server or do I need it on LAN connections?

But the message on the screen relating to the device access settings was very clear and you did not mention that earlier - that is why i thought you may have had a password issue as well Glad that it is all resolved

Hi, what internet metadata fetchers do you have enabled on the library?

Hi @UsamaWaheedCould you please try this on the latest emby for android beta - which is currently 3.5.31 and let me know if the crash still happens Thanks

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.