Reserved ports
The following ports are reserved by Blaxel’s system:- 443: This port hosts the main sandbox API and is exposed via HTTPS
- 80: Reserved for system operations
- 8080: Reserved for sandbox API functionality
Expose a port
To whitelist sandbox traffic in your network, you can retrieve the public IP addresses used by Blaxel.
ports parameter. This allows you to access these ports from outside the sandbox via the sandbox API.
You only need to expose ports at sandbox creation time if you plan to access the port via the sandbox API. For access via preview URL, ports are dynamically opened as needed.
Access the sandbox on a specific port
Via the sandbox API
This option requires your request to be authenticated. You can access your sandbox on a specific port through the sandbox API using the following URL format:my-sandbox in workspace abc123: https://sbx-my-sandbox-abc123.us-pdx-1.bl.run/port/3000
Request paths, if any, can be specified after the port number. For example: https://sbx-my-sandbox-abc123.us-pdx-1.bl.run/port/3000/my/api/endpoint
Via a preview URL
Preview URLs provide a simple URL that maps to an internal port of your sandbox. You can either make this URL fully public or secure it with token-based authentication. Generally speaking:- for file and process management in your sandbox, use the sandbox API or SDK.
- to access running applications within the sandbox (such as a NextJS preview server on port 3000), use a preview URL instead.
Via SDK
- sandbox.fetch() (recommended)
- Manual URL (older SDKs)
Available in
@blaxel/core >= 0.2.79 (Node.js) and blaxel >= 0.2.49 (Python).fetch method that handles authentication and proxies requests through the sandbox’s /port/{port} endpoint.Create preview URLs
Expose applications running within the sandbox via a direct preview URL.
