Skip to main content
Start a server in the background, then expose its listening port:
Open the printed URL in your browser. It serves your application once the server is listening. The URL uses HTTPS even though the example server listens on HTTP inside the sandbox.

Configure your application

Make your server listen on 0.0.0.0, and pass that same port to expose(). Keep long-lived servers in the background so starting one does not block your SDK call. Anyone with the URL can reach the service. Add authentication in your application before using the endpoint for private data or actions. The endpoint supports HTTP/1.1 and HTTP/2. HTTP/1.0 requests receive 426.

Check a server that does not respond

Read the application’s log:
Check that the process is running and listening on the port you exposed. If the sandbox is paused or archived, resume or unarchive it before trying again. A server keeps its sandbox awake while active. After archive/unarchive, keep using the same URL, but allow a brief reconnect period. Existing network connections need to be established again.

Remove the endpoint

Remove public access without deleting the sandbox:
You can inspect a sandbox’s endpoints in the console or with GET /vms/{id}/ingress. When you no longer need the server or its sandbox:
Deleting the sandbox also makes its endpoints unavailable. Clients may take up to about 30 seconds to receive a failed connection rather than wait for a response.