AnsweredAssumed Answered

Failing to login to ArcGIS Server when it is federated with Portal on Azure

Question asked by valraa on Jul 20, 2017
Latest reply on Jan 21, 2019 by json.ajax

Hi,

 

the machine in question has winserver 2016 and IIS 10.

ArcGIS Enterprise pre-installed and not configured ("esri" image in the MS Azure market).

Now I'm in the process of installing and configuring the WebAdaptor.

In previous installations I checked that the URL I was using to access the webadaptor was the external DNS so that I could access arcgis server and portal from outside through port 80.

Inthis installation, I have problems in doing so for Portal in the sense that when I click on "Cofigure" in "https://<my_external_DNS>/arcgis/webadaptor/portal", it says that configuration succeeded, but the link provided does not work (a blank page shows up).

I typed in as the portal URL "https://<my_external_DNS>:7443" for portal.

For ArcGIS Server it does not even configure. I receive an error saying "Additional non-parsable characters are at the end of the string".

Strangely, unregistering WebAdaptor from Portaladmin, I can access the portal with https://<my_external_DNS>:7443, but it automatically redirects to https://<my_internal_DNS>:7443/arcgis/home/.

To be precise: https://beagis.westus2.cloudapp.azure.com:7443 redirects to https://bea-arcgis-srv.1radqad4t4hulcabelsigtpwqb.xx.internal.cloudapp.net:7443/arcgis/home/ . I think this is the problem and this is how the installation provided with the image was dsigned.

If I use the internal_DNS I can succesfully configure the WebAdaptor, but I had other problems, like not being able to login to arcgis/rest/services (after pressing login I was receiving a Timeout Exceed error).

The only source I could find to be of help was this other thread, specifically one comment saying "I had a similar problem on my Windows network system.  Seems it was because I had initially setup things using our internal network names (before installing our SSL certs).  I needed to unregistered portal from the Web Adapter and then go through the setup using the public domain name the cert was applied to.".

I need this to work as it should have been easier than installing everything from scratch, but it is getting even way harder...

Aprreciate any help.

Outcomes