Understanding 404 responses in logs

[vdrover 62]

I just rotated my logs and see this message repeating:

'Info Server: http/1.1 Response 404 to host11. Time: 0ms. GET http://emby_remote_ip/embywebsocket?api_key=x_secret7_x&deviceId=REDACTED'

Any thoughts on what's generating this?

embyserver (3).txt

[Luke 42080]

HI, something is sending a request to a non-existing api url. Whatever it is, it doesn't look like it's coming from an Emby app.

Either that, or maybe you're using a reverse proxy and you've misconfigured it.

[vdrover 62]

I’m definitely using a reverse proxy. Any thoughts on how to troubleshoot? 

[Lessaj 467]

What's your config for the websocket proxy? I use apache.

Quote

ProxyPass "/embywebsocket" "wss://emby.my.domain:8920/embywebsocket" connectiontimeout=10 keepalive=on
ProxyPassReverse "/embywebsocket" "wss://emby.my.domain:8920/embywebsocket"

ProxyPass "/" "https://emby.my.domain:8920/" connectiontimeout=10 keepalive=on
ProxyPassReverse "/" "https://emby.my.domain:8920/"

 

[vdrover 62]

I'm using nginx proxy manager with these configs (attached).

[Lessaj 467]

Maybe enable websockets support? Sorry not familiar with this but seems like something that should be enabled. 

[vdrover 62]

This post helped me solve the 404 error just now.

But I am also getting this "info" message on every page  load of the web app:

Quote

Info Server: http/1.1 Response 204 to host8. Time: 1ms. POST http://host7:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=3A4659AB-B8ED-43D1-8870-2C6A4B8A178A&X-Emby-Client-Version=1.8.8 (2)&X-Emby-Token=x_secret5_x&reqformat=json

Should I be worried about this?

[Lessaj 467]

That's playing progress reported by an Apple TV, not related to the web app.

[vdrover 62]

Aaaah, sounds like it's normal then. thanks!