Understand blocked internet requests

If code run by a specialist cannot reach a website or API, its internet-access settings may explain why.

Find the refused request

1. Open the specialist’s edit screen.
2. Expand Advanced — system prompt and internet access.
3. Read Blocked requests beneath the access settings.
4. Match the destination and time to the task that failed.

Use the reason to decide what to do

Reason	Meaning	Next step
Internet blocked	Internet access is blocked for this specialist.	Ask an authorised administrator to review whether the task needs internet access.
Domain not selected	The destination is not in the specialist’s selected domains.	Check the hostname. Add it only if it is needed and approved for the task.
Private address	The destination resolves to a protected private, internal, link-local, or metadata address.	Check that the destination is correct. Ask your administrator about intentional access to an internal service.
DNS failure	The destination’s address could not be resolved.	Check the hostname for a typo and confirm that the service is available.

Full internet access still blocks private destinations. It is not a way to enable access to an internal service.

Retry after correcting the cause

Save any approved changes, then ask the specialist to retry the task. If the request fails again, check for a new entry and compare its destination and reason.

An empty blocked-request list does not prove the upstream service is healthy. A connected tool can also fail because of its own permissions, credentials, or an upstream error.

Ask for help

Share the destination hostname, displayed reason, approximate time, and what you were trying to do with your administrator or the Lifter team. Leave out credentials and private customer data.

See Configure a specialist’s internet access for the available access levels.