privatePortalURL Value

[BrianLeroux]

I am try to fix a portal validation issue where the will occasionally fail and other times succeed. It was suggested to update theprivatePortalURL from https://LoadBalanceURL.domain.com:7443/arcgis to https://LoadBalanceURL.domain.com/portal. All documentation i found shows to use :7443 so I am not sure the suggestion otherwise is accurate and our system was initially configured by ESRI. 

@ChristopherPawlyszyn Any insight on this?

This is an HA system running on 2 VM servers. Each server has Server, Portal, and web adaptors(arcgis/portal) installed. We use an F5 load balancer. 

[mgress12]

We are experiencing similar behavior after implementing a privatePortalURL using the format: https://LoadBalanceURL.domain.com:7443/arcgis

This is a 10.9.1 HA deployment with two portal servers, two federated servers, and one web adaptor with IWA. F5 is the load balancer.

Federated servers will validate successfully off and on. We are also seeing this with publishing hosted feature layers and deleting items. The inconsistences came with setting the privatePortalURL.

We've tried turning off one portal machine to see if that clears up the issue but no luck so far. No blocks encountered in the firewall that line up with the errors we see in Portal.

Error messages include:

Could not connect to the ArcGIS component at URL 'https://LoadBalanceURL.domain.com:7443/arcgis.' The ArcGIS component on that machine may not be running or the machine may not be reachable at this time.Error: Connection reset.

We've opened a support case to work through the issue.

[BrianLeroux]

Your system configuration sounds nearly identical to mine. I also have a case open and they are doing a bit of research now. please keep me posted if you make any progress in resolving your issues and i will do the same. thanks.

PS for some strange reason when i right click copy your second link in your post above and copy to a browser it shows me your actually URL you must have copied in and edited. Probably not a huge deal but you may want to edit that out.

[mgress12]

Thanks, will do.

[mgress12]

So far we haven't been able to identify the cause of the connection resets between our F5 load balancer and Portal. We can see the resets through Wireshark captures but haven't yet found a solution.

As an alternative, we have had luck using the Application Request Routing module in IIS to balance the requests to our two Portal machines.

[BrianLeroux]

Thanks for the update. We are still working with ESRI on the issue and no solid leads yet. We are looking into firewall and traffic routing soon but I expect to see what you are seeing.

[BillFox]

do you have ADFS in the mix?

[BrianLeroux]

While we have ADFS for other uses I do not believe it is in the mix for our GIS system.

[BillFox]

I believe setting the private portal url and web context url is required to be set at the time of installation only and any adjustments after the build will have glitches or flop with any already created content.

[BillFox]

for example: all case sensitive

in your portal admin page,

home > system > properties

the two settings must be the same:

WebContextURL : https://<public facing url for portal>/<portal's webadaptorname>

privatePortalURL: https://<public facing url for portal>/<portal's webadaptorname>

and then in arcgis server's home > security > config

these two should be the same value as those two

portalUrl

privatePoralUrl

Then the two should be set to similar for arcgis server's web adaptor via the public url / reverse proxy / dns alias

serverUrl : https://<public facing url for portal>/<arcgis server's webadaptor name>

privateHostingServerUrl : https://<public facing url for portal>/<arcgis server's webadaptor name>

@ChristopherPawlyszyn https://community.esri.com/t5/arcgis-enterprise-questions/webcontexturl-or-web-adapter/td-p/1073142

https://enterprise.arcgis.com/en/portal/11.1/administer/windows/configure-existing-enterprise-deploy...