### Agent Diagnostic I followed the example from this link: https://github.com/NVIDIA/OpenShell/tree/main/examples/sandbox-policy-quickstart but it has not been working successfully. The logs show the following. ### Description I configured a policy like this: ``` network_policies: code_hub: name: code_read_write endpoints: - host: 218.11.11.225 port: 80 protocol: rest enforcement: enforce access: read-only binaries: - { path: /usr/bin/curl } ``` Then I ran: ``` sandbox@demo:~$ curl -v 218.11.11.225:80 * Uses proxy env variable no_proxy == '127.0.0.1,localhost,::1' * Uses proxy env variable http_proxy == 'http://10.200.0.1:3128' * Trying 10.200.0.1:3128... * Connected to 10.200.0.1 (10.200.0.1) port 3128 > GET http://218.11.11.225/ HTTP/1.1 > Host: 218.11.11.225 > User-Agent: curl/8.5.0 > Accept: */* > Proxy-Connection: Keep-Alive > < HTTP/1.1 403 Forbidden * no chunk, no close, no size. Assume close to signal end < * Closing connection ``` The logs are as follows: ``` [1774352985.070] [sandbox] [INFO ] [openshell_sandbox::proxy] FORWARD action=deny binary=/usr/bin/curl dst_host=218.11.11.225 dst_port=80 method=GET path=/ policy=code_hub reason=endpoint has L7 rules; use CONNECT ``` I guess I’m using it incorrectly. How should I use the L7 policy? ### Reproduction Steps 1. openshell sandbox create --name demo 2. vim policy 3. openshell policy set demo --policy policy.yaml --wait 4. openshell sandbox connect demo 5. curl -v 218.11.11.225:80 ``` * Uses proxy env variable no_proxy == '127.0.0.1,localhost,::1' * Uses proxy env variable http_proxy == 'http://10.200.0.1:3128' * Trying 10.200.0.1:3128... * Connected to 10.200.0.1 (10.200.0.1) port 3128 > GET http://218.11.11.225/ HTTP/1.1 > Host: 218.11.11.225 > User-Agent: curl/8.5.0 > Accept: */* > Proxy-Connection: Keep-Alive > < HTTP/1.1 403 Forbidden * no chunk, no close, no size. Assume close to signal end < * Closing connection ``` ### Environment - linux ### Logs ```shell ``` ### Agent-First Checklist - [x] I pointed my agent at the repo and had it investigate this issue - [x] I loaded relevant skills (e.g., `debug-openshell-cluster`, `debug-inference`, `openshell-cli`) - [x] My agent could not resolve this — the diagnostic above explains why
Activity
chinazj commentedon Mar 24, 2026
use connect
log
timosur commentedon Mar 24, 2026
I am experiencing the same issue.
Have this policy here in place:
getting following error when doing a curl:
johntmyers commentedon Mar 24, 2026
Since you are both using using IP addresses directly, try doing this for your policies:
fix(sandbox): treat literal IP in policy host as implicit allowed_ips
johntmyers commentedon Mar 24, 2026
I've created #570 which will remove the need to add a redundant
allowed_ipssection in the policy.fix(sandbox,server): fix chunk merge duplicates and OPA variable coll…
test(e2e): add overlapping policy tests and update FWD-2 for implicit…
timosur commentedon Mar 24, 2026
@johntmyers Thank you for this quick fix, worked for me! :-) Also great idea to remove this redundant
allowed_ips!fix(sandbox): treat literal IP in policy host as implicit allowed_ips (…
fix(sandbox,server): fix chunk merge duplicates and OPA variable coll…
test(e2e): add overlapping policy tests and update FWD-2 for implicit…
johntmyers commentedon Mar 24, 2026
I will close this issue. Let us know if it happens again.
fix(sandbox,server): fix chunk merge duplicates and OPA variable coll…