How to collect Users statistics behind reverse proxy. IP Address always the same.

Permanently deleted user

15 juin 2016 16:51

I have statistics that are collecting for the "Users" information, but the IP addresses are all the same.  I'm assuming this has something to do with reverse proxy or web adaptor.  Any suggestions?

 

0

• 

  Permanently deleted user

  15 juin 2016 17:55

  I don't have a solution but I can't get any user stats from behind my reverse proxy.  Could you maybe provide some information on how you configgured Insights ( Analytics) to capture the data?

   

   

  0
• 

  Permanently deleted user

  15 juin 2016 18:20

  Check this (I just had Tech Support help me with this):

   

  In IISLog role.config add a ServerOverride tag specifiying your reverse proxy

   

        <Folder Name="IIS Logs - ArcGIS Server Tiled Services" Path="\\gis-geo-web-00.pottcounty.lan\logfiles" Username="arcgis" Password="*" Domain="POTTCOUNTY" ServerOverride="gis.pottcounty-ia.gov" />

   

  Same with ArcGISLog:

   

      <Folder Name="ArcGIS Logs - GISAPPS-2 Network Share" Path="\\gis-geo-arc-00\g$\arcgisserver_logs" Username="arcgis" Password="*" Domain="POTTCOUNTY" ServerOverride="gis.pottcounty-ia.gov" />

   

  In these gis-geo-web-00 is the webserver and hosts GVH viewer.  gis-geo-arc-00 is the arcgis server.

   

  Also check that your client relay is working by pasting the client relay url into a browser - you should get a 200 response, like you get with this: http://insight.pottcounty-ia.gov/Geocortex/Insight/Insight/ClientRelay

   

   

  0
• 

  Permanently deleted user

  15 juin 2016 19:36

  Hi Jamie and Craig,

   

  Jamie, your issue is a known bug.  The client relay will always report the last hop, which in your case is the reverse proxy IP address.  We have an open improvment to fix this (GID-430), but there is no timeline yet for when it will be addressed.  I'll add you as a stakeholder.

   

  Craig, for your issue, I don't think the reverse proxy is the problem (although it could be).  The key thing with Insight is that the URLs that your users are using to access the viewer need to match the URLs that Insight has auto discovered for the viewer.  Have a look at the URL your users are using, and compare it to the URL that shows up in Insight (under Geocortex Applications > Viewer name).  If they don't match, that's probably the issue.

   

  I hope this helps!

   

  Thanks,

   

  Danny

  0
• 

  Jeff Timm

  31 janvier 2018 17:34

  Has there been a resolution to this yet?  I have the same issue.

  0
• 

  Jeff Timm

  31 janvier 2018 17:35

  Also if this is the case "Have a look at the URL your users are using, and compare it to the URL that shows up in Insight (under Geocortex Applications > Viewer name).  If they don't match, that's probably the issue."

   

  How do you change that in Analytics?

  0

Vous devez vous connecter pour laisser un commentaire.