Site fails to load, takes too long to respond

Permanently deleted user

6. Dezember 2016 16:51

I'm testing out our first HTML5 viewer (2.7.1).  Internally on our network, everything works fine but it still takes on average 9-13 seconds to get past the splash page.  However, some can load the site externally and some can't.  Those who can't, get the message: "This site can’t be reached [servername] took too long to respond". The wierd part is this problem is random.

 

Things I've checked so far:

• Ensured users are using recommended browsers with JS turned allowed (turned on)
• Geocortex Manager and HTML5 Viewer reside on same server
• Ran Fiddler and no errors.
• I have about 42 map services sitting in Manager but I've only added the layers to the viewer, not the entire service
• None of the layers are secured - it's not needed since this is the public viewer
• There is no SSL currently set up (yet)
• I only have one site and one viewer
• I don't have any workflows running on startup other than the standard splash page
• There are no data connections
• I only have three basemaps - two ESRI World maps and one Bing map
• I have no search tables

0

• 

  Permanently deleted user

  23. Dezember 2016 23:40

  Hi Stephanie,

   

  When you say that some people can load the site externally and some cannot, is that behavior consistent  -- i.e., those who can access the site can always and those who cannot can never access the site? I'm guessing that, by random, you mean that this isn't the case (i.e., sometimes people can access the site and sometimes they can't), but I want to be sure.

   

  (https://support.geocortex.com/essentialsGSCkba?sub-nav=kba&main-nav=essentials&feedtype=SINGLE_ARTICLE_SEARCH_RESULT&id=kA360000000L142) This article may help you to troubleshoot the issue; if it doesn't help, you may want to (To: support@latitudegeo.com) open a support case.

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.