Jump to content


Photo

30 seconds to 15 minutes loading time on Fire TV

slow load fire stick

  • Please log in to reply
39 replies to this topic

#21 jmbond04 OFFLINE  

jmbond04

    Advanced Member

  • Members
  • 31 posts
  • Local time: 12:51 PM

Posted 26 November 2019 - 12:06 PM

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?



#22 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 48159 posts
  • Local time: 12:51 PM

Posted 26 November 2019 - 12:59 PM

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.



#23 pir8radio OFFLINE  

pir8radio

    NGINX

  • Members
  • 2936 posts
  • Local time: 11:51 AM
  • LocationChicago

Posted 26 November 2019 - 06:35 PM

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, 26 November 2019 - 06:40 PM.


#24 jmbond04 OFFLINE  

jmbond04

    Advanced Member

  • Members
  • 31 posts
  • Local time: 12:51 PM

Posted 27 November 2019 - 04:22 AM

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?



#25 jmbond04 OFFLINE  

jmbond04

    Advanced Member

  • Members
  • 31 posts
  • Local time: 12:51 PM

Posted 28 November 2019 - 08:57 PM

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.



#26 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 48159 posts
  • Local time: 12:51 PM

Posted 29 November 2019 - 12:50 PM

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.

 

That log shows that the app completely loaded the home screen in less than 4 seconds.



#27 pir8radio OFFLINE  

pir8radio

    NGINX

  • Members
  • 2936 posts
  • Local time: 11:51 AM
  • LocationChicago

Posted 29 November 2019 - 02:26 PM

just to rule out duckdns   is there any change if you enter your remote ip directly into the client vs your  duckdns name?



#28 jmbond04 OFFLINE  

jmbond04

    Advanced Member

  • Members
  • 31 posts
  • Local time: 12:51 PM

Posted 29 November 2019 - 02:26 PM

That log shows that the app completely loaded the home screen in less than 4 seconds.


It was definitely slower than that but that time was quicker than most. It a little while I'll get you another example.

#29 jmbond04 OFFLINE  

jmbond04

    Advanced Member

  • Members
  • 31 posts
  • Local time: 12:51 PM

Posted 29 November 2019 - 04:15 PM

That log shows that the app completely loaded the home screen in less than 4 seconds.

 

I just sent new logs. Took at least 2 to 3 minutes to load. I then tried to load a show but gave up after it took ~5 minutes to go from the home screen to a Next Up TV show and only the background image had shown. 

 

Logs were sent between 3:05  and 3:15pm Eastern

Emby User Name displayed: James



#30 jmbond04 OFFLINE  

jmbond04

    Advanced Member

  • Members
  • 31 posts
  • Local time: 12:51 PM

Posted 29 November 2019 - 04:35 PM

just to rule out duckdns is there any change if you enter your remote ip directly into the client vs your duckdns name?


Just enabled http so I could try this. The problem still exists using the direct ip.

#31 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 48159 posts
  • Local time: 12:51 PM

Posted 30 November 2019 - 12:44 PM

I just sent new logs. Took at least 2 to 3 minutes to load. 

 

Did you have an actual stopwatch on this?  The log starts at 15:05:30 and shows that you selected an item at 15:05:57.

 

That is 27 seconds which, I grant you, may feel like 2-3 minutes and is still a long time.

 

It looks like it is just taking your server that long to respond.  There are no errors, just a request sent out and a response coming back almost 30 seconds later.

 

This definitely looks like it is network related somehow.  This log is going through duckdns.



#32 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 142522 posts
  • Local time: 12:51 PM

Posted 30 November 2019 - 05:02 PM

Have you tried a local network connection without the reverse proxy just to compare?



#33 jmbond04 OFFLINE  

jmbond04

    Advanced Member

  • Members
  • 31 posts
  • Local time: 12:51 PM

Posted 01 December 2019 - 04:55 PM

Did you have an actual stopwatch on this?  The log starts at 15:05:30 and shows that you selected an item at 15:05:57.

 

That is 27 seconds which, I grant you, may feel like 2-3 minutes and is still a long time.

 

It looks like it is just taking your server that long to respond.  There are no errors, just a request sent out and a response coming back almost 30 seconds later.

 

This definitely looks like it is network related somehow.  This log is going through duckdns.

 

I didn't pull out a timer and to a very strong test but I looked at the clock when I started it and when I have finished it and it had changed by 2 minutes. So it was at least over a minute. 

The other concerning thing is it was very slow to load the info screen for a show. Long enough that I stopped it and sent on the logs.



#34 jmbond04 OFFLINE  

jmbond04

    Advanced Member

  • Members
  • 31 posts
  • Local time: 12:51 PM

Posted 01 December 2019 - 04:58 PM

Have you tried a local network connection without the reverse proxy just to compare?

 

I have tried directly connecting to it but the clients with issues are the ones at another house. The clients that are on the same local network as the server are working fine.

Since the ones that are the issue are remote I can't have them connect through the local network connection.



#35 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 48159 posts
  • Local time: 12:51 PM

Posted 01 December 2019 - 06:55 PM

I have tried directly connecting to it but the clients with issues are the ones at another house. The clients that are on the same local network as the server are working fine.

 

So doesn't that pretty much confirm what we are saying about the network connection?



#36 jmbond04 OFFLINE  

jmbond04

    Advanced Member

  • Members
  • 31 posts
  • Local time: 12:51 PM

Posted 02 December 2019 - 10:45 PM

So doesn't that pretty much confirm what we are saying about the network connection?

 

How does it confirm it. As I stated before my phone had no issues using the Emby app loading up quickly on the same network where the Fire TVs that are having this issue are. The only issue came with loading from the Fire TV Emby app. I also tried Emby Theater and had no issues. So the connect was working fine. There's something different between the Fire TV app and the Web client/Emby Theater/ Emby for Android phone.



#37 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 142522 posts
  • Local time: 12:51 PM

Posted 03 December 2019 - 02:42 AM

So then have you tried lowering the in-app quality setting to reduce the bitrate?



#38 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 48159 posts
  • Local time: 12:51 PM

Posted 03 December 2019 - 10:26 AM

So then have you tried lowering the in-app quality setting to reduce the bitrate?

 

He is having very slow general response in browsing.  We haven't even gotten to playback.



#39 ebr OFFLINE  

ebr

    Chief Bottle Washer

  • Administrators
  • 48159 posts
  • Local time: 12:51 PM

Posted 03 December 2019 - 10:26 AM

What other apps are installed on these particular Fire devices?



#40 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 142522 posts
  • Local time: 12:51 PM

Posted 03 December 2019 - 12:35 PM

In that case can you please attach an emby server log from when this happened? the one in the first post is only a two minute example and doesn't contain any obvious problems. Thanks.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users