SSL kills images on Firestick

[JuJuJurassic 49]

I finally enabled SSL,  and great, tested it on my laptop, using a different network and it worked perfectly. Marvellous.

A couple of family members connect via Emby on their firesticks, I use one on the TV downstairs. They rang me to say there were no images. I then moved my TV's Firestick to https, and there were no images on my Firestick. As you can see below.

It's not bandwidth, as it's local and still doing it. I uninstalled the app and re-installed it to see if there was an update, but the problem persisted, i moved it to http instead of https and it works fine.

Any ideas? I really want to go to SSL for remote connections.

Thanks

 

embyserver (17).txt embyserver (16).txt

[Q-Droid 989]

The devs might want to see app logs from the firesticks.

Any reverse proxy or traffic filtering in the setup?

[JuJuJurassic 49]

Thanks Q-droid, 

It's an open Lan, no filtering

Could you advise me how do I get the log from the Emby app on the.firestick?

Thanks

Juju

[ebr 16174]

Hi.  SSL shouldn't be an issue but is it possible you are also connecting with IPv6?

[Q-Droid 989]

4 hours ago, JuJuJurassic said:

Thanks Q-droid, 

It's an open Lan, no filtering

Could you advise me how do I get the log from the Emby app on the.firestick?

Thanks

Juju

It might vary by app but on Android I find it under App Settings -> Logs -> Settings to enable app logging. Requires a restart then you can recreate the problem and send the logs. 

I don't really know if there's a preferred way by the devs to share app logs.

 

[justinrh 260]

12 hours ago, JuJuJurassic said:

I then moved my TV's Firestick to https,

Just for my info, how did you do this?

[justinrh 260]

Can you disable IPv6 on your router and/or the server?

The symptom sounds like the image links are not HTTPS.

Emby apps need an console (that can show errors and traffic) like browsers have 

Edited February 10, 2024 by justinrh

[JuJuJurassic 49]

15 hours ago, ebr said:

Hi.  SSL shouldn't be an issue but is it possible you are also connecting with IPv6?

Hi ebr,

It's all IP4.

It's connecting to an Ubuntu box, I've attached the .yaml configuration file, use notepad to view it. The network 193.37.226.x is "owned" by me and used internally, so treat it as a private network. 193.37.226.250 is Emby's local address within the house. The 10.1.x.x network goes to the internet router, the other networks go to the san.

Thanks

00-installer-config.yaml

[JuJuJurassic 49]

8 hours ago, justinrh said:

Just for my info, how did you do this?

Hi Justinrh

I deleted the emby app, re installed it, and added a server manually to http rather than https

I don't use emby connect for anything.

Thanks

any suggestions?

[JuJuJurassic 49]

8 hours ago, justinrh said:

Can you disable IPv6 on your router and/or the server?

The symptom sounds like the image links are not HTTPS.

Emby apps need an console (that can show errors and traffic) like browsers have 

Hi Justinrh,

There is no IP6 on the network.

It works fine from my laptop over https, the images are there, so they can be delivered over https

Any suggestions?

Thanks

[Q-Droid 989]

You don't quite have an open LAN, it's a segmented network.

Are the laptop and firestick on the same subnet when you're testing HTTPS? Can you clear the cache on the laptop before testing HTTPS? Is the laptop running browser or ET app?

[ebr 16174]

Can you please produce that screen with the missing images and then follow the instructions to send a log from the app?

 

[justinrh 260]

12 hours ago, JuJuJurassic said:

I deleted the emby app, re installed it, and added a server manually to http rather than https

Thanks.  So you are connecting to your public IP via HTTPS from within the LAN?  I saw "193.37.226.250 is Emby's local address within the house."  I just wanted to make sure I understood what you were connecting to.

[rbjtech 5284]

You appear to have a very strange network setup .. 

193.37.226.250 - private use or not, you should not be using public address space for private use - especially if it is routed to the internet.   I would hope your router is dropping the packets and not attempting to route them, upstream routers certainly will be.

Do yourself a favor and configure the network as per IPv4 policy - and use RFC1918 addressing.   using 10.x.x.x/24 is ok, but even that is meant for large(huge) private networks - do you really need 16 Million local Ip addresses ?    192.168.0.0/16 gives you 65 Thousand, suitable for home and even medium enterprise use.

Using https 'locally' will ultimately need you to have either an externally approved ca (certificate authority) or you can be your own ca if that is an option (unlikely) - either way, trying to use an unorthodox/illegal network config to get this to work - is just making pain for yourself.

[JuJuJurassic 49]

Hi All,

So I haven't changed anything and today it all works perfectly. The server rebooted at the Hardware level, but it did that twice before hand too. I checked the let's Encrypt certificate, and that's not renewed overnight.

So I'm happy, but what about the next person who has this? I know there's an IP6 problem, but I can't offer any suggestions on why it now works. So if anyone reading this has it again, the only thing that happened was 3 power off reboots.

Thanks for all the help

juju