What Is Already Configured
After a one-click deployment, a Docker container running the open-source Browserless image starts and exposes a WebSocket and REST API on port 3000 inside the container. You can verify that it is working using the built-in endpoints: interactive API documentation is available at /docs, the health check at /pressure, and metrics at /metrics. Container restarts after a failure or host reboot are handled by Docker's restart policy. The specific policy (unless-stopped, always, etc.) used for one-click deployments is determined by the Leneex control panel.
This is how a one-click Browserless deployment works in practice: simply starting the container does not require manual configuration of Chromium, fonts, or dependencies, as these are already included in the image. Storage for downloaded files and browser user data can be attached separately as a volume, if needed.
Initial Access and Authentication Token
Connect to the browser using a URL in the following format: ws://your-domain:port/chromium?token=YOUR_TOKEN.
This works with Puppeteer and Playwright. Alternatively, you can send standard HTTP requests to REST endpoints for screenshots and PDF generation. A token is required for external access; without one, connections should generally be limited to a private network.
What to Check Before Production Workloads
By default, Docker allocates only 64 MB of shared memory to /dev/shm, which is insufficient for Chrome to run reliably under load. Increasing shared memory to at least 2 GB is recommended. If the Leneex control panel does not allow you to increase the container's shm_size through the interface, you will need to apply this setting manually through Docker Compose.