App not loading

[GiGo 108]

I couldn't recreate the issue again today for some reason, it worked first time which is great, however, I have been having an issue with the Roku not loading Emby on the first attempt, I have no idea why it is doing it, normally it just starts after 2 or 3 restarts but today it 4 or 5.

I have attached the log if you wouldn't mind looking, I enabled debug also.

.3 is my server and .146 is my Roku if that helps.

Thanks!

embyserver.txt

[ebr 16169]

7 hours ago, GiGo said:

I have been having an issue with the Roku not loading Emby

Hi. Exactly what happens?

[GiGo 108]

On 11/01/2022 at 14:32, ebr said:

Hi. Exactly what happens?

Sorry mate, this should have been a reply to the other thread I createrd, not sure how this got it's own thread?; 

 

[ebr 16169]

Hi. I split it to a new topic because you were reporting a completely different issue. 

Can you please explain what 'not loading" means?  What exactly happens? 

Thanks.

[Baenwort 118]

So for the last two days the Roku Emby app and Emby Beta app do not load when selected from the Roku launch screen. The screen changes like it is starting the load and then it drops back to the main screen.

When I use the old Neon app I am still able to reach my local Emby server and play stuff.

Using a Roku 4 Ultra with latest system update.

Only thing that changed around the same time was my LetsEncrypt certificate renewed but that shouldn't affect local play back?

[ebr 16169]

1 hour ago, Baenwort said:

Only thing that changed around the same time was my LetsEncrypt certificate renewed

That sounds suspicious.  Can you confirm how  you are connecting to your server?

[Baenwort 118]

1 hour ago, ebr said:

That sounds suspicious.  Can you confirm how  you are connecting to your server?

Roku 4 Ultra via wired Cat5e to a Switch that is also the one that the TrueNAS server running Emby is on.

Android + iOS phones via WAN work fine. Local Windows 10 PC works fine. Same Roku 4 Ultra using the old Neon Blue Emby app works also.

Just the regular Emby App and the Emby Beta App doesn't work. (currently running 4.6.7.0 stable on the server).

I'm able to stream from the Emby server to a local Chromecast Audio via the Emby website on a Windows 10 PC using Vivaldi. 

I've tried rebooting the Roku.

[Luke 42077]

Have you tried clearing app data?

[ebr 16169]

5 hours ago, Luke said:

Have you tried clearing app data?

I think the only way to do that on Roku is to uninstall and re-install but that may be a good thing to try.

@Baenwort by "how you are connecting" I meant from an address standpoint and is it http or https?

[Baenwort 118]

So on the webbrowsers I am using HTTPS even on the local LAN.

As to the Roku App? Other than uninstalling and reinstalling the app I am uncertain how to validate the connection method. Can you provide direction?

I was able to restart the server this morning before anyone started streaming anything and here are some logs.  I accessed it from the Roku in the order of "stable app", 'beta app', 'stable app', Neon app (then streamed a recording for a bit), then tried the 'stable app again.

hardware_detection-63779736833.txtffmpeg-transcode-40c0bc17-70a3-4b67-b694-dea18424a96f_1.txtembyserver.txt

[ebr 16169]

Hi.  I'm pretty sure the only reference in your server log to a Roku is from the BN app (and it is using plain http).  That tells me the other one is never getting there. Most likely due to the cert.  However, the app should not just be closing in that instance. 

Can you try uninstalling and re-installing the channel?

[Baenwort 118]

Sure, it does open as far as displaying the Emby logo.

I've never had this occur before and the LetsEncrypt cert rotates every 90 days so we've been through quite a few rounds of this without problem before. 

[Baenwort 118]

1 hour ago, ebr said:

Hi.  I'm pretty sure the only reference in your server log to a Roku is from the BN app (and it is using plain http).  That tells me the other one is never getting there. Most likely due to the cert.  However, the app should not just be closing in that instance. 

Can you try uninstalling and re-installing the channel?

Tried uninstalling and reinstalling and no change in behaviour. The screen goes black and shows the Emby logo for a brief second before returning to the homescreen.

Do you want me to restart the server and make sure the only activity is startup of the stable Roku app?

[Baenwort 118]

The cert shows valid for the web browser. It is pulled by another device but includes the emby sub-domain and is valid for it.

Here is a fresh start with only access from Roku 'stable' app. embyserver.txthardware_detection-63779744116.txt last thing I did before going to pull the logs was attempt to connect.

 

The Roku's IP is 192.168.1.209 and I can ping it from the Emby Jail.

Edited February 6, 2022 by Baenwort

[Baenwort 118]

Is there any debugging or logging I can pull from the Roku? 

