Your org's policy gives this box no egress
Code: egress.no_class
What happened
Section titled “What happened”The org’s policy gives the box no egress, so the proxy allows it no destination.
Awake’s answer says:
this box's org's policy gives it no egress, so the egress proxy allows it no destinationWhy 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 sets what your box may reach.
What your admin can do
Section titled “What your admin can do”In the console, an Org admin opens Admin → Policies → Access.
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.
Related codes
Section titled “Related codes”egress.no_bundle: No egress policy is in force for your orgegress.not_allowed: The destination isn’t allowed
Still stuck
Section titled “Still stuck”Ask your Awake admin. Give them the code, egress.no_class, and when it happened.