internet speed issue with emby server

[El_Cookie 7]

Hello everyone,

I have a bandwidth problem with emby, my maximum connection is limited to 3 Mo/s with emby.

So when I have several users it lags for them.

However, the internet connection for my server is: upload 400 Mbps / Download 1 Gbps .

Theoretically I should be able to upload at 400 Mbps max? But it's not the case, I'm limited to 3 Mo/s.

 

Video download test:

- Lan 3 Mo/s download for me

- Wan 3 Mo/s download for any user

 

Network configuration :

Internet => Internet box => Truenas Scale [ Kubernet cluster { Traefik => Emby Server (4.7.13.0)} ]

Https connection enabled

 

On my Truenas Scale I installed openspeedtest and here are the results:

- Lan (http) all bandwidth used

- Wan (https) download 335 Mbps

 

So my conclusion is that it's not coming from Truenas or my internet connection, but from the emby application.

 

Someone can help me to resolve this problem ?

Edited August 8, 2023 by El_Cookie

[Q-Droid 989]

Please attach hardware specs, server log, hardware detection log and ffmpeg logs.

[El_Cookie 7]

Sorry,  how can I get hardware detection log and ffmpeg log ?

I'd like to point out that there's no transcoding when viewing video, so there's no ffmpeg-transcode log, just direct play.

[Q-Droid 989]

All logs are in the same directory.

Are you limiting bandwidth in Emby or Traefik?

 

[El_Cookie 7]

Hardware spec:
- CPU : AMD Ryzen 9 5900X 12 core
- OS : TrueNAS SCALE 22.12.3.2
- GPU : Nvidia T400 
- Ram : 96 Go
- Stockage : SSD 256 Go for OS - SSD Nvme 1 To for apps - 24 To HDD for Data 
- Ethernet : 
    - Intel Full duplex 1Gbit 
    

Server log when I try to download movies :