[speechles 2055]

@Baenwort It might make it faster if we could actually reproduce the error. Any chance you can add me (speechles) to your server for testing? If I can see the error in the Roku debug console (app crash) I can figure out what is happening. That will take the load off you as far as chasing the problem. Just PM me and let me know how to login and I can fix it. We are here to help. 

 

Also.. The BNN app will be disappearing on Febuary 24th, 2022. It will not be available as a private channel. It will be deleted from your Roku. This is beyond the control of Emby or myself. Unofficial private channels are leaving Roku forever. They will now only allow temporary Beta channels which can exist for 30 days. Keep this in mind as we progress into 2022. Below is the reference from Roku.

 

Here is that "View Online" link too: https://x.email1.roku.com/ats/msg.aspx?sg1=934cba917ad6bf79ca20002cea349ffed32aebfa9054a6aa80620377c826b26a

 

Edited February 6, 2022 by speechles

[Baenwort 118]

So I was able to get the Emby 'Stable" app to let me enter in server details. I had to uninstall both the "stable' and the 'beta' app at the same time then reinstall the 'stable' app before it would go to the host entry screen.

I suspect this means the 'stable' and the 'beta' app are sharing cache or log in details?

Once there I could use the http port (8096) and connect to the server host 'emby.adams.fun' but when I changed the host to 'https://emby.adams.fun' and the port to 8265 (my https port) I got error code (-60) when I had https:// at the start of the host name and error (-40) when I forgot to include that.

Edited February 6, 2022 by Baenwort

[speechles 2055]

3 minutes ago, Baenwort said:

I suspect this means the 'stable' and the 'beta' app are sharing cache or log in details?

The Roku has a registry which stores the information per developer ID key number. Rather than juggle keys when updating apps there is a single key that all Emby Roku apps update VIA. This is to make it easier on everyone all the way around. Roku has also recently started to enforce that users are not creating multiple application ID to go over the only 5 applications per developer rule. Roku is cracking down as of February 24th. Keep that in mind.

[Baenwort 118]

4 minutes ago, speechles said:

The Roku has a registry which stores the information per developer ID key number. Rather than juggle keys when updating apps there is a single key that all Emby Roku apps update VIA. This is to make it easier on everyone all the way around. Roku has also recently started to enforce that users are not creating multiple application ID to go over the only 5 applications per developer rule. Roku is cracking down as of February 24th. Keep that in mind.

I think the Beta channel limitation on number of users will be a larger problem as I sometimes switch from stable to beta server chains when bugs crop up. As I recall you need to use the 'beta' app when running the beta server versions. I presume Emby has some method to allow the running of the 'beta' app along with the beta server versions that doesn't need me to install and configure a new 'beta' app every 120 days.

 

 from https://blog.roku.com/developer/beta-channels#Rokusunsettingnoncertifiedchannels-Migratinganon-certifiedchanneltoapublicchannel

I don't see how the 5 application per developer rule will impact Emby or my use of it as I only run the two "Emby" apps and the Blue Neon app (my son is autistic and doesn't handle change well. We keep the BN app around as the interface matches what Emby looked like when he started being allowed to use the TV).

[ebr 16169]

19 minutes ago, Baenwort said:

Once there I could use the http port (8096) and connect to the server host 'emby.adams.fun' but when I changed the host to 'https://emby.adams.fun' and the port to 8265 (my https port) I got error code (-60) when I had https:// at the start of the host name and error (-40) when I forgot to include that.

Okay, so that tells me it is a certificate problem.  Let's Encrypt certs had a root (or maybe intermediate) expire late last year and that caused a lot of issues with older and more strict devices.

[Baenwort 118]

5 minutes ago, ebr said:

Okay, so that tells me it is a certificate problem.  Let's Encrypt certs had a root (or maybe intermediate) expire late last year and that caused a lot of issues with older and more strict devices.

The prior cert that was working was issued in November of 2021. This cert I'm under now was issued February 3rd 2022. Is the prior cert in that window?

[ebr 16169]

I really am not sure.  That is about the time that these issues started cropping up but Roku may have also changed something in the meantime.

[pwhodges 2012]

Another recent Let's Encrypt issue has been some faulty certificates which were issued recently (I don't know the exact time-scale, nor the number of bad certificates involved - I got two warning notifications from them while using a couple of dozen certificates).  These certificates were revoked on 31 Jan, and depending on the programming of the client using them, may have stopped working on that date.  These certificates needed reissuing, but to the best of my knowledge, Caddy (v2.4.2 and up) is the only client which will have within three days requested updated certificates automatically as a result of the revocation.

Paul