Fire playback to emby behind proxy failing

[egandt 3]

Fire playback to emby behind proxy failing, I see two possible issues. 

First is the attempt to use: /emby/embywebsocket and second the HttpServer error.  Playback from a web-browser and Android app are fine, but from the Fire get this:

	2018-09-05 13:17:38.550 Info HttpServer: HTTP POST http://10.120.25.62:8096/emby/Items/44013159ee679187ef0f15b9cb13a14d/PlaybackInfo?format=json. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTT Build/LVY48F)
2018-09-05 13:17:38.554 Error HttpServer: Error processing request
	*** Error Report ***
	Version: 3.5.2.0
	Command line: /system/EmbyServer.dll -programdata /config -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3
	Operating system: Unix 4.15.0.30
	64-Bit OS: True
	64-Bit Process: True
	User Interactive: True
	Processor count: 8
	Program data path: /config
	Application directory: /system
	Error HttpServer: Error processing request
	Parameter name: id
	   at Emby.Server.Implementations.Library.UserManager.GetUserById(Guid id)
	   at Emby.Server.MediaEncoding.Api.MediaInfoService.GetPlaybackInfo(GetPostedPlaybackInfo request)
	   at Emby.Server.MediaEncoding.Api.MediaInfoService.Post(GetPostedPlaybackInfo request)
	   at Emby.Server.Implementations.Services.ServiceExecGeneral.GetTaskResult(Task task)
	   at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost appHost, IRequest httpReq, IResponse httpRes, ILogger logger, String operationName, CancellationToken cancellationToken)
	   at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IHttpRequest httpReq, String urlString, String host, String localPath, CancellationToken cancellationToken)
	System.ArgumentNullException
	   at Emby.Server.Implementations.Library.UserManager.GetUserById(Guid id)
	   at Emby.Server.MediaEncoding.Api.MediaInfoService.GetPlaybackInfo(GetPostedPlaybackInfo request)
	   at Emby.Server.MediaEncoding.Api.MediaInfoService.Post(GetPostedPlaybackInfo request)
	   at Emby.Server.Implementations.Services.ServiceExecGeneral.GetTaskResult(Task task)
	   at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost appHost, IRequest httpReq, IResponse httpRes, ILogger logger, String operationName, CancellationToken cancellationToken)
	   at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IHttpRequest httpReq, String urlString, String host, String localPath, CancellationToken cancellationToken)
	
