Unable to stream externally since upgrading

[chinswain 11]

Hi,

Since upgrading emby I am unable to stream any media (Live TV, movies and tv shows) outside of my network.
I get "Playback Error, no compatible streams are currently available)

I have a Synology DS918+ (DSM 7.1) running Emby 4.7.9.0

I have a DNS entry setup for the Synology, DNS via Google and secured via SSL from Cloudflare.

Emby is reverse proxied (Login Portal, Advanced, Reverse Proxy) from https://emby.mywebsite/co.uk to http://192.168.86.40:8096

Can you see anything in the attached logs?

embyserver.txt ffmpeg-transcode-6c39b063-e1e6-44e5-9238-76f2ef35c647_1.txt

[Luke 42078]

HI there, are you able to play inside your local network?

[chinswain 11]

Yes, if I hit it directly (http://192.168.86.40:8096)

I noticed in the ffmpeg log it's switching to http (http://emby.mywebsite.co.uk/***) rather than https - is there a setting for that?

Edited November 14, 2022 by chinswain

[Luke 42078]

5 hours ago, chinswain said:

Yes, if I hit it directly (http://192.168.86.40:8096)

I noticed in the ffmpeg log it's switching to http (http://emby.mywebsite.co.uk/***) rather than https - is there a setting for that?

Does your server dashboard display the correct remote address that you want it to use?

[chinswain 11]

It shows my external IP http://xxx.xxx.xxx.xxx:8096/ 

However it's reverse proxied from https://emby.mywebsite.co.uk to http://internal-IP:8086 so I don't this it matters as emby is not exposed directly.

Did anything change after 4.6 that could explain the http instead of https in the logs?

[Happy2Play 9780]

Unrelated but you need to adjust your iNotify.

The configured user limit (8192) on the number of inotify watches has been reached, or the operating system failed to allocate a required resource.

 

[Luke 42078]

14 minutes ago, chinswain said:

It shows my external IP http://xxx.xxx.xxx.xxx:8096/ 

However it's reverse proxied from https://emby.mywebsite.co.uk to http://internal-IP:8086 so I don't this it matters as emby is not exposed directly.

Did anything change after 4.6 that could explain the http instead of https in the logs?

I would make sure to configure the wan address in Emby Server network settings, as well as the public facing port(s) and the SSL option. This will help make the server aware of what the remote address should actually be.

Once you get it to display the correct remote address on the server dashboard, then you should see a different result.

[chinswain 11]

I managed to resolve this - my website was running via Cloudflare who now block video streaming on their free plan.