Skip to content
Awake docs

Your org's exceptions refuse this host

Code: egress.exception

What happened

Section titled “What happened”

The org’s exceptions, its own deny list, refuse the host, whatever else allows it.

Awake’s answer says:

your organization's policy refuses this host, whatever else allows it

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”

Ask your Awake admin, who manages your org’s exceptions.

Your org can keep a list of exceptions: hosts, or every host under a domain such as *.example.com, that it refuses whatever else allows them. An exception wins over Awake’s own sets, your org’s destinations and an approved request alike, so asking for the host in Requests won’t open it. If your work needs the host, tell your Awake admin which one, and why.

What your admin can do

Section titled “What your admin can do”

Only an Org admin adds or removes an exception, as part of the org’s policy. To let boxes reach the host again, an Org admin removes the exception that covers it, or replaces a wildcard exception with narrower ones, then publishes the policy. The console doesn’t show exceptions yet, so for now an Org admin changes them through Awake’s API.

If none of your org’s exceptions covers the host, Awake may not hold exceptions by name yet where your box runs. Until it does, the proxy may refuse with this code what it can’t tell apart from an excepted host: every host under a wildcard destination that covers an exception, and hosts your org’s policy doesn’t name. Your admin can ask Awake support when that ends.

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.exception, and when it happened.