Skip to content
Awake docs

The proxy doesn't connect to IP addresses

Code: egress.ip_literal

What happened

Section titled “What happened”

The request named an IP address instead of a host, and the proxy never connects to one.

Awake’s answer says:

the egress proxy never connects to an IP address: name the host

Why Awake does this

Section titled “Why Awake does this”

Every request a box sends leaves through the Egress Proxy, outside the box, which allows only what your org’s policy names and refuses the rest. The Egress Proxy says more.

What you can do

Section titled “What you can do”

Use the host’s name instead of its IP address.

Name the host the address belongs to: https://api.example.com/, not https://203.0.113.7/. Destinations are hosts, so an address matches none of them.

What your admin can do

Section titled “What your admin can do”

Nothing in the console allows a request to an IP address. It’s one of Awake’s guardrails, the same in every org.

For agents

Section titled “For agents”

Tell the person what was refused and why, with this code, and don’t retry in a loop. Don’t try another host, encoding or route to get around a control.

Where Awake records it

Section titled “Where Awake records it”

The Egress Proxy records each refusal, never the request’s data. Org admins and security auditors read the records in the Audit log.

Section titled “Related codes”

Still stuck

Section titled “Still stuck”

Ask your Awake admin. Give them the code, egress.ip_literal, and when it happened.