¿Cómo acceder a ArcGIS Portal desde la dirección IP local del servidor en lugar de su nombre de dominio?

Question

<\/HEAD>¡Hola a todos!<\/P> <\/P> Recientemente, hemos estado intentando implementar un Portal para la instancia de ArcGIS Server 10.7.1 en nuestra infraestructura, pero nos hemos topado con un problema con nuestro servicio de proxy inverso NGINX. Actualmente, en mi máquina Windows Server puedo acceder a mi Portal a través de la dirección: https:\/\/win-q0ejvg3fcqh.arcgis.local:7443\/arcgis\/home\/index.html<\/A>, pero cada vez que intento acceder mediante la IP local fija de mi máquina así: https:\/\/192.168.25.209:7443\/arcgis\/home\/index.html<\/A> me redirige a https:\/\/win-q0ejvg3fcqh.arcgis.local:7443\/arcgis\/home\/index.html<\/A>, el nombre y dominio de mi máquina. Necesito poder acceder a mi Portal desde la dirección IP local de su servidor para poder reenviar sus puertos a internet a través de mi servidor NGINX, ¿cómo podría lograr eso? Actualmente, no tengo ningún Web Adaptor instalado y realmente me gustaría seguir usando solo mi NGINX, debido a restricciones de la empresa. Cualquier ayuda será muy<\/STRONG> apreciada, Saludos.<\/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!