Skip to content
Awake docs

The destination took too long to answer

Code: egress.upstream_timeout

What happened

Section titled “What happened”

The destination didn’t answer the proxy in time.

Awake’s answer says:

the egress proxy waited too long for this destination to answer: try again

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”

Try again. If it keeps happening, the destination may be slow or down.

What your admin can do

Section titled “What your admin can do”

Nothing in the console changes this.

For agents

Section titled “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

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”

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