Skip to content
AutomatedOn Help Centre

Why won't AutomatedOn connect to an internal address?

Updated 19 October 2026 · For back office users

For security, AutomatedOn won't connect to private or internal network addresses. This protects your tenant and Three 17's hosting if a URL is mistyped or misused. It applies to data sources, API requests, token endpoints and message sending.

What's blocked

AutomatedOn checks the address a web address actually points to, not just the text you typed. It refuses to connect when the only addresses are:

  • your own machine (loopback), such as localhost or 127.0.0.1
  • private network ranges: 10.x.x.x, 172.16.x.x to 172.31.x.x and 192.168.x.x
  • link-local addresses, 169.254.x.x, including cloud metadata services
  • 0.x.x.x addresses
  • the equivalent private and link-local IPv6 ranges

What you'll see

The error says AutomatedOn is refusing to connect because the address resolves only to a private, loopback or link-local address. You might see it in Test Connection, a dataset's Preview tab, or a process's history.

Related safeguard for REST APIs

When a REST dataset follows next-page links, it only follows links on the same host as the data source's Base URL, so your credentials are never sent to another site. If a link points elsewhere, you'll see Refusing to follow the next page link to '...': it isn't on the data source's host.

What to do

  • Check the URL for typos.
  • Use the system's public address. The system you're connecting to must be reachable from the internet.
  • If you're not sure which address to use, ask the system's supplier or Three 17 support.

Was this guide helpful?