2018-09-05 13:17:38.554 Info HttpServer: HTTP Response 400 to 123.123.231.123. Time: 4ms. http://10.120.25.62:8096/emby/Items/44013159ee679187ef0f15b9cb13a14d/PlaybackInfo?format=json 
2018-09-05 13:17:38.812 Info HttpServer: HTTP GET http://10.120.25.62:8096/emby/embywebsocket?deviceId=be65a32d51fa39b1. UserAgent: 
2018-09-05 13:17:38.812 Error HttpServer: Could not find handler for /emby/embywebsocket
2018-09-05 13:17:38.812 Info HttpServer: HTTP Response 404 to 123.123.231.123. Time: 0ms. http://10.120.25.62:8096/emby/embywebsocket?deviceId=be65a32d51fa39b1 
2018-09-05 13:17:38.957 Info HttpServer: HTTP GET http://10.120.25.62:8096/emby/Items/93c8d024c6b8c4d040d1ec9a763aae45/Images/Primary?Accept=webp&MaxHeight=280&EnableImageEnhancers=true&Tag=bd88206d385443a1c431456aae386801. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTT Build/LVY48F)
2018-09-05 13:17:38.960 Info HttpServer: HTTP Response 200 to 123.123.231.123. Time: 2ms. http://10.120.25.62:8096/emby/Items/93c8d024c6b8c4d040d1ec9a763aae45/Images/Primary?Accept=webp&MaxHeight=280&EnableImageEnhancers=true&Tag=bd88206d385443a1c431456aae386801 
2018-09-05 13:17:38.983 Info HttpServer: HTTP GET http://10.120.25.62:8096/emby/Items/c597e896089086d7038480be1f7bf3ff/Images/Primary?Accept=webp&MaxHeight=280&EnableImageEnhancers=true&Tag=0183324b0932fadf59c5672f3f95ee8e. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTT Build/LVY48F)
2018-09-05 13:17:38.985 Info HttpServer: HTTP Response 200 to 123.123.231.123. Time: 2ms. http://10.120.25.62:8096/emby/Items/c597e896089086d7038480be1f7bf3ff/Images/Primary?Accept=webp&MaxHeight=280&EnableImageEnhancers=true&Tag=0183324b0932fadf59c5672f3f95ee8e 
2018-09-05 13:17:39.169 Info HttpServer: HTTP GET http://10.120.25.62:8096/emby/embywebsocket?deviceId=be65a32d51fa39b1. UserAgent: 
2018-09-05 13:17:39.169 Error HttpServer: Could not find handler for /emby/embywebsocket
2018-09-05 13:17:39.169 Info HttpServer: HTTP Response 404 to 123.123.231.123. Time: 0ms. http://10.120.25.62:8096/emby/embywebsocket?deviceId=be65a32d51fa39b1 
2018-09-05 13:17:39.374 Info HttpServer: HTTP GET http://10.120.25.62:8096/emby/Items/ab855a1b5e9a9fa1fbd0d4a59febc53b/Images/Primary?Accept=webp&MaxHeight=280&EnableImageEnhancers=true&Tag=d3ed297004ce48eb63e5354eb1484761. UserAgent: Dalvik/2.1.0 (Linux; U; Android 5.1.1; AFTT Build/LVY48F)
2018-09-05 13:17:39.376 Info HttpServer: HTTP Response 200 to 123.123.231.123. Time: 2ms. http://10.120.25.62:8096/emby/Items/ab855a1b5e9a9fa1fbd0d4a59febc53b/Images/Primary?Accept=webp&MaxHeight=280&EnableImageEnhancers=true&Tag=d3ed297004ce48eb63e5354eb1484761 
2018-09-05 13:17:39.728 Info HttpServer: HTTP GET http://10.120.25.62:8096/emby/embywebsocket?deviceId=be65a32d51fa39b1. UserAgent: 
2018-09-05 13:17:39.728 Error HttpServer: Could not find handler for /emby/embywebsocket
2018-09-05 13:17:39.728 Info HttpServer: HTTP Response 404 to 123.123.231.123. Time: 0ms. http://10.120.25.62:8096/emby/embywebsocket?deviceId=be65a32d51fa39b1 
2018-09-05 13:17:44.870 Info HttpServer: HTTP GET http://10.120.25.62:8096/emby/embywebsocket?deviceId=be65a32d51fa39b1. UserAgent: 
2018-09-05 13:17:44.870 Error HttpServer: Could not find handler for /emby/embywebsocket

I'm running Emby locally using the latest docker image (and I just downloaded the Emby application to the Fire today.

 

I have proxy setup looking like:

        RewriteEngine on
        RewriteRule ^/emby(.*)    http://10.120.25.62:8096/emby$1 [proxy]
        RewriteRule ^/emby http://10.120.25.62:8096 [proxy]
        RewriteRule ^/embywebsocket(.*)    http://10.120.25.62:8096/embywebsocket$1 [proxy]
        RewriteRule ^/embywebsocket http://10.120.25.62:8096 [proxy]

        # web browser requires this
        <Location />
                ProxyPass           http://10.120.25.62:8096/
                ProxyPassReverse    http://10.120.25.62:8096/
        </Location>

        # web browser and android require this
        <Location /emby>
                ProxyPass           http://10.120.25.62:8096/emby
                ProxyPassReverse    http://10.120.25.62:8096/emby
        </Location>
  
        # Fire seems to require this, not need for web or android
        <Location /embywebsocket>
                ProxyPass               http://10.120.25.62:8096/embywebsocket
                ProxyPassReverse        http://10.120.25.62:8096/embywebsocket
        </Location>

This as I said works for both Android and Web Browsers, but not the Fire.

 

I also tried adding in addition:

        RewriteRule ^/emby/embywebsocket(.*)    http://10.120.25.62:8096/embywebsocket$1 [proxy]
        RewriteRule ^/emby/embywebsocket http://10.120.25.62:8096 [proxy]

In order to redirect /emby/embywebsocket to /embywebsocket without any success.

 

I personally think the the more likely problem is "Error HttpServer: Error processing request" when going from the Fire, but I'm

 

Suggestions?

ERIC

 

[ebr 14947]

We saw something similar recently.  I believe the proxy is stripping out a lot of the data that is sent with that POST command.  The other apps "work" because, without that data, they just make the decision to transcode to a very compatible format.  The fire app happens to include an important item (the user ID) in the post data and, when its not there, nothing can continue.

[egandt 3]

Thanks, seeing what can be done to forward requests properly.

 

ERIC