Skip to content
Awake docs

A secret's placeholder was sent where the secret isn't added

Code: egress.placeholder_elsewhere

What happened

Section titled “What happened”

A request carried a secret’s placeholder toward a host or path the secret isn’t added on.

Awake’s answer says:

this request carries a secret's placeholder toward a host or path the secret isn't added on, so the egress proxy refused it

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”

Add the host to the secret in Secrets, or point your tool at a host the secret is for.

In the console: Secrets.

A secret’s placeholder is swapped for its value only on the hosts and paths the secret is added on. In Secrets, add the host your tool sends it to, if that’s where the secret belongs. If it isn’t, point your tool at the host the secret is for.

What your admin can do

Section titled “What your admin can do”

Nothing in the console changes this.

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.

Section titled “Related codes”

Still stuck

Section titled “Still stuck”

Ask your Awake admin. Give them the code, egress.placeholder_elsewhere, and when it happened.