Jump to content
Sign in to follow this  
jmbond04

30 seconds to 15 minutes loading time on Fire TV

Recommended Posts

jmbond04

I'm having an issue where it's taking up to 10 minutes to connect to the Emby server. It takes about 30 seconds to go through the loading screen with the circle. Then it takes anywhere from a few seconds to ~10 minutes for it to actually load My Media and the other sections. 

 

A couple things to note.

 

1. On the same network I can connect using a Galaxy S10 phone with the Emby app and on a windows pc with Emby Theater in 15 seconds or less.

2. The server is running behind a nginx reverse proxy but I don't think this is the problem since I only see this issue with Fire Sticks on one network.

3. I am having this issue on both a Fire Stick Gen 2 and a Fire Stick 4k.

4. I have attached one log of it taking about 2.5 minutes. Basically I reset the log before starting the app and downloaded right after it finished.

 

Does anyone have any ideas on what could be causing this and how to fix it.?

 

 

Edit: Log should now be attached.

fire_tv_start_embyserver.txt

Edited by jmbond04

Share this post


Link to post
Share on other sites
ebr

Hi.  There is no log attached.  Did you forget to hit the last button?

 

I suspect the reverse proxy though.  Can you test without it?

Share this post


Link to post
Share on other sites
jmbond04

Hi.  There is no log attached.  Did you forget to hit the last button?

 

I suspect the reverse proxy though.  Can you test without it?

 

I tried this again using https through port 8920. This time it took about 6 minutes with the same issue as described before.

 

It doesn't look like the reverse proxy is the issue here.

fire_tv_https__no_proxy_embyserver.txt

Share this post


Link to post
Share on other sites
sephrat

Sounds like a connectivity issue.

Is your Fire TV connected to the same Wifi network as the phone you test your connection with? Some routers have 2 different spots for regular and 5G (ac). Although 5G is usually better, regular Wifi may have better performance depending on the obstacles between your device and your router.

Share this post


Link to post
Share on other sites
Luke

Have you compared your nginx settings to @@pir8radio ?

Share this post


Link to post
Share on other sites
jmbond04

Sounds like a connectivity issue.

Is your Fire TV connected to the same Wifi network as the phone you test your connection with? Some routers have 2 different spots for regular and 5G (ac). Although 5G is usually better, regular Wifi may have better performance depending on the obstacles between your device and your router.

 

All devices are using the same wifi network. I have tested the fire sticks on both the 2.4 and 5 bands with no difference.

Edited by jmbond04

Share this post


Link to post
Share on other sites
jmbond04

Have you compared your nginx settings to @@pir8radio ?

 

When I was originally setting my reverse proxy up a couple years ago I compared with this forum to get it working.

 

With the second test using https directly to Emby I would think the reverse proxy is not causing this issue. 

Share this post


Link to post
Share on other sites
Luke

How does the web app compare?

Share this post


Link to post
Share on other sites
jmbond04

How does the web app compare?

 

Just checked and the web app works great through both Firefox and silk on the Fire Stick. The navigation is a lot more annoying then the actual app since it makes you use the cursor. 

Share this post


Link to post
Share on other sites
jmbond04

All the responses I see in there are quite fast.

 

Can you try sending a log from the app?

 

I enabled debug and selected "Send Logs" after it loaded using the app. Still took a while to load.

 

Logs were sent between 3:45 and 3:50pm Eastern

Emby User Name displayed: Glenn and Karen

 

Let me know what you find or if you need any more info.

Share this post


Link to post
Share on other sites
ebr

Shoot - this is an old Fire TV which puts no timestamps in the logs so I can't see how long anything is taking.  I do, however, see several timeouts on the websocket connections.

 

Also, it appears to be a remote connection.  How did you log in?

Share this post


Link to post
Share on other sites
jmbond04

Shoot - this is an old Fire TV which puts no timestamps in the logs so I can't see how long anything is taking.  I do, however, see several timeouts on the websocket connections.

 

Also, it appears to be a remote connection.  How did you log in?

 

Yeah that is a Fire Stick Gen 2 I believe. It should still be remote connecting to the server through ip address and port 8920 (https). It's still set like this to bypass the reverse proxy but I normally log in using Emby Connect and go through port 8096.

 

Any idea what would be causing the websocket timeouts?

Share this post


Link to post
Share on other sites
ebr

You said these issues were all on a local wifi network but that is not the case.  You are going out through the internet to your server so it can definitely just be a network bottleneck.

 

The auto bitrate test returned an extremely low value also indicating slow network response.

Share this post


Link to post
Share on other sites
jmbond04

You said these issues were all on a local wifi network but that is not the case.  You are going out through the internet to your server so it can definitely just be a network bottleneck.

 

The auto bitrate test returned an extremely low value also indicating slow network response.

Sorry I meant all the client devices are on the same network. The server is at a different location.

 

I guess the issue I have with this is I have 3 Fire Sticks that are having issues with just the Emby app. The Web client has no issues connecting through Firefox on the same device. I also have a phone and a windows computer that have no issues connecting through there respective apps. All of the clients are on the same wifi network and band.

 

The Client's network is ~200 Mbps Down/ ~10 Mbps Up

The Server's network is ~200 Mbps Down/ ~20 Mbps Up

 

This is plenty of speed on both sides to load faster than minutes in the Fire TV App.

Share this post


Link to post
Share on other sites
Luke

Have you tried lowering the in app quality setting?

Share this post


Link to post
Share on other sites
jmbond04