2023-08-08 14:36:09.338 Debug Server: http/1.1 Response 200 to host4. Time: 0ms. http://emby_remote_ip/emby/system/info/public
2023-08-08 14:36:09.364 Debug Server: http/1.1 GET http://emby_remote_ip/emby/System/Info. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:09.365 Debug Server: http/1.1 Response 200 to host4. Time: 1ms. http://emby_remote_ip/emby/System/Info
2023-08-08 14:36:09.391 Debug Server: http/1.1 GET http://emby_remote_ip/emby/DisplayPreferences/usersettings?userId=d139d0b47ada44a3b16deffb794888d7&client=emby&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:09.391 Debug Server: http/1.1 Response 200 to host4. Time: 1ms. http://emby_remote_ip/emby/DisplayPreferences/usersettings?userId=d139d0b47ada44a3b16deffb794888d7&client=emby&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr
2023-08-08 14:36:09.398 Info Server: http/1.1 POST http://emby_remote_ip/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr&reqformat=json. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:09.398 Debug AuthenticationRepository: UpdateCapabilities id: 28
2023-08-08 14:36:09.399 Info Server: http/1.1 Response 204 to host4. Time: 1ms. http://emby_remote_ip/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr&reqformat=json
2023-08-08 14:36:09.465 Debug Server: http/1.1 GET http://emby_remote_ip/emby/Users/d139d0b47ada44a3b16deffb794888d7/Views?X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:09.465 Debug Server: http/1.1 GET http://emby_remote_ip/emby/System/Configuration?X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:09.465 Debug Server: http/1.1 GET http://emby_remote_ip/emby/web/configurationpages?PageType=PluginConfiguration&UserId=d139d0b47ada44a3b16deffb794888d7&EnableInMainMenu=true&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:09.466 Debug Server: http/1.1 Response 200 to host4. Time: 1ms. http://emby_remote_ip/emby/System/Configuration?X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr
2023-08-08 14:36:09.466 Debug Server: http/1.1 Response 200 to host4. Time: 0ms. http://emby_remote_ip/emby/web/configurationpages?PageType=PluginConfiguration&UserId=d139d0b47ada44a3b16deffb794888d7&EnableInMainMenu=true&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr
2023-08-08 14:36:09.466 Debug Server: http/1.1 GET http://emby_remote_ip/emby/System/Logs/Query?SortBy=SortName&SortOrder=Ascending&Fields=BasicSyncInfo,CanDelete,Container,PrimaryImageAspectRatio,ProductionYear,Status,EndDate,CommunityRating,OfficialRating,CriticRating&StartIndex=0&EnableImageTypes=Primary,Backdrop,Thumb&ImageTypeLimit=1&Limit=30&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:09.466 Debug Server: http/1.1 Response 200 to host4. Time: 1ms. http://emby_remote_ip/emby/Users/d139d0b47ada44a3b16deffb794888d7/Views?X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr
2023-08-08 14:36:09.467 Debug Server: http/1.1 Response 200 to host4. Time: 1ms. http://emby_remote_ip/emby/System/Logs/Query?SortBy=SortName&SortOrder=Ascending&Fields=BasicSyncInfo,CanDelete,Container,PrimaryImageAspectRatio,ProductionYear,Status,EndDate,CommunityRating,OfficialRating,CriticRating&StartIndex=0&EnableImageTypes=Primary,Backdrop,Thumb&ImageTypeLimit=1&Limit=30&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr
2023-08-08 14:36:11.554 Debug Server: http/1.1 GET http://emby_remote_ip/emby/Items/45918/Download?mediaSourceId=f7522ccb7195a73fbb5a9c4369d318e1. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:14.382 Debug Server: http/1.1 GET http://172.16.3.58:8096/. UserAgent: kube-probe/1.25
2023-08-08 14:36:14.382 Debug Server: http/1.1 GET http://172.16.3.58:8096/. UserAgent: kube-probe/1.25
2023-08-08 14:36:14.382 Debug Server: http/1.1 Response 302 to host10. Time: 0ms. http://172.16.3.58:8096/
2023-08-08 14:36:14.382 Debug Server: http/1.1 Response 302 to host10. Time: 0ms. http://172.16.3.58:8096/
2023-08-08 14:36:14.636 Debug Server: http/1.1 GET http://host6:10079/emby/System/ActivityLog/Entries?StartIndex=0&Limit=10&MinDate=2023-08-01T12:36:12.288Z&hasUserId=true&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=0f5bf628-451a-492c-8439-3dee658b4508&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:14.636 Debug Server: http/1.1 GET http://host6:10079/emby/System/ActivityLog/Entries?StartIndex=0&Limit=4&MinDate=2023-08-01T12:36:12.288Z&hasUserId=false&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=0f5bf628-451a-492c-8439-3dee658b4508&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:14.637 Debug Server: http/1.1 Response 200 to host7. Time: 2ms. http://host6:10079/emby/System/ActivityLog/Entries?StartIndex=0&Limit=10&MinDate=2023-08-01T12:36:12.288Z&hasUserId=true&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=0f5bf628-451a-492c-8439-3dee658b4508&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr
2023-08-08 14:36:14.637 Debug Server: http/1.1 Response 200 to host7. Time: 2ms. http://host6:10079/emby/System/ActivityLog/Entries?StartIndex=0&Limit=4&MinDate=2023-08-01T12:36:12.288Z&hasUserId=false&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=0f5bf628-451a-492c-8439-3dee658b4508&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr
2023-08-08 14:36:18.571 Debug Server: http/1.1 GET http://emby_remote_ip/web/manifest.json. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:18.572 Debug Server: http/1.1 Response 304 to host4. Time: 0ms. http://emby_remote_ip/web/manifest.json
2023-08-08 14:36:18.849 Debug Server: http/1.1 GET http://emby_remote_ip/emby/system/info/public. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:18.849 Debug Server: http/1.1 Response 200 to host4. Time: 0ms. http://emby_remote_ip/emby/system/info/public
2023-08-08 14:36:18.873 Debug Server: http/1.1 GET http://emby_remote_ip/emby/System/Info. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:18.873 Debug Server: http/1.1 Response 200 to host4. Time: 1ms. http://emby_remote_ip/emby/System/Info
2023-08-08 14:36:18.897 Debug Server: http/1.1 GET http://emby_remote_ip/emby/DisplayPreferences/usersettings?userId=d139d0b47ada44a3b16deffb794888d7&client=emby&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:18.897 Debug Server: http/1.1 Response 200 to host4. Time: 1ms. http://emby_remote_ip/emby/DisplayPreferences/usersettings?userId=d139d0b47ada44a3b16deffb794888d7&client=emby&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr
2023-08-08 14:36:18.901 Info Server: http/1.1 POST http://emby_remote_ip/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr&reqformat=json. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:18.902 Debug AuthenticationRepository: UpdateCapabilities id: 28
2023-08-08 14:36:18.902 Info Server: http/1.1 Response 204 to host4. Time: 1ms. http://emby_remote_ip/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr&reqformat=json
2023-08-08 14:36:18.977 Debug Server: http/1.1 GET http://emby_remote_ip/emby/Users/d139d0b47ada44a3b16deffb794888d7/Views?X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:18.978 Debug Server: http/1.1 Response 200 to host4. Time: 1ms. http://emby_remote_ip/emby/Users/d139d0b47ada44a3b16deffb794888d7/Views?X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr
2023-08-08 14:36:18.981 Debug Server: http/1.1 GET http://emby_remote_ip/emby/System/Configuration?X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:18.982 Debug Server: http/1.1 Response 200 to host4. Time: 0ms. http://emby_remote_ip/emby/System/Configuration?X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr
2023-08-08 14:36:18.984 Debug Server: http/1.1 GET http://emby_remote_ip/emby/web/configurationpages?PageType=PluginConfiguration&UserId=d139d0b47ada44a3b16deffb794888d7&EnableInMainMenu=true&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:18.985 Debug Server: http/1.1 Response 200 to host4. Time: 0ms. http://emby_remote_ip/emby/web/configurationpages?PageType=PluginConfiguration&UserId=d139d0b47ada44a3b16deffb794888d7&EnableInMainMenu=true&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr
2023-08-08 14:36:18.985 Debug Server: http/1.1 GET http://emby_remote_ip/emby/System/Logs/Query?SortBy=SortName&SortOrder=Ascending&Fields=BasicSyncInfo,CanDelete,Container,PrimaryImageAspectRatio,ProductionYear,Status,EndDate,CommunityRating,OfficialRating,CriticRating&StartIndex=0&EnableImageTypes=Primary,Backdrop,Thumb&ImageTypeLimit=1&Limit=30&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188
2023-08-08 14:36:18.986 Debug Server: http/1.1 Response 200 to host4. Time: 1ms. http://emby_remote_ip/emby/System/Logs/Query?SortBy=SortName&SortOrder=Ascending&Fields=BasicSyncInfo,CanDelete,Container,PrimaryImageAspectRatio,ProductionYear,Status,EndDate,CommunityRating,OfficialRating,CriticRating&StartIndex=0&EnableImageTypes=Primary,Backdrop,Thumb&ImageTypeLimit=1&Limit=30&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr
2023-08-08 14:36:21.100 Debug Server: http/1.1 GET http://emby_remote_ip/emby/System/Logs/embyserver.txt/Lines?SortBy=SortName&SortOrder=Ascending&Fields=BasicSyncInfo,CanDelete,Container,PrimaryImageAspectRatio,ProductionYear,Status,EndDate,CommunityRating,OfficialRating,CriticRating&StartIndex=0&EnableImageTypes=Primary,Backdrop,Thumb&ImageTypeLimit=1&Sanitize=true&Limit=100&X-Emby-Client=Emby Web&X-Emby-Device-Name=Microsoft Edge Windows&X-Emby-Device-Id=cea69195-5e4b-4a97-b38b-4bc843c605d2&X-Emby-Client-Version=4.7.13.0&X-Emby-Language=fr. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.188

