ALB Pathing to analytics error
Hi
I have configured an AWS Application Load Balancer (ALB) to direct all queries to a Geocortex cluster, but to another server when the path /analyticsreports/ is used.
After configuring analytics correctly on the server, and having the correct pages come up from http://localhost/analyticsreports/
I get a 404 error when using the full external path to the server (ALB)
This is the 404 from the FireFox debug network page , a post to (what appears to be the ArcGIS portal server)
https://server.example.com/Geocortex/Analytics/Security/Saved/Get
Could there be a CORS issue here. Anyone encountered this?
I've attached the error from the browser page

0
-
Hi Roland,
The request getting a 404, https://server.example.com/Geocortex/Analytics/Security/Saved/Get, should be the Analytics server, it's the sign-in process.
You'll need to configure another entry in the AWS ALB, to point to the Analytics server when the path /Geocortex/Analytics/ is used.
Thanks,
Aaron Oxley0 -
Thanks Aaron
I had a path rule pointing to the server, that was the issue.
I resolved the issue by creating another ALB rule for a different FQDN, pointing to analytics. Thus the header determines the server at the endpoint, not the path.
Roland0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
2 commentaires