No egress policy is in force for your org

Code: egress.no_bundle

What happened

No signed policy is in force for the box’s org in its cell, so the proxy allows the box no destination.

Awake’s answer says:

no policy bundle is in force for this box's org, so the egress proxy allows it no destination

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

Try again in a few minutes. If it lasts, ask your Awake admin to contact Awake support.

What your admin can do

In the console, an Org admin opens Admin → Policies → Versions and cells.

There, Versions and cells shows which version of your org’s policy each cell holds. If the Audit log shows a version of your org’s policy refused because the proxy couldn’t enforce it, boxes in that cell are refused with this code until a version the proxy can enforce is in force. Ask Awake support, with the version’s number.

For agents

Try again once, after a short wait. If it fails again, tell the person what failed, with this code. Don’t try another host, encoding or route to get around a control.

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.

egress.no_class: Your org’s policy gives this box no egress
egress.unknown_source: The proxy doesn’t know this box yet

Still stuck

Your Awake admin can ask Awake support. Give them the code, egress.no_bundle, and when it happened.