Have you tried lowering the in app quality setting?

Quality settings for getting the loading screen up? It's not aware of any settings that would help with that.

It's taking up to like 15 minutes from opening the app to my media being loaded. Once the app is actually loaded playing videos seem to work quite a bit better.

Share this post


Link to post
Share on other sites
Luke

Ok sorry I thought this was when trying to play something.

Share this post


Link to post
Share on other sites
jmbond04

Ok sorry I thought this was when trying to play something.

Not problem, just trying to make sure my issue is clear.

Share this post


Link to post
Share on other sites
ebr

The Server's network is ~200 Mbps Down/ ~20 Mbps Up

 

Okay, so that means your connection to that server is limited to a max of 20Mb/s.  That isn't huge but should be fine for browsing.

 

Only thing I can think to do is put in some code in the app to add our own timestamps to the log for this old version of Android so that I can see how long some of these things are actually taking.  Other than the websocket time-outs there are no "errors" in the app side. My guess is just that things are responding very slowly and the auto bitrate test would indicate that as well.  It is coming up with 2Kb/s.

Share this post


Link to post
Share on other sites
jmbond04

Okay, so that means your connection to that server is limited to a max of 20Mb/s.  That isn't huge but should be fine for browsing.

 

Only thing I can think to do is put in some code in the app to add our own timestamps to the log for this old version of Android so that I can see how long some of these things are actually taking.  Other than the websocket time-outs there are no "errors" in the app side. My guess is just that things are responding very slowly and the auto bitrate test would indicate that as well.  It is coming up with 2Kb/s.

Guess I still don't understand why the app would be getting such a slow connection but the web app on the same device has no issues.

 

Is there a new version of the app I need to get to run a test with?

Share this post


Link to post
Share on other sites
ebr

Is there a new version of the app I need to get to run a test with?

 

Not yet.  I'm going to have to make modifications and release a new beta.

Share this post


Link to post
Share on other sites
pir8radio

I'm having an issue where it's taking up to 10 minutes to connect to the Emby server. It takes about 30 seconds to go through the loading screen with the circle. Then it takes anywhere from a few seconds to ~10 minutes for it to actually load My Media and the other sections. 

 

A couple things to note.

 

1. On the same network I can connect using a Galaxy S10 phone with the Emby app and on a windows pc with Emby Theater in 15 seconds or less.

2. The server is running behind a nginx reverse proxy but I don't think this is the problem since I only see this issue with Fire Sticks on one network.

3. I am having this issue on both a Fire Stick Gen 2 and a Fire Stick 4k.

4. I have attached one log of it taking about 2.5 minutes. Basically I reset the log before starting the app and downloaded right after it finished.

 

Does anyone have any ideas on what could be causing this and how to fix it.?

 

 

Edit: Log should now be attached.

 

 

Is your nginx forwarding to your emby server via "localhost" or 127.0.0.1  or some other way, Ip domain name? 

Try disabling IPV6 on the server. 

Do you use cloudflare or anything in front of your server?  Do you use a domain name or IP to your network? Post your config, I can also be a redirect issue in your config. 

Can also be a router config issue, depending on your setup.

Edited by pir8radio

Share this post


Link to post
Share on other sites
jmbond04

Is your nginx forwarding to your emby server via "localhost" or 127.0.0.1  or some other way, Ip domain name? 

Try disabling IPV6 on the server. 

Do you use cloudflare or anything in front of your server?  Do you use a domain name or IP to your network? Post your config, I can also be a redirect issue in your config. 

Can also be a router config issue, depending on your setup.

 

nginx is forwarding to 192.168.11.51 which is actually a container on the same network as the nginx server.

 

IPV6 is already disabled.

 

I use duck dns instead of direct ip to get to the server. Basically the path should be client -> duckdns (get ip) -> nginx -> emby.

The nginx for emby is as follows

server {
  # Emby
  server_name SERVER_URL;

  location / {
      proxy_pass http://192.168.11.51:8096;
                proxy_set_header        X-Real-IP               $remote_addr;
                proxy_set_header        X-Forwarded-For         $proxy_add_x_forwarded_for;
                proxy_set_header        Host                    $host;
                proxy_set_header        X-Forwarded-Proto       $remote_addr;
                proxy_set_header        X-Forwarded-Protocol    $scheme;
                proxy_redirect          off;

                proxy_http_version      1.1;
                proxy_set_header        Upgrade                 $http_upgrade;
                proxy_set_header        Connection              "upgrade";
                proxy_set_header        Range                   $http_range;  # Allows specific chunks of a file to be requested.
                proxy_set_header        If-Range                $http_if_range;  # Allows specific chunks of a file to be requested.
  }

    listen [::]:8096 ssl; # managed by Certbot
    listen 8096 ssl; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    client_max_body_size 10G;
    fastcgi_buffers 64 4k;
}

 

I think we have ruled out the reverse proxy being the issue when a did a direct https test to the emby server and still have the same issue. This makes the route client -> duckdns (get ip) -> emby.

 

Are there any specific configurations I should look for in the router on either the client or server side?

Share this post


Link to post
Share on other sites
jmbond04

Not yet.  I'm going to have to make modifications and release a new beta.

I just sent some logs using a First Stick 4k. That should be a newer device that hopefully gives you the time stamps you need.

 

Logs were sent between 7:50 and 8:00pm Eastern

Emby User Name displayed: James

 

Let me know if there is anything else you need.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×
×
  • Create New...