Select to view content in your preferred language

Secondary server refusing to connect using HTTPS.

951
3
Jump to solution
12-11-2024 07:07 AM
GeoNomad
Occasional Contributor

Hi.

I'm having a problem with ArcGIS Enterprise 11.2. We have a multi-machine deployment running through an App Gateway in Azure.  One of our servers refuses to connected when switching from Http and Https.

Server has problem with 6443 port machine status gets error "Error"

Failed to get the status of the server machine 'server.domain'. Could not connect to the ArcGIS component at URL 'https://server:6443/arcgis/admin/local/isAppServerStarted'. The ArcGIS component on that machine may not be running or the machine may not be reachable at this time.Error: Connection refused: connect

Code

500

I've reached out to ESRI support but wanted to know if anyone has a workflow to fix this issue. Thank you in advance!

@JakeSkinner @BhaskaraGummadi

0 Kudos
1 Solution

Accepted Solutions
GeoNomad
Occasional Contributor

Just to add the steps that I've taken:

  • Stopped ArcGIS Server Service
  • Located the server.xml file at C:\ArcGIS\Server\framework\runtime\tomcat\conf
  • Opened Notepad as an admin and noticed the keyAlias was missing "Application Gateway", added that and saved.
  • Restarted the ArcGIS Server Service. 
  • Opened the server.xml file and noticed the changes to the keyAlias setting were not saved.
  • Opened Server Admin and compared the primary and secondary server machines settings.
  • Noticed Application Gateway parameter was missing in the Web Server SSL Certificate setting on the secondary server machine.
  • Edited the machine settings, went back to the server xml file and added Application Gateway, saved and restarted service.
  • Working now.

View solution in original post

3 Replies
GeoNomad
Occasional Contributor

Just to add the steps that I've taken:

  • Stopped ArcGIS Server Service
  • Located the server.xml file at C:\ArcGIS\Server\framework\runtime\tomcat\conf
  • Opened Notepad as an admin and noticed the keyAlias was missing "Application Gateway", added that and saved.
  • Restarted the ArcGIS Server Service. 
  • Opened the server.xml file and noticed the changes to the keyAlias setting were not saved.
  • Opened Server Admin and compared the primary and secondary server machines settings.
  • Noticed Application Gateway parameter was missing in the Web Server SSL Certificate setting on the secondary server machine.
  • Edited the machine settings, went back to the server xml file and added Application Gateway, saved and restarted service.
  • Working now.
TimoT
by
Frequent Contributor

It's great that you resolved your issue, but I'd be wary and double check all your directory permissions for service account are in order. 

There are few situations that you should ever need to manually edit the server.xml file. The key alias is simply the alias of an imported (or self signed) certificate that is bound to the server's HTTPS port. 

When you perform this step as per Esri documentation, it should update the keyalias portion of the server.xml file for you.

Double check your server service account permissions, or you may have further problems down the line

aamohamed
New Contributor

Thanks a lot for the solutions, I faced the same issue and it had been solved with your solution but I need to add one more information, server.xml may  have two parts for keyAlias  value so you have to insert a value on both and you may use the default generated SSL certificate value "selfsignedcertificate" and then from admin page you can upload your certificate and once update your ArcGIS server machine certificate the server.xml will be updated permanently and your issue will be solved.

 

Thanks

0 Kudos