Upgraded connections aren't allowed to this destination
Code: egress.upgrade_not_allowed
What happened
Section titled “What happened”The destination takes no upgraded connections, such as a WebSocket.
Awake’s answer says:
the box's egress policy doesn't allow upgraded connections to 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”Ask your Awake admin to allow upgraded connections to this destination.
Over plain HTTP, such as a ws:// URL, the proxy never upgrades a connection, whatever the destination allows: use wss:// or https instead.
What your admin can do
Section titled “What your admin can do”In the console, an Org admin opens Admin → Policies → Destinations.
There, a destination takes upgraded connections over https when every method on it is allowed, or when it’s tunneled.
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.plain_http: Plain HTTP was refused
Still stuck
Section titled “Still stuck”Ask your Awake admin. Give them the code, egress.upgrade_not_allowed, and when it happened.