Creating new Update Set Source error: "Unable to validate connection: Loopback and site-local URLs are not supported. Provide the URL of another instance"

[s_w_]

I am trying to create a new Update Set Source (sys_update_set_source) across 2 London environments, but am getting the error:

Unable to validate connection: Loopback and site-local URLs are not supported. Provide the URL of another instance

I would like to know what this error means, and how to resolve it.

The urls I'm using are in the form: 'https://instance1.company.com', 'https://instance2.company.com', etc.

All environment access errors / firewall issues should be resolved.

I am able to create these Update Set Sources from some of our Istanbul environments (currently going through an upgrade) and test connection to the same instances with no issue (except a warning that the instances have different versions)

Thanks in advance

[Allen Andreas]

Are you meaning you're doing https://instance1.service-now.com? If not, that's the format it needs to be in.

Please mark reply as Helpful/Correct. Thanks!

[s_w_]

Our ServiceNow instances are all 'On Premise', so local company urls.

[Allen Andreas]

Ah, understood. Never dealt with on-premise. Wouldn't want to either, haha. Hopefully someone else here in the community can offer up a solution for you.

[Jonsthan SOUSA]

I don't know if you have found a solution to your issue but I have been in a similar situation as of recently.

We have setup a HTTP proxy to allow our instances to connect to the outer world. For the Update Sources to work we had to add a property called "glide.update_set.remote.check_host" and set it to "true". Afterwards you need to set the value to "false" (only possible to change it through DB) and run a cache.do .

 Hope this is useful to you or anyone else having this issue on On-Premise.