Jump to content

Got a 401 while attempting to read from my TV Mediacenter


gdebure
Go to solution Solved by gdebure,

Recommended Posts

gdebure

Hello there,

 

Since a few days, I get an error while trying to read media from Emby (running on a Synology DS218J) on my TV mediacenter. The mediacenter is a builtin application that is provided by my Internet Service Provider (SFR, a french ISP). It sees correctly my Emby server through DLNA, I can browse my collection, but whwen trying to read I get an error on the TV screen. In the log files in Emby, I can see the following error :

2019-08-05 22:00:08.434 Info HttpServer: HTTP Response 200 to 192.168.1.75. Time: 48ms. http://192.168.1.63:8096/Items/12483/Images/Primary/0/0a158b2a6661d6c9c38f4e8a0a6a12bf/jpg/48/48/0/0
2019-08-05 22:00:08.862 Info HttpServer: HTTP POST http://192.168.1.63:8096/dlna/6cc5b99f68b544a08d8ef38896fd82d6/contentdirectory/control. UserAgent: Linux/2.6.23.17_stm23_0125dorade00 UPnP/1.0 DLNADOC/1.50 Portable SDK for UPnP devices/1.6.18
2019-08-05 22:00:08.894 Info HttpServer: HTTP Response 200 to 192.168.1.75. Time: 32ms. http://192.168.1.63:8096/dlna/6cc5b99f68b544a08d8ef38896fd82d6/contentdirectory/control
2019-08-05 22:00:09.106 Info HttpServer: HTTP POST http://192.168.1.63:8096/dlna/6cc5b99f68b544a08d8ef38896fd82d6/contentdirectory/control. UserAgent: Linux/2.6.23.17_stm23_0125dorade00 UPnP/1.0 DLNADOC/1.50 Portable SDK for UPnP devices/1.6.18
2019-08-05 22:00:09.118 Info HttpServer: HTTP Response 200 to 192.168.1.75. Time: 13ms. http://192.168.1.63:8096/dlna/6cc5b99f68b544a08d8ef38896fd82d6/contentdirectory/control
2019-08-05 22:00:10.819 Info HttpServer: HTTP POST http://192.168.1.63:8096/dlna/6cc5b99f68b544a08d8ef38896fd82d6/contentdirectory/control. UserAgent: Linux/2.6.23.17_stm23_0125dorade00 UPnP/1.0 DLNADOC/1.50 Portable SDK for UPnP devices/1.6.18
2019-08-05 22:00:10.831 Info HttpServer: HTTP Response 200 to 192.168.1.75. Time: 12ms. http://192.168.1.63:8096/dlna/6cc5b99f68b544a08d8ef38896fd82d6/contentdirectory/control
2019-08-05 22:00:11.383 Info HttpServer: HTTP POST http://192.168.1.63:8096/dlna/6cc5b99f68b544a08d8ef38896fd82d6/contentdirectory/control. UserAgent: Linux/2.6.23.17_stm23_0125dorade00 UPnP/1.0 DLNADOC/1.50 Portable SDK for UPnP devices/1.6.18
2019-08-05 22:00:11.391 Info HttpServer: HTTP Response 200 to 192.168.1.75. Time: 8ms. http://192.168.1.63:8096/dlna/6cc5b99f68b544a08d8ef38896fd82d6/contentdirectory/control
2019-08-05 22:00:11.508 Info HttpServer: HTTP GET http://192.168.1.63:8096/videos/12483/stream.mkv?DeviceId=04053a80a241f24c4aab6c52edc36179&MediaSourceId=caad708186370efaf023b0ef512a78d1&Static=true&PlaySessionId=a2fc4f5f26cf76a1bd276e3a6f0cf9b2. User-Agent=Lavf54.30.100, Accept=*/*, Range=bytes=0-, Connection=close, Host=192.168.1.63:8096
2019-08-05 22:00:11.574 Error HttpServer: Access token is invalid or expired.
2019-08-05 22:00:11.581 Info HttpServer: HTTP Response 401 to 192.168.1.75. Time: 73ms. http://192.168.1.63:8096/videos/12483/stream.mkv?DeviceId=04053a80a241f24c4aab6c52edc36179&MediaSourceId=caad708186370efaf023b0ef512a78d1&Static=true&PlaySessionId=a2fc4f5f26cf76a1bd276e3a6f0cf9b2

I attach the full log in case it is useful.

 

Is there anything I can do server side to fix it ? There is no option on the mediacenter itself to request a new access token...

 

Thanks :)

Edited by gdebure
Link to comment
Share on other sites

gdebure

Not really... I'm not using this too often. I'm quite sure it was working beginning of July, but no guarantees... Is there some kind of HTTP request I could POST or PUT on the server to force devices to request a new access token ?

Link to comment
Share on other sites

gdebure

Oh hold on, there is something new and probably easier to investigate : VLC has the same error from a PC.

 

Votre média d'entrée ne peut être ouvert:

VLC ne peut pas ouvrir « http://192.168.1.63:8096/videos/3013/stream.avi?DeviceId=ffd1dab382f5ae23e7e4334952e48ce4&MediaSourceId=c2b741eb595a3b48d8eab48633013dd6&Static=true&PlaySessionId=a715a798829f2a6cc169f26f93b60515 ».Vérifier les messages du journal pour plus de détails.

 

Now, this was definitely working a few days ago, and what changed in between is that I've now configured Kodi (on the same PC as the one with the VLC error, plus another PC) to access Emby.

Link to comment
Share on other sites

  • Solution
gdebure

OK, I got it fixed... sorry for the unnecessary noise. It was a mistake in the local network configuration. Everything is back to normal.

  • Like 1
Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...