sskwhiteshadow 2 Posted February 13, 2025 Posted February 13, 2025 (edited) HI All, Been having strange issues since the upgrade of Emby/Shield: 1. It no longer shows when a Shield device is playing a show (i have 2 in the house) 2. Since its not showing that its watching it isn't marking shows as watched/played 3. When i try and click "played" (check mark) Nothing occurs it doesn't update If I look in the log i can see its playing: 2025-02-13 17:09:03.668 Info Server: http/1.1 POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2025-02-13 17:09:03.669 Info Server: http/1.1 Response 302 to host1. Time: 2ms. POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress 2025-02-13 17:09:03.733 Info Server: http/1.1 GET http://168.119.209.41:8096/emby/Videos/10795/stream.mkv?api_key=x_secret2_x&DeviceId=5c9b158ef4afc0c8&MediaSourceId=27698637309497b4165dce5f04bf2f33&Static=true. Source Ip: host1, Connection=keep-alive, Host=host3, User-Agent=Emby/2.1.23g (Linux;Android 11) ExoPlayerLib/2.18.7, Accept-Encoding=identity, Range=bytes=632264079-, Icy-MetaData=1 2025-02-13 17:09:03.735 Info Server: http/1.1 Response 302 to host1. Time: 1ms. GET http://168.119.209.41:8096/emby/Videos/10795/stream.mkv?api_key=x_secret2_x&DeviceId=5c9b158ef4afc0c8&MediaSourceId=27698637309497b4165dce5f04bf2f33&Static=true 2025-02-13 17:09:04.220 Info Server: http/2 Response 404 to host1. Time: 3ms. GET https://168.119.209.41:8920/emby/Sessions/Playing/Progress 2025-02-13 17:09:04.278 Info Server: http/2 GET https://168.119.209.41:8920/emby/Videos/10795/stream.mkv?api_key=x_secret2_x&DeviceId=5c9b158ef4afc0c8&MediaSourceId=27698637309497b4165dce5f04bf2f33&Static=true. Source Ip: host1, Host=host4, User-Agent=Emby/2.1.23g (Linux;Android 11) ExoPlayerLib/2.18.7, :method=GET, Accept-Encoding=identity, Range=bytes=632264079-, icy-metadata=1 2025-02-13 17:09:10.903 Info App: Sqlite: 284 - automatic index on LastWatchedEpisodes(SeriesPresentationUniqueKey) 2025-02-13 17:09:13.568 Info Server: http/1.1 POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2025-02-13 17:09:13.569 Info Server: http/1.1 Response 302 to host1. Time: 1ms. POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress 2025-02-13 17:09:13.711 Info Server: http/2 Response 404 to host1. Time: 1ms. GET https://168.119.209.41:8920/emby/Sessions/Playing/Progress 2025-02-13 17:09:23.572 Info Server: http/1.1 POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2025-02-13 17:09:23.572 Info Server: http/1.1 Response 302 to host1. Time: 0ms. POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress 2025-02-13 17:09:23.717 Info Server: http/2 Response 404 to host1. Time: 1ms. GET https://168.119.209.41:8920/emby/Sessions/Playing/Progress 2025-02-13 17:09:33.572 Info Server: http/1.1 POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2025-02-13 17:09:33.573 Info Server: http/1.1 Response 302 to host1. Time: 1ms. POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress 2025-02-13 17:09:33.712 Info Server: http/2 Response 404 to host1. Time: 0ms. GET https://168.119.209.41:8920/emby/Sessions/Playing/Progress 2025-02-13 17:09:43.576 Info Server: http/1.1 POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2025-02-13 17:09:43.576 Info Server: http/1.1 Response 302 to host1. Time: 0ms. POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress 2025-02-13 17:09:43.716 Info Server: http/2 Response 404 to host1. Time: 1ms. GET https://168.119.209.41:8920/emby/Sessions/Playing/Progress 2025-02-13 17:09:53.580 Info Server: http/1.1 POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2025-02-13 17:09:53.580 Info Server: http/1.1 Response 302 to host1. Time: 0ms. POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress 2025-02-13 17:09:53.724 Info Server: http/2 Response 404 to host1. Time: 1ms. GET https://168.119.209.41:8920/emby/Sessions/Playing/Progress 2025-02-13 17:10:03.578 Info Server: http/1.1 POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2025-02-13 17:10:03.578 Info Server: http/1.1 Response 302 to host1. Time: 0ms. POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress 2025-02-13 17:10:03.720 Info Server: http/2 Response 404 to host1. Time: 1ms. GET https://168.119.209.41:8920/emby/Sessions/Playing/Progress 2025-02-13 17:10:13.584 Info Server: http/1.1 POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2025-02-13 17:10:13.584 Info Server: http/1.1 Response 302 to host1. Time: 0ms. POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress 2025-02-13 17:10:13.724 Info Server: http/2 Response 404 to host1. Time: 1ms. GET https://168.119.209.41:8920/emby/Sessions/Playing/Progress 2025-02-13 17:10:23.588 Info Server: http/1.1 POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2025-02-13 17:10:23.589 Info Server: http/1.1 Response 302 to host1. Time: 1ms. POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress 2025-02-13 17:10:23.728 Info Server: http/2 Response 404 to host1. Time: 1ms. GET https://168.119.209.41:8920/emby/Sessions/Playing/Progress 2025-02-13 17:10:33.588 Info Server: http/1.1 POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2025-02-13 17:10:33.588 Info Server: http/1.1 Response 302 to host1. Time: 0ms. POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress 2025-02-13 17:10:33.730 Info Server: http/2 Response 404 to host1. Time: 1ms. GET https://168.119.209.41:8920/emby/Sessions/Playing/Progress 2025-02-13 17:10:43.592 Info Server: http/1.1 POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2025-02-13 17:10:43.592 Info Server: http/1.1 Response 302 to host1. Time: 0ms. POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress 2025-02-13 17:10:43.733 Info Server: http/2 Response 404 to host1. Time: 0ms. GET https://168.119.209.41:8920/emby/Sessions/Playing/Progress I also notice that I have my Server set to Require HTTPS but its playing HTTP (I have my cert installed and works on all other devices no issues....) If I use my chrome browser or EMBY on my computer it has no issues embyserver.txt Edited February 13, 2025 by sskwhiteshadow
sskwhiteshadow 2 Posted February 13, 2025 Author Posted February 13, 2025 (edited) Now i change Required SSL to preffered and now i can see the stream no issue and no longer getting error 404 in the emby logs? Can someone assist me in this.. and i need to move this post else wher as i thought it was Android TV related.. but it seems now Not using a reverse proxy Edited February 13, 2025 by sskwhiteshadow
sskwhiteshadow 2 Posted February 13, 2025 Author Posted February 13, 2025 (edited) Now i change Required SSL to preferred not required and now i can see the show being played on dashboard. No issue and no longer getting error 404 in the emby logs for my Nvidea shield and i can see the progress and mark played and all those things. Not using a reverse proxy I use my emby theater app on my PC and it shows port 8920 is working and shows the progress of me watching and no 404 errors for it Latest log host1 seems to be shield device host2 is emby theater on my computer Curious why shield has issues using HTTPs HTTP/2 .. I notice a difference in the request as well: Emby Theater 2025-02-13 17:42:15.563 Info Server: http/2 POST https://host2:8920/emby/Sessions/Playing/Progress?X-Emby-Client=Emby Theater&X-Emby-Device-Name=Peep-machine&X-Emby-Device-Id=Peep-machine&X-Emby-Client-Version=3.0.20&X-Emby-Token=x_secret3_x&X-Emby-Language=en-us&reqformat=json. Source Ip: host1, UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) EmbyTheater/3.0.20 Chrome/87.0.4280.141 Electron/11.5.0 Safari/537.36 SHIELD: 2025-02-13 17:42:20.012 Info Server: http/1.1 POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress. Source Ip: host1, UserAgent: Dalvik/2.1.0 (Linux; U; Android 11; SHIELD Android TV Build/RQ1A.210105.003) 2025-02-13 17:42:20.012 Info Server: http/1.1 Response 302 to host1. Time: 0ms. POST http://168.119.209.41:8096/emby/Sessions/Playing/Progress 2025-02-13 17:42:20.152 Info Server: http/2 Response 404 to host1. Time: 0ms. GET https://168.119.209.41:8920/emby/Sessions/Playing/Progress latest file embyserver1.txt Edited February 13, 2025 by sskwhiteshadow
Luke 42078 Posted February 14, 2025 Posted February 14, 2025 Hi, the fact that you were getting those 404's means that the server thinks the 192.X address is a remote connection, and not inside your local network. Do you have some kind of odd network setup that could cause this? Have you configured any other options in Emby Server network settings?
sskwhiteshadow 2 Posted February 14, 2025 Author Posted February 14, 2025 What 192.x address? I see 168.119.209.41 which is my public ip address root@PeepMain ~ # netstat -tulnp | grep EmbyServer tcp6 0 0 :::8920 :::* LISTEN 504949/EmbyServer tcp6 0 0 :::8096 :::* LISTEN 504949/EmbyServer udp 0 0 168.119.209.41:38245 0.0.0.0:* 504949/EmbyServer udp 0 0 0.0.0.0:38715 0.0.0.0:* 504949/EmbyServer udp 0 0 127.0.0.1:39621 0.0.0.0:* 504949/EmbyServer udp 0 0 0.0.0.0:1900 0.0.0.0:* 504949/EmbyServer udp6 0 0 :::7359 :::* 504949/EmbyServer
Luke 42078 Posted February 14, 2025 Posted February 14, 2025 I'm really sorry. I misread the log file. The reason for the 404's is that POST requests are getting redirected into GET. On the server there is no way to avoid this. Anyway that is the technical reason. The redirect to https is really just meant for the web app when you are putting the server address into the browser address bar. What you should do is sign out of the app that you're connecting from, then do a new server connection to your https address. Please see if that helps.
sskwhiteshadow 2 Posted February 16, 2025 Author Posted February 16, 2025 (edited) So if i signout and put in the URL and sign in without emby connect it seems to work. BUT if i use my emby connect account it keeps running into the issue. Weird that if i use emby connect account it keeps running into this issue. Edited February 16, 2025 by sskwhiteshadow
Luke 42078 Posted February 21, 2025 Posted February 21, 2025 On 2/15/2025 at 8:55 PM, sskwhiteshadow said: So if i signout and put in the URL and sign in without emby connect it seems to work. BUT if i use my emby connect account it keeps running into the issue. Weird that if i use emby connect account it keeps running into this issue. Hi. Does your Emby server dashboard show the correct remote address?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now