Information top of logs page :
 

Application path: /app/emby
2023-08-08 00:00:00.000 Info App: Logs path: /config/logs
2023-08-08 00:00:00.000 Info App: Cache path: /config/cache
2023-08-08 00:00:00.000 Info App: Internal metadata path: /config/metadata
2023-08-08 00:00:00.000 Info App: Transcoding temporary files path: /transcode/transcoding-temp
2023-08-08 00:00:00.000 Info App: Plugins:
AniSearch 1.0.0.0
Bluray Folder Support 1.0.0.0
Cinema Intros 1.0.40.0
DLNA 1.2.7.0
Dvd Folder Support 1.0.0.0
Emby Guide Data 1.0.12.0
Fanart.tv 1.0.14.0
M3U TV Tuner 1.0.13.0
MovieDb 1.6.8.0
MusicBrainz 1.0.22.0
Nfo Metadata 1.0.75.0
OMDb 1.0.20.0
Open Subtitles 1.0.34.0
Port Mapper 1.2.1.0
Studio Images 1.0.3.0
TheAudioDb 1.0.18.0
TheTVDB 1.4.0.0
Trailers 1.3.6.0
Webhooks 1.0.25.0
XmlTV 1.1.2.0 

 

[Q-Droid 989]

You can attach the log files instead of pasting.

 

[El_Cookie 7]

Traefik and Emby are not limited and user too.

i have another test application behind traefik and it works fine.
 

[El_Cookie 7]

An other test since 14:48:30 

