Install ArcGIS Enterprise on a Home LAN

[JimSaundersJr]

I have a Lenovo ThinkSystem SR630 server running Windows Server 2019 and I have installed IIS 10. The server is on my home LAN fed by a Google Fiber Router. I have a Domain Name / Website from Google Domains and I have managed to publish a test website from my server. (Not hosted by Google.) I have a Let'sEncrypt SSL certificate issued for my domain name. I am trying to install ArcGIS Enterprise on this server using ArcGIS Enterprise Builder. I am not having any luck. It seems that Builder requires a Fully Qualified Domain Name (FQDN) in order to install properly. It breaks down when trying to configure the Web Adaptors for Portal and Server.

Has anyone setup ArcGIS Enterprise using ArcGIS Enterprise Builder (or in any way) on a home server and gotten it to work? Do I need to install a DNS service on my server to get this to work?

I'm afraid I do not have a lot of experience / knowledge with Network Engineering. Thanks.

[HenryLindemann]

Hi @JimSaundersJr how far did you get with the deployment ?

 When you open your site https://saundersintl.net/portal/webadaptor on the server do you see the webadaptor configuration page ?

have you configured them like this 

ArcGIS Server 

ArcGIS for portal

• You can make the host file entry but before you install ArcGIS for portal and never change it after the fact.
• Can you check the log file name under c:\arcgisportal\logs or where you installed ArcGIS for portal
• what is the name is it saundersintl.net if not make the host file entry and uninstall portal clean out c:\program files\arcgis\portal and reinstall portal NB if this is a clean install.

• can you confirm that the webadaptors are reflecting under your website you want to see server and portal in here

  

   
• I noted that you have a website also running on this url in the root, this can cause conflicts

          

if yes can you move your personal website to a folder.

if you are open to it call it something like home, then your website would be https://saundersintl.net/home

otherwise you will have to make a redirect with url re-writes to the home folder if you want to preserve https://saundersintl.net

Is ArcGIS Enterprise up

on the server if you open https://saundersintl.net:6443/arcgis/manager and https://saundersintl.net:7443/arcgis/home do you see websites?

Please let me know what is working or not and I will guide you trough the steps, first lets get it working on your server then we will worry about the rest, but I think when it is working then you will be good to go.

Kind Regards

Henry

[JimSaundersJr]

I believe that the https://SaundersIntl.net is not being recognized as being on my SI-Server1.  When I enter https://saundersintl.net/portal/webadaptor I get the message "The web adaptor configuration URL has to be accessed from the machine hosting the web adaptor."  I am using the Google Domains site to enter my DNS Resource records.  And I can not get anything to recognize https://SI-Server1.saundersintl.net/* .

When I try https://saundersintl.net:6443/arcgis/manager I get the response "

This site can’t be reached

saundersintl.net refused to connect.

When I try https://saundersintl.net:7443/arcgis/home I get the same refused to connect message.

I'm afraid I will need to install Active Domain and a Domain Network Service on my server in order to move my saundersintl.net domain name to my server.

[JimSaundersJr]

The website you see is installed on my SI-Server1. (Windows Server 2019).  IIS has the first "Default Web Site" at C:\inetpub\wwwroot and the second defined website is this "saundersintl.net" at C:\inetpub\saundersintl and it is my test website.  But I can not get SI-Server to join the saundersintl.net domain.

[Scott_Tansley]

The domain is an alias that points to the server.  On the web prod machine you could use use https://localhost/portal/webadaptor yes you’ll get certificate errors but ignore them.  Then in the configuration you can enter si-server.lan and the credentials.  The web adaptor only needs to know about the internal routes to application servers.  Not the external Alias name.