Network and egress

Problems with blocked hosts and network policies. A space can only reach the hosts its network policy allows. Each package adds the hosts it needs. For the operator side of networking, see Networking and egress.

A request is blocked by network policy

You see: blocked by Marshal Platform network policy: host not in session allowlist

Cause: The space tried to reach a host that its network policy does not allow. Marshal returns a 403 for the request. Tools often show it as a failed CONNECT or a 403 Forbidden.

Fix: Pick one of these.

Add the package that covers the host to the stack. For example, egress-dockerhub allows pulls from Docker Hub.
Ask an admin to allow the host in the network policy that the stack uses. Admins edit policies on the Network policies page. They add a rule with the action allow for the host. Traffic that no rule matches follows the policy’s default action, which is deny unless an admin changed it.

Then create a new space. The Audit page shows blocked requests. Filter by status Blocked to find the host.

Editor cannot connect over Remote-SSH

Cause: The editor must download its server into the space and reach its own services. Those hosts are blocked unless the stack allows them.

Fix: Add the egress package for your editor to the stack: egress-vscode, egress-cursor, egress-copilot, or egress-windsurf. These packages contain only allow-lists. They add no tools and no credentials. Create a new space.

Blocked: unrecognized secret placeholder

You see: blocked by Marshal http_secrets: unrecognized secret placeholder

Cause: The request carried a Marshal secret placeholder that is not tied to any active credential in this space. Marshal blocked it rather than send a token that cannot work. A common cause is that the credential was removed or swapped while a process still held the old placeholder. Another is a placeholder for a field the agent is never meant to send.

Fix: Start a new space so the process gets the current placeholders. Use each placeholder only where Marshal put it.

Blocked: possible secret leak

You see: blocked by Marshal http_secrets: possible secret-exfiltration attempt

Cause: The request would have sent a live secret to a host that the secret is not allowed for. Marshal treats this as a possible leak and blocks it.

Fix: If the destination is wrong, fix the command. If the destination is correct, ask an admin to add the host to the allowed hosts of that credential.

A network policy cannot be deleted

You see: Cannot delete the default policy or Policy in use

Cause: The organization’s default policy stays in place, and you can edit its rules. A policy that stacks use shows Policy in use, with the number of stacks that use it as their baseline.

Fix: For a policy in use, reassign those stacks to another policy, then delete. Only admins can delete policies.