LaurenceM 1 Posted April 30, 2016 Share Posted April 30, 2016 Hi, I've been using Emby for a good 6 months now and it used to load almost instantly however after an upgrade a while back it takes a good 5+ seconds to display the media whenever you refresh the page. Emby is on a dedicated server with a VLAN to a NAS and an external connection for remote access - nothing has changed here to cause the slowdown. I've noticed when watching the page load log i see a timeout saying: Failed to load resource: net::ERR_CONNECTION_TIMED_OUT http://192.168.0.4:8096/emby/system/info/public For some reason Emby is trying to load the local IP of the server on my remote PC, which of course wouldn't work so is timing out. This loads first in the script which is why nothing displays until the timeout. My Emby settings haven't changed either, and as far as I can see there isn't anything on the web interface to change to stop it loading a local ip for this one script? Is there a config file or software file that can be edited to go off the external ip rather than local? Thanks Link to comment Share on other sites More sharing options...
bfir3 113 Posted April 30, 2016 Share Posted April 30, 2016 This issue has been reported over here: http://emby.media/community/index.php?/topic/32100-very-slow-loading-of-nextup-latest-items Not much progress on the cause yet, but it is happening to a handful of users at the very least. 1 Link to comment Share on other sites More sharing options...
Luke 37057 Posted June 2, 2016 Share Posted June 2, 2016 So basically it tries to connect to that url first, then times out and uses the right one? If that sounds correct, then I would try clearing your browsing data and seeing if that resolves it. What is the url of the web client you're using? Is it your personal server url, or are you using the online hosted version at app.emby.media? Link to comment Share on other sites More sharing options...
LaurenceM 1 Posted June 2, 2016 Author Share Posted June 2, 2016 (edited) Hey Luke, thanks for getting back to me. It's not a browser issue as it does it for every user on my Emby (15 different people), on Chrome, Firefox and IE. I have a server located within a data center, and the Emby Server app running at emby.laurencemillward.co.uk Basically i go to emby.laurencemillward.co.uk from any PC and it starts loading the page, but will sit loading (spinning wheel) for exactly 8 seconds before timing out a local ip (the local ip of the server) and then proceeds to load almost instantly after that 8 seconds. The first connection the browser makes is: Begin connectToServers, with 1 servers connectionmanager.js?v=3.0.5972.0:1076 testing connection mode 0 with server Laurence Millward - Emby connectionmanager.js?v=3.0.5972.0:200 tryConnect url: http://192.168.0.20:8096/emby/system/info/public connectionmanager.js?v=3.0.5972.0:172 ConnectionManager requesting url: http://192.168.0.20:8096/emby/system/info/public connectionmanager.js?v=3.0.5972.0:123 fetchWithTimeout: timeoutMs: 8000, url: http://192.168.0.20:8096/emby/system/info/public Obviously this wouldn't work as it's trying to load the local IP of the server rather than the remote IP of the server. There is a quick fix to change the timeout from 8 seconds to something like 1, but i'm not sure if this is something i can change somewhere until an official fix is found? Or if there is a way to stop it trying to load the local IP, and to use the remote one instead. So basically it tries to connect to that url first, then times out and uses the right one? If that sounds correct, then I would try clearing your browsing data and seeing if that resolves it. What is the url of the web client you're using? Is it your personal server url, or are you using the online hosted version at app.emby.media? Edited June 2, 2016 by LaurenceM Link to comment Share on other sites More sharing options...
LaurenceM 1 Posted June 2, 2016 Author Share Posted June 2, 2016 (edited) Here is the full network log, as you can see Emby tries loading a local IP before the remote one which is why once the 8 second timeout is up, it loads instantly. Begin connect connectionmanager.js?v=3.0.5972.0:808 Begin getAvailableServers connectionmanager.js?v=3.0.5972.0:756 Begin getConnectServers connectionmanager.js?v=3.0.5972.0:926 Begin connectToServers, with 1 servers connectionmanager.js?v=3.0.5972.0:1076 testing connection mode 0 with server Laurence Millward - Emby connectionmanager.js?v=3.0.5972.0:200 tryConnect url: http://192.168.0.20:8096/emby/system/info/public connectionmanager.js?v=3.0.5972.0:172 ConnectionManager requesting url: http://192.168.0.20:8096/emby/system/info/public connectionmanager.js?v=3.0.5972.0:123 fetchWithTimeout: timeoutMs: 8000, url: http://192.168.0.20:8096/emby/system/info/public chrome-extension://enhhojjnijigcajfphajepfemndkmdlo/cast_sender.js Failed to load resource: net::ERR_FAILED chrome-extension://fmfcbgogabcbclcofgocippekhfcmgfj/cast_sender.js Failed to load resource: net::ERR_FAILED connectionmanager.js?v=3.0.5972.0:191 ConnectionManager request failed to url: http://192.168.0.20:8096/emby/system/info/public connectionmanager.js?v=3.0.5972.0:1095 test failed for connection mode 0 with server Laurence Millward - Emby connectionmanager.js?v=3.0.5972.0:1076 testing connection mode 1 with server Laurence Millward - Emby connectionmanager.js?v=3.0.5972.0:200 tryConnect url: http://emby.laurencemillward.co.uk:8096/emby/system/info/public connectionmanager.js?v=3.0.5972.0:172 ConnectionManager requesting url: http://emby.laurencemillward.co.uk:8096/emby/system/info/public connectionmanager.js?v=3.0.5972.0:123 fetchWithTimeout: timeoutMs: 20000, url: http://emby.laurencemillward.co.uk:8096/emby/system/info/public connectionmanager.js?v=3.0.5972.0:135 fetchWithTimeout: succeeded connecting to url: http://emby.laurencemillward.co.uk:8096/emby/system/info/public connectionmanager.js?v=3.0.5972.0:176 ConnectionManager response status: 200, url: http://emby.laurencemillward.co.uk:8096/emby/system/info/public connectionmanager.js?v=3.0.5972.0:1089 calling onSuccessfulConnection with connection mode 1 with server Laurence Millward - Emby connectionmanager.js?v=3.0.5972.0:172 ConnectionManager requesting url: http://emby.laurencemillward.co.uk:8096/emby/System/Info Edited June 2, 2016 by LaurenceM 1 Link to comment Share on other sites More sharing options...
Luke 37057 Posted June 3, 2016 Share Posted June 3, 2016 Hi, yes I can reproduce this. I am looking into it, thanks. Link to comment Share on other sites More sharing options...
Luke 37057 Posted June 3, 2016 Share Posted June 3, 2016 ok, i'll have a fix going up on the beta channel later today. thanks. Link to comment Share on other sites More sharing options...
LaurenceM 1 Posted June 8, 2016 Author Share Posted June 8, 2016 Hi Luke, Thanks for taking time to look at this. I just updated my Emby to the latest beta release and it's still taking 8 seconds to load the main homepage. Once the connection is made everything after that loads instantly until i refresh the page, but the initial first load of the emby site takes 8 seconds as per: Begin connect connectionmanager.js?v=3.1.13.0:809 Begin getAvailableServers connectionmanager.js?v=3.1.13.0:757 Begin getConnectServers connectionmanager.js?v=3.1.13.0:927 Begin connectToServers, with 1 servers connectionmanager.js?v=3.1.13.0:1080 testing connection mode 0 with server Laurence Millward - Emby connectionmanager.js?v=3.1.13.0:200 tryConnect url: http://192.168.0.20:8096/emby/system/info/public connectionmanager.js?v=3.1.13.0:172 ConnectionManager requesting url: http://192.168.0.20:8096/emby/system/info/public connectionmanager.js?v=3.1.13.0:123 fetchWithTimeout: timeoutMs: 8000, url: http://192.168.0.20:8096/emby/system/info/public chrome-extension://enhhojjnijigcajfphajepfemndkmdlo/cast_sender.js Failed to load resource: net::ERR_FAILED chrome-extension://fmfcbgogabcbclcofgocippekhfcmgfj/cast_sender.js Failed to load resource: net::ERR_FAILED connectionmanager.js?v=3.1.13.0:191 ConnectionManager request failed to url: http://192.168.0.20:8096/emby/system/info/public connectionmanager.js?v=3.1.13.0:1099 test failed for connection mode 0 with server Laurence Millward - Emby connectionmanager.js?v=3.1.13.0:1080 testing connection mode 1 with server Laurence Millward - Emby connectionmanager.js?v=3.1.13.0:200 tryConnect url: http://emby.laurencemillward.co.uk:8096/emby/system/info/public connectionmanager.js?v=3.1.13.0:172 ConnectionManager requesting url: http://emby.laurencemillward.co.uk:8096/emby/system/info/public connectionmanager.js?v=3.1.13.0:123 fetchWithTimeout: timeoutMs: 20000, url: http://emby.laurencemillward.co.uk:8096/emby/system/info/public connectionmanager.js?v=3.1.13.0:135 fetchWithTimeout: succeeded connecting to url: http://emby.laurencemillward.co.uk:8096/emby/system/info/public and right at the bottom of the network log also shows a: Requesting url without automatic networking: http://emby.laurencemillward.co.uk:8096/LiveTv/Recordings?userId=36d89533ad…f71ab&limit=5&Fields=PrimaryImageAspectRatio%2CSyncInfo&IsInProgress=false http://192.168.0.20:8096/emby/system/info/public Failed to load resource: net::ERR_CONNECTION_TIMED_OUT connectionmanager.js?v=3.1.13.0:142 fetchWithTimeout: timed out connecting to url: http://192.168.0.20:8096/emby/system/info/public mediacontroller.js?v=3.1.13.0:16 keyCode 123 Link to comment Share on other sites More sharing options...
Luke 37057 Posted June 8, 2016 Share Posted June 8, 2016 ok I think I see the issue. Thanks. Link to comment Share on other sites More sharing options...
LaurenceM 1 Posted June 9, 2016 Author Share Posted June 9, 2016 Hey Luke, Found out what was causing it I had "emby.laurencemillward.co.uk" in the Advanced > "External Domain" setting. Obviously emby isnt a DNS server so not sure why I even had it in the first place when i have external DNS. I removed the domain from there and it now loads almost instantly, no sign of any spinning wheel or timeouts! Although people who use that setting will be seeing the same issues I was potentially? Link to comment Share on other sites More sharing options...
Luke 37057 Posted June 9, 2016 Share Posted June 9, 2016 Actually in this case I don't think it's related to that setting. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now