Playback Error No compatible streams iOS v. 16.6.1 on iPhone

[JohnsLibrary 8]

I have been getting this playback error whenever I try to play any video outside of my lan. Inside lan works perfectly. I tried connecting with http and https using the appropriate ports to no avail.

Attached is the log file

Thanks in advance for your help.

embyserver.txt

[Luke 39664]

Hi, what time did the problem occur?

[JohnsLibrary 8]

Between 3:25pm and 4:30pm eastern time.

[JohnsLibrary 8]

Oh, and also tried it around 5 to 615pm.

[JohnsLibrary 8]

Follow-up to my earlier posts about the playback error. It appears the my Comodo firewall was blocking a few ip address's that were not connected to my cell phone network

which is T-Mobile. The ip address's belong to cloudfront.net and hosted by Amazon AWS. I do not believe that these are related to T-Mobile routing since I have other services which I can

play from my iPhone with no issues.

So at this point, it looks as if the error message may be somewhat mis-leading as it uses the term "compatible streams", when in fact the stream is basically being blocked.

[Luke 39664]

Thanks for following up.

[JohnsLibrary 8]

As a follow-up to my previous follow-up (lol), I'm wondering if anyone has determined a list of ip addresses that are essential for Emby to function.

Since I've gotten past my previous issues with Comodo blocking outbound traffic from Emby, I have been paying closer attention to exactly where Emby is connecting.

So far I have logged a list of 5 ip's that must be un-blocked and are listed here along with hostname/whois result:

173.230.139.54 - Emby Media

104.237.62.213 - ipify.org

64.185.227.156 - ipify.org

18.238.61.98 - cloudfront.net

54.80.252.5 Amazon AWS

Now I have noticed that Emby Alerts is showing these messages:

Emby Guide Installation Failed -and-

Check for Plug-In Updates Failed

I have only one plug-in which is the Emby Guide Data.

Can anyone tell me what ip's are needed to fix the above errors?

[Luke 39664]

3 hours ago, JohnsLibrary said:

As a follow-up to my previous follow-up (lol), I'm wondering if anyone has determined a list of ip addresses that are essential for Emby to function.

Since I've gotten past my previous issues with Comodo blocking outbound traffic from Emby, I have been paying closer attention to exactly where Emby is connecting.

So far I have logged a list of 5 ip's that must be un-blocked and are listed here along with hostname/whois result:

173.230.139.54 - Emby Media

104.237.62.213 - ipify.org

64.185.227.156 - ipify.org

18.238.61.98 - cloudfront.net

54.80.252.5 Amazon AWS

Now I have noticed that Emby Alerts is showing these messages:

Emby Guide Installation Failed -and-

Check for Plug-In Updates Failed

I have only one plug-in which is the Emby Guide Data.

Can anyone tell me what ip's are needed to fix the above errors?

HI, plugin installs will come from mb3admin.com and embydata.com

[JohnsLibrary 8]

Are there any other reasons for Emby to connect to the group of IP's I'm seeing Comodo Firewall showing?

It appears that over time the list is growing and even with no visible logins or other activity initiated (such as live recording)

Emby Server is connecting to various Cloudfront and Amazon AWS IP addresses apart from mb3admin.com and embydata.com.

Call me paranoid, but it should be possible to lock down Emby and configure your firewall to allow only those sites necessary for the

program to work. I'm sure that choosing to show captions, trailers and other things need a place to go to get the information.

So, where is this coming from? What part of Emby is initiating these requests and where is the list?

Thanks.

[Luke 39664]

Quote

Emby Server is connecting to various Cloudfront and Amazon AWS IP addresses

Such as?

[JohnsLibrary 8]

see attached:

BTW: I did whois and blacklist check on most of these. As you can see in the attached, Comodo has blocked several new IPs

since I last looked.

Comodo Firewall Log.htm

[Luke 39664]

OK, to hunt down what those ip addresses correspond to, you may want to look at the server log at the same timestamp of what's in the comodo log.

Also It looks like you only have one plugin installed, emby guide data. Is that right? if you're using that, that will pulls guide data from gracenote api's.

[JohnsLibrary 8]

Ok, thanks. Hopefully, I can get to it tonight or tomorrow sometime.

 

[JohnsLibrary 8]

Ok, I took a look at both the Emby Log and Comodo Activity for just a two hour window. There are a bunch of connection errors (can't tell if they are related to ip's I'm blocking) I'm not sure what it's telling other than EmbyServer is making

connections to some sites like api.ipify.org (is this the gracenote api's you mentioned?) and blocking connections to a different ip with the same host name. There is also a connection to Amazon-AWS and a few to cloudflare.net.

However, as far as I can tell, they all relate to EmbyServer functions such as library updates and folder/episode graphics. 

Here is the list over a 24+ hour window, from my installation, of all the ip's I have seen:

54.80.252.5, 64.185.227.156, 18.238.61.98, 104.237.62.212, 104.237.62.213, 173.231.16.75, 173.231.16.77, 64.185.227.155, 140.82.114.6, 54.92.248.9(in), 54.83.69.249(in),

193.163.125.124 (in-census.internet-measurement--obvious port scan),104.21.95.214(embydata.com), 172.67.148.166(embydata.com), 173.230.139.54 (mb3admin.com)

The last 3 above you have indicated are known to be needed. All the above are outbound except for three ips (54.92.248.9, 54.83.69.249 Amazon AWS) and 193.163.125.124 which appears to be some kind of port scan for internet measurement.

Would there be any reason why there are inbound connections from Amazon static IP's on port 8096?

So, I'm back to the question of is there a list of ip/hostnames that Emby needs in order to work properly?

Emby_Debug.txt embyserver-63833443200.txt

[Luke 39664]

Quote

connections to some sites like api.ipify.org (is this the gracenote api's you mentioned?)

No, these are two separate things.

Quote

So, I'm back to the question of is there a list of ip/hostnames that Emby needs in order to work properly?

I believe I have given you all of the host names. I don't have all of the ip addresses behind those host names on hand.

[Luke 39664]

Quote

Would there be any reason why there are inbound connections from Amazon static IP's on port 8096?

I can't think of any, unless you have tried our Alexa features.

[cyruspy 5]

Hello!, what would be the final official list of destinations to allow?

I'm looking for alternatives to make emby use a HTTP proxy for outgoing connections, but firewall rules could work for the time being.

[JohnsLibrary 8]

I never did finish the list. Seemed that there were a lot of sites where the movie meta data was extracted from and the ip address's

changed so it was almost impossible to filter them via firewall and have Emby function normally. I would assume that you could

do what I did and try using something like Comodo Firewall and have it ask for every outbound connection for Emby and see

which ones are truly necessary.