Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

MID Server installation shows "Cannot connect to install.service-now.com"

小沢真
Tera Contributor

Hi,

I am trying to install a MID Server, but the following warning is displayed during the installation:

_0-1791177023916.png

 

Warning: Cannot connect to install.service-now.com.
Installation can continue successfully, but the MID Server will not be able to auto-upgrade. Press 'Next' to continue.

This issue occurs in my home lab environment on both Windows Server 2016 and Windows Server 2025.

 

Although the installation appears to be able to continue, it seems that the MID Server will not be able to perform automatic upgrades and would therefore require manual upgrades in the future.

 

Therefore, I would like to understand what is causing this warning and how I can resolve it, rather than simply proceeding with the installation.

 

Could anyone advise what could cause this warning?

 

Thank you.

2 REPLIES 2

Tanushree Maiti
Tera Patron

Hi @小沢真 

 

Can you check this KB's Resolution:

KB1710292 Unable to connect to instance while installing MID server 

 

Also  check community post:

https://www.servicenow.com/community/developer-forum/mid-server-installation-issue/m-p/3102951/page/...

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

Thank you for checking.

 

The issue we are experiencing is slightly different from the one described in the KB you shared.

 

There are no issues with connectivity to the ServiceNow instance, and when we proceeded with the installation, the MID Server was able to communicate with the instance without any problems.

 

However, as stated in the warning message, automatic upgrades will not be available. Therefore, even though the MID Server can successfully communicate with the instance, we believe that we will need to perform upgrades manually going forward.

 

We would like to understand what is causing this warning to appear.