embyserver.txt

[Q-Droid 989]

Have you found transcoding logs? Attach if you have.

Is your server local to you or hosted?

Are the Emby default ports (8096) exposed on your LAN and can you connect directly to your Emby server and test? Bypassing Traefik. I see a kube probe is able to reach Emby on the default port.

There are limits in effect and this is possibly due to the unreliable bandwidth detection for Emby clients. So for now focus on LAN connections to see if you can get around this limit. If you don't have local networks defined in the settings AND it turns out that all connections are treated as remote then you may need to list subnets to be treated as local.

Quote

2023-08-08 10:37:08.541 Info App: User policy for admin. EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True
2023-08-08 10:37:08.541 Info App: Bitrate exceeds DirectPlay limit: media bitrate: 10297651, max bitrate: 1500000
2023-08-08 10:37:08.542 Info App: Bitrate exceeds DirectStream limit: media bitrate: 10297651, max bitrate: 1500000
2023-08-08 10:37:08.543 Info App: Bitrate exceeds DirectPlay limit: media bitrate: 10297651, max bitrate: 1500000
2023-08-08 10:37:08.543 Info App: Bitrate exceeds DirectStream limit: media bitrate: 10297651, max bitrate: 1500000
2023-08-08 10:37:08.543 Info App: Bitrate exceeds DirectPlay limit: media bitrate: 10297651, max bitrate: 1500000

Test the above with a LAN connection to see if anything changes. This may take a few rounds of testing to sort out before you have a final solution.

 

[El_Cookie 7]

Quote

Have you found transcoding logs? Attach if you have.

Today (08/08/2023) I have only one file, I've attached transcoding log here.

 

Quote

Is your server local to you or hosted?

Are the Emby default ports (8096) exposed on your LAN and can you connect directly to your Emby server and test? Bypassing Traefik. I see a kube probe is able to reach Emby on the default port.

It's server local for me. I try this with my ip server on lan 192.168.1.**:10079 (port exposed) bypassing Traefik and I'm still limited to 3 mo/s max. 

 

Quote

There are limits in effect and this is possibly due to the unreliable bandwidth detection for Emby clients. So for now focus on LAN connections to see if you can get around this limit. If you don't have local networks defined in the settings AND it turns out that all connections are treated as remote then you may need to list subnets to be treated as local.

I don't really understand how I should configure it so that my local ip 192.168.1.1/24 is seen as the local ip address. you can see below my network config : 

ffmpeg-directstream-2fa0c73c-49a4-464a-a7a3-69cf936890b8_1.txt

[El_Cookie 7]

I try  Plex with same configuration and I download at over 10 mo/s .
 

[Q-Droid 989]

You enter your local subnet in CIDR format in the "LAN networks" field, the first one. It should be 192.168.1.0/24 for your local subnet. Zero, not one. This is so all devices on your LAN appear local to Emby.

But, since you're using a reverse proxy you don't want to access Emby via said proxy while on LAN. Always bypass it because recent changes in Emby can make all proxied connections to appear as remote.

Remote clients may have change their streaming options (playback quality settings) from Auto to a value that matches their own available downstream bandwidth or the quality they want.

 

[El_Cookie 7]

After restart Emby server I have found hardware detection logs.

 

hardware_detection-63827105353.txt

[El_Cookie 7]

Quote

You enter your local subnet in CIDR format in the "LAN networks" field, the first one. It should be 192.168.1.0/24 for your local subnet. Zero, not one. This is so all devices on your LAN appear local to Emby.

But, since you're using a reverse proxy you don't want to access Emby via said proxy while on LAN. Always bypass it because recent changes in Emby can make all proxied connections to appear as remote.

Noted .

Quote

Remote clients may have change their streaming options (playback quality settings) from Auto to a value that matches their own available downstream bandwidth or the quality they want.

So I'm still limited by 3 Mo/s bandwidth on local ip address and Wan IP address with my domain name. 
I try with my phone on 5G . this limitation means that many people outside my network will not be able to watch properly. For example 3 Mo/s divided by 10 users is not good. Or my connection allows 40 Mo/s theoretical

 

Edited August 8, 2023 by El_Cookie

[Q-Droid 989]

Restart Emby after you make the changes. Then test again and post a fresh server log. We want to make sure the LAN connections are seen as local.

For remote connections (test on 5G) change the client app settings as I posted above. Set the playback quality to a value other than Auto.

