<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic GeoEvent manager on 443 behind reverse proxy in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/geoevent-manager-on-443-behind-reverse-proxy/m-p/620143#M23873</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have GeoEvent behind a reverseproxy to do port translation between 6143 and 443.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This works fine for the REST interface:&lt;/P&gt;&lt;P&gt;&lt;A href="https://geoevent.domain.com/geoevent/rest"&gt;https://geoevent.domain.com/geoevent/rest&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, when going to&lt;/P&gt;&lt;P&gt;&lt;A href="https://geoevent.domain.com/geoevent/manager/"&gt;https://geoevent.domain.com/geoevent/manager/&lt;/A&gt; it redirects the page itself to 6143 ,which is forbidden at our network environment for public use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to configure Geoevent Manager behind a reverseproxy (or a Webadaptor if that works too)?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 13 May 2019 14:48:21 GMT</pubDate>
    <dc:creator>SchipholArchitect</dc:creator>
    <dc:date>2019-05-13T14:48:21Z</dc:date>
    <item>
      <title>GeoEvent manager on 443 behind reverse proxy</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/geoevent-manager-on-443-behind-reverse-proxy/m-p/620143#M23873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have GeoEvent behind a reverseproxy to do port translation between 6143 and 443.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This works fine for the REST interface:&lt;/P&gt;&lt;P&gt;&lt;A href="https://geoevent.domain.com/geoevent/rest"&gt;https://geoevent.domain.com/geoevent/rest&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, when going to&lt;/P&gt;&lt;P&gt;&lt;A href="https://geoevent.domain.com/geoevent/manager/"&gt;https://geoevent.domain.com/geoevent/manager/&lt;/A&gt; it redirects the page itself to 6143 ,which is forbidden at our network environment for public use.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to configure Geoevent Manager behind a reverseproxy (or a Webadaptor if that works too)?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 May 2019 14:48:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/geoevent-manager-on-443-behind-reverse-proxy/m-p/620143#M23873</guid>
      <dc:creator>SchipholArchitect</dc:creator>
      <dc:date>2019-05-13T14:48:21Z</dc:date>
    </item>
    <item>
      <title>Re: GeoEvent manager on 443 behind reverse proxy</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/geoevent-manager-on-443-behind-reverse-proxy/m-p/620144#M23874</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Schiphol,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This could be due to not having the WebContextURL property being set in the ArcGIS Server Admin endpoint. The process can be found here:&amp;nbsp;&lt;A href="https://enterprise.arcgis.com/en/server/latest/deploy/windows/using-a-reverse-proxy-server-with-arcgis-server.htm"&gt;https://enterprise.arcgis.com/en/server/latest/deploy/windows/using-a-reverse-proxy-server-with-arcgis-server.htm&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the WebContextURL set the manager should no longer redirect to the internal port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Cody&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 May 2019 20:06:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/geoevent-manager-on-443-behind-reverse-proxy/m-p/620144#M23874</guid>
      <dc:creator>CodyMarsh</dc:creator>
      <dc:date>2019-05-22T20:06:49Z</dc:date>
    </item>
  </channel>
</rss>

