Como acessar o ArcGIS Portal a partir do endereço IP local do servidor em vez do nome de domínio?

Question

<\/HEAD>Olá a todos!<\/P> <\/P> Recentemente, temos tentado implementar um Portal para a instância do ArcGIS Server 10.7.1 em nossa infraestrutura, mas encontramos um problema com nosso serviço de proxy reverso NGINX. Atualmente, na minha máquina Windows Server, posso acessar meu Portal pelo endereço: https:\/\/win-q0ejvg3fcqh.arcgis.local:7443\/arcgis\/home\/index.html<\/A>, mas sempre que tento acessá-lo via o IP local fixo da minha máquina assim: https:\/\/192.168.25.209:7443\/arcgis\/home\/index.html<\/A> sou redirecionado para https:\/\/win-q0ejvg3fcqh.arcgis.local:7443\/arcgis\/home\/index.html<\/A>, o nome da minha máquina e domínio. Preciso ser capaz de acessar meu Portal pelo endereço IP local do servidor para que eu possa encaminhar suas portas para a internet via meu servidor NGINX, como posso conseguir isso? Atualmente, não tenho nenhum Web Adaptor instalado e realmente gostaria de continuar usando apenas meu NGINX, devido a restrições da empresa. Qualquer ajuda será muito<\/STRONG> apreciada, Saudações.<\/P><\/BODY><\/HTML>

ChristopherPawlyszyn · Accepted Answer

Hello João Victor Teófilo Salgado,

From what I understand you seem to need a method to have Portal using the private IP address for it's site configuration. This is typically done in our CloudFormation template deployments in AWS as well, and would need to be defined as a hostname.properties entry prior to site creation.

Installing Portal for ArcGIS—Portal for ArcGIS | Documentation for ArcGIS Enterprise

Additionally, there are more requirements for your NGINX and Portal configuration that are outlined in this documentation.

Configure your portal to use a reverse proxy server—Portal for ArcGIS | Documentation for ArcGIS Enterprise.

Customers tend to have the most issue with making sure the location headers in 30x responses are re-written to the WebContextURL, in my experience. When they have those issues, an easy workaround is to implement the web adaptors in front of Portal and Server and still have NGINX pass the traffic to those endpoints. If that is something you choose not to do, this information may be helpful as well.

Nginx (Reverse Proxy) and ArcGis Portal

Best of luck!

teofilosalgado · Accepted Answer

Hi Christopher,

I managed to make it work with plain NGINX, I was missing these headers in my configuration:
proxy_set_header X-Forwarded-Host $host:$server_port;

proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

The links you've sent were very helpful, specially the last one! Thank you very much for your help!