Emby limits by stream, not an aggregate. So it will limit the bitrate for the streaming media but it does not act on the network bandwidth. It only deals with the media stream itself and doesn't - can't - do anything to affect the available network bandwidth. For example 10 limited users would each get 3mbps, an aggregate of 30mbps if your network allows. If you are seeing something being throttled at the network then it's not Emby.

 

[El_Cookie 7]

You can see log below.

Playback start at 16:46:43 with movie "Le chevalier noir" but movie stop every 5 seconds. I modified setting on my android emby client to 4K 160 Mbps on internet .

Détail of movies : 

 

The bitrate of the video is higher than the connection speed. I'd have to find someone who also uses TrueNAS Scale to do some tests

embyserver (3).txt hardware_detection-63827109661.txt

[Q-Droid 989]

20 minutes ago, El_Cookie said:

The bitrate of the video is higher than the connection speed.

What do you mean?

When setting the client quality limit it is an "up to" value to allow everything at or below that bitrate.

The test appears to be a remote session. Did you get the LAN sessions working?

 

[El_Cookie 7]

Quote

What do you mean?

What I mean is that the video freezes because of this limitation that I found with emby, because the bitrate exceeds the bitrate that I find with emby. Sorry my english is probably not good.

Quote

The test appears to be a remote session. Did you get the LAN sessions working?

Same issue Lan session freeze with this video. Something being throttled at the network. Maybe the emby container ? 

Right from the first few seconds of playback, the video started lagging. Log here.

embyserver (4).txt

[El_Cookie 7]

I only think about it now but I had the same problem with a Jellyfin container on a linux server with docker-compose. This may help

[Q-Droid 989]

A remote session using a mobile device can have many variables so it's better to use a stable, preferably wired connection to test problems like these. Start with LAN to make sure it is the most reliable then move out to wired WAN then wireless if the others are good. And speaking of variables it might also be better to use media that is known to direct play video and audio to establish a baseline.

This is good. It shows that LAN clients are detected correctly.

Quote

2023-08-08 17:34:46.955 Info App: User policy for admin. EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True
2023-08-08 17:34:46.995 Info App: RemoteClientBitrateLimit: 500000000, RemoteIp: host2, IsInLocalNetwork: True
2023-08-08 17:34:47.006 Info App: RemoteClientBitrateLimit: 500000000, RemoteIp: host2, IsInLocalNetwork: True
2023-08-08 17:34:47.007 Info App: RemoteClientBitrateLimit: 500000000, RemoteIp: host2, IsInLocalNetwork: True

And this too. It's clear this was a remote session and the bitrate limit is set high.

Quote

2023-08-08 18:21:09.562 Info App: User policy for Cookies. EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: False EnableAudioPlaybackTranscoding: True
2023-08-08 18:21:09.562 Info App: RemoteClientBitrateLimit: 500000000, RemoteIp: host3, IsInLocalNetwork: False
2023-08-08 18:21:09.562 Info App: RemoteClientBitrateLimit: 500000000, RemoteIp: host3, IsInLocalNetwork: False
2023-08-08 18:21:09.562 Info App: RemoteClientBitrateLimit: 500000000, RemoteIp: host3, IsInLocalNetwork: False

 

One more thing. If you frequently use apps on LAN (phone, etc.) then it would be good to override the default Local IP address in the network settings to that it reflects your host IP and not the container IP. These are the access links visible on the dashboard. When phones transition from LAN to WAN (mobile network) they use this info to reconnect locally.

 

[El_Cookie 7]

I try with my computer in my home same issue.

I also change local IP visible with my real IP and not ip on container. It's OK now .

 

[Q-Droid 989]

When you play media from PC what do you see in web player Stats for Nerds (OSD sprocket) and Emby server User Sessions dashboard?

How does the same look for phone/tablet on LAN and WAN?

 

[El_Cookie 7]

Quote

And speaking of variables it might also be better to use media that is known to direct play video and audio to establish a baseline.

I don't think the choice of video matters because my problem is already with downloading videos.

No matter which video I choose, I can't get more than 3 Mb/s, whereas with Plex I can get up to 10 Mb/s with applications on the same server and retrieving the same films. 

With Plex : 

Download detail Plex : 

 

With Emby : 

Download detail emby : 

 

The same video 

[Q-Droid 989]

Oh. All along I've assumed you meant streaming, not downloads. My mistake.

 

 

[Q-Droid 989]

Are you selecting "Download" or "Download to"? "Download" on PC runs at wire speed for me - 900+ mbps.

The option "Download to" can add conversion and I don't know details about this feature or how that would affect the download itself.