Select to view content in your preferred language

How can I change the httpProt and httpsPort at portal.domain.com:7443/arcgis/sharing/rest/self (Portal 10.9.1 Linux))

600
4
11-03-2022 12:39 PM
Labels (1)
RobertRaines
Emerging Contributor

How can I change the httpPort and httpsPort at portal.domain.com:7443/arcgis/sharing/rest/self?

 

These values are usually 80 and 443, but on my install they are 7080 and 7443. This is a fresh install just registered with WebAdaptor. I have reloaded multiple times and this has happened.

 

How can I change these values? THere is an update link near the bottom of the page but these keys/values are not available t ochange.

0 Kudos
4 Replies
Scott_Tansley
MVP Regular Contributor

The first question is, why do you need to change them?  The web adaptor runs on 80/443 (preferably only 443) and it forwards the requests to the 7080/7443 ports, which is part of the standard flow.  We don't really change those ports.

Scott Tansley
https://www.linkedin.com/in/scotttansley/
0 Kudos
RobertRaines
Emerging Contributor

When I connect through WebAdaptor my browser is being pointed to Webadaptor_FQDN:7443/portal/sharing/rest/... instead of WebAdaptor_FQDN:443/portal/sharing/rest...  

Those variables on all my other ESRI instances are set to 80/443 when accessing through webadaptor but 7080/7443 on this new 10.9.1 instance. When you connect directly to the Portal they are 7080/7443. I think my config change needs to happen on the WebAdaptor not Portal as I initially thought.

0 Kudos
Scott_Tansley
MVP Regular Contributor

Can you check the properties of your webcontexturl:  https://enterprise.arcgis.com/en/portal/latest/administer/windows/using-a-reverse-proxy-server-with-... 

I always explicitly set this, even with Web Adaptors.  It forces all 'responses' to use the correct path.  Maybe setting it, if it's not set may help.

Scott Tansley
https://www.linkedin.com/in/scotttansley/
0 Kudos
RobertRaines
Emerging Contributor

We going to go a different direction, we can visualize our data on another tool that costs less and gives us less headaches, ESRI support has been unable to help and we just don't have time to fight their tools anymore. We have already removed them from other projects with great success, this one is next. I appreciate the help from everyone on this thread. Thank you.

0 Kudos