Comment accéder à ArcGIS Portal depuis l'adresse IP locale du serveur au lieu de son nom de domaine ?

Question

<\/HEAD>Bonjour à tous !<\/P> <\/P> Récemment, nous avons essayé de mettre en place un Portal pour une instance ArcGIS Server 10.7.1 dans notre infrastructure, mais nous avons rencontré un problème avec notre service de proxy inverse NGINX. Actuellement, sur ma machine Windows Server, je peux accéder à mon Portal via l'adresse : https:\/\/win-q0ejvg3fcqh.arcgis.local:7443\/arcgis\/home\/index.html<\/A>, mais chaque fois que j'essaie d'y accéder via l'adresse IP locale fixe de ma machine comme ceci : https:\/\/192.168.25.209:7443\/arcgis\/home\/index.html<\/A>, je suis redirigé vers https:\/\/win-q0ejvg3fcqh.arcgis.local:7443\/arcgis\/home\/index.html<\/A>, le nom de ma machine et son domaine. Je dois pouvoir accéder à mon Portal depuis l'adresse IP locale de son serveur afin de pouvoir rediriger ses ports vers Internet via mon serveur NGINX, comment puis-je y parvenir ? Actuellement, je n'ai aucun Web Adaptor installé et je souhaiterais vraiment continuer à utiliser uniquement mon NGINX, en raison des restrictions de l'entreprise. Toute aide sera très<\/STRONG> appréciée, Cordialement.<\/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!