docs(network): ports to keep open when running a firewall inside a sandbox - #338
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
beran-t
force-pushed
the
docs/network-default-private-range-blocking
branch
from
August 7, 2026 15:25
0c257d6 to
c0187de
Compare
beran-t
force-pushed
the
docs/network-default-private-range-blocking
branch
from
August 7, 2026 15:33
c0187de to
8e85369
Compare
beran-t
marked this pull request as ready for review
August 7, 2026 15:37
beran-t
marked this pull request as draft
August 7, 2026 15:44
beran-t
force-pushed
the
docs/network-default-private-range-blocking
branch
from
August 7, 2026 15:49
8e85369 to
b8b0844
Compare
beran-t
changed the title
beran-t
marked this pull request as ready for review
August 7, 2026 15:49
beran-t
changed the title
beran-t
force-pushed
the
docs/network-default-private-range-blocking
branch
from
August 7, 2026 15:54
b8b0844 to
5bc224e
Compare
beran-t
force-pushed
the
docs/network-default-private-range-blocking
branch
from
August 7, 2026 16:05
5bc224e to
73be61f
Compare
beran-t
changed the title
beran-t
force-pushed
the
docs/network-default-private-range-blocking
branch
from
August 10, 2026 08:53
73be61f to
37b14f4
Compare
tvi
approved these changes
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a "Running a firewall inside the sandbox" section to the Restricting public access page. If you run
iptablesinside a sandbox, it lists what must stay open so the sandbox keeps talking to the SDK:lo) traffic.49983(the envd control channel).49999, if you use the Code Interpreter template.Why
A customer's template build failed repeatedly because a start-command
iptablesscript dropped traffic on link-local / private ranges, which severed the sandbox's own control channel (thread T-7578). The docs never said which ports a guest-side firewall must preserve. This turns that into concrete, followable guidance rather than a blanket "do not do it".Verified
Ports are source- and live-verified (via the e2b-engineer subagent against
e2b-dev/infra, the SDKs, and the code-interpreter template):49983is the single envd port (packages/envd/main.go:38,299,packages/shared/pkg/consts/envd.go:4) - every SDK op and public-URL proxying goes through it.49999(JUPYTER_PORT, JSconsts.ts/ Pythonconstants.py; templatestart-up.sh) and proxies to Jupyter onlocalhost:8888, so loopback must stay open. Live repro: under a guest INPUT drop policy allowing only49983,commands.runworks butrunCodetimes out until49999is allowed.House style respected (no em dashes or semicolons in the added prose). Editing existing pages already wired in nav; no
docs.jsonchange.mintlify devnot run (known macOSENAMETOOLONGcrash per the docs-pr skill reference).