The path isn't allowed on this destination
Code: egress.path_not_allowed
What happened
Section titled “What happened”The destination is allowed, but not the request’s path.
Awake’s answer says:
the box's egress policy doesn't allow this path on this 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”Use a path the destination allows, or ask your Awake admin to allow this one.
What your admin can do
Section titled “What your admin can do”In the console, an Org admin opens Admin → Policies → Destinations.
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.method_not_allowed: The method isn’t allowed on this destinationegress.not_allowed: The destination isn’t allowed
Still stuck
Section titled “Still stuck”Ask your Awake admin. Give them the code, egress.path_not_allowed, and when it happened.