Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Use a pinned Node.js project, run it in a Chrome-ready container, and treat the VPS as a production service rather than a one-off script. The dependable pattern is: validate that collection is permitted, write a scraper with explicit waits and bounded retries, build from a Puppeteer-compatible image, run Chrome with an init process and the required sandbox capability, then add scheduling, secrets, logs, health checks and resource limits.
Antihost offers VPS plans with one-click Docker, NVMe storage and a 14-day free trial.
This guide walks through that pattern and explains when a self-hosted Browserless deployment is a better fit than embedding Chromium in every scraper container.
As an Amazon Associate I earn from qualifying purchases.
Recommended Free Tools
What the finished system looks like
A small deployment has four layers:
- Scraper code: Node.js and Puppeteer navigate to an allowed target, wait for the page state you need, extract structured fields and write a result.
- Browser container: Docker supplies Chrome for Testing, its libraries and a repeatable runtime.
- VPS operations: A scheduler starts jobs, while restart rules, log rotation, a firewall and runtime-injected secrets keep the service maintainable.
- Data and monitoring: Results are persisted outside the disposable container, and a heartbeat or health endpoint exposes failures before a schedule silently stops producing data.
Keep the browser process and the scraper process in the same container for a simple, low-latency job. Move to a remote browser service when several applications need shared sessions, a REST interface or a central queue.
Prerequisites and collection boundaries
Software and host requirements
- Use Node.js 22.12 or newer, the current minimum listed in Puppeteer’s system requirements.
- Choose a 64-bit Linux VPS. Chrome for Testing supports Debian and Ubuntu on x64 and arm64 when the required distribution packages are present.
- Install Docker Engine and Compose (or an equivalent scheduler). Give the VPS enough RAM for the number of simultaneous Chromium pages you intend to run; begin with one worker.
- Reserve persistent storage for results, screenshots and logs. A container filesystem is not a database.
Decide what is allowed before coding
Write down the target domains, fields, request rate, retention period and failure policy. Review the site’s terms, robots guidance, privacy obligations and copyright rules. A proxy can change the network path; it does not grant permission to bypass authentication, paywalls, rate limits or other access controls.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Create a pinned Node project
Start locally so dependency and selector errors are easier to diagnose. The exact Puppeteer release is your compatibility decision; pin it with an exact package version and commit the lockfile after testing it with your chosen Node 22 release.
mkdir puppeteer-vps-scraper
cd puppeteer-vps-scraper
npm init -y
npm install --save-exact puppeteer
npm install --save-exact pino
npm pkg set scripts.start="node src/scrape.js"
mkdir -p src data logsnpm install --save-exact records the selected version instead of a caret range. Run npm ci in the image and in deployments so the lockfile, rather than a fresh dependency resolution, determines what is installed. Check that the selected Puppeteer release supports Node 22.12 or newer before committing.
A scraper with waits, validation and cleanup
The following example reads a URL from an environment variable, waits for a meaningful selector, extracts a list, retries transient navigation failures with backoff, emits JSON logs and always closes the browser. Replace the selector and fields with ones permitted for your target.
const http = require('node:http');
const fs = require('node:fs/promises');
const pino = require('pino');
const puppeteer = require('puppeteer');
const log = pino({ level: process.env.LOG_LEVEL || 'info' });
const targetUrl = process.env.TARGET_URL;
const outputFile = process.env.OUTPUT_FILE || '/app/data/latest.json';
const selector = process.env.ITEM_SELECTOR || 'article';
const maxAttempts = Number(process.env.MAX_ATTEMPTS || 3);
const navigationTimeout = Number(process.env.NAVIGATION_TIMEOUT_MS || 30000);
let lastSuccess = 0;
if (!targetUrl) throw new Error('TARGET_URL is required');
const sleep = ms => new Promise(resolve => setTimeout(resolve, ms));
async function scrapeOnce(browser) {
const page = await browser.newPage();
await page.setDefaultNavigationTimeout(navigationTimeout);
await page.setDefaultTimeout(navigationTimeout);
try {
await page.goto(targetUrl, { waitUntil: 'domcontentloaded' });
await page.waitForSelector(selector, { visible: true });
const rows = await page.$$eval(selector, nodes => nodes.map(node => ({
title: node.querySelector('h2,h3')?.textContent?.trim() || null,
text: node.textContent?.trim() || ''
})));
if (!rows.length) throw new Error('selector returned no records');
return { fetchedAt: new Date().toISOString(), url: targetUrl, rows };
} finally {
await page.close();
}
}
async function run() {
const browser = await puppeteer.launch({
headless: true,
args: ['--disable-dev-shm-usage']
});
try {
let result;
for (let attempt = 1; attempt <= maxAttempts; attempt++) {
try {
result = await scrapeOnce(browser);
break;
} catch (error) {
log.warn({ attempt, err: error }, 'scrape attempt failed');
if (attempt === maxAttempts) throw error;
await sleep(1000 * 2 ** (attempt - 1));
}
}
await fs.writeFile(outputFile, JSON.stringify(result, null, 2));
lastSuccess = Date.now();
log.info({ count: result.rows.length, outputFile }, 'scrape completed');
} finally {
await browser.close();
}
}
const server = http.createServer((req, res) => {
if (req.url === '/healthz' && lastSuccess) {
res.writeHead(200, { 'content-type': 'application/json' });
return res.end(JSON.stringify({ ok: true, lastSuccess }));
}
if (req.url === '/healthz') {
res.writeHead(503, { 'content-type': 'application/json' });
return res.end(JSON.stringify({ ok: false }));
}
res.writeHead(404);
res.end();
});
server.listen(Number(process.env.PORT || 8080), '0.0.0.0');
run().catch(error => {
log.error({ err: error }, 'scrape failed');
process.exitCode = 1;
});The --disable-dev-shm-usage flag makes Chrome use temporary disk space instead of the container’s shared-memory mount. It can prevent crashes on small defaults, but it may be slower than allocating adequate shared memory; treat it as a fallback, not a substitute for capacity planning. In a read-only container, provide writable temporary and profile locations or Chrome will fail while creating files.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Make extraction resilient
- Wait for the selector or a network condition that represents the data, not an arbitrary sleep.
- Validate required fields and record the page URL and fetch timestamp with every row.
- Capture an HTML file or screenshot on final failure, but enforce a retention limit so diagnostics cannot fill the disk.
- Use per-target rate limits and a single browser page at first. Add concurrency only after measuring CPU, RAM, network and target responses.
- Close pages after each task and close the browser on
SIGTERM; an init process also reaps child processes when the container stops.
Choose and build the Docker image
Official Puppeteer image
Puppeteer publishes an image containing Chrome for Testing, its dependencies and a pre-installed Puppeteer version. It is designed for Chrome’s sandbox, so the documented run pattern grants the SYS_ADMIN capability and uses --init:
docker run -i --init --cap-add=SYS_ADMIN --rm ghcr.io/puppeteer/puppeteer:latest node -e "console.log('browser image ready')"For production, replace latest with a tested image tag and keep the application dependency aligned with the browser version in that tag. The capability is broader than an ordinary application needs; isolate the container, expose no Docker socket and avoid adding unrelated capabilities.
Custom Debian or Ubuntu image
A custom image is useful when you need your own Node patch level, OS packages, non-root user, or a small application layer. Install the distribution libraries required by Chrome for Testing, copy the lockfiles first for build caching, run npm ci, and then copy source code.
FROM node:22-bookworm-slim
WORKDIR /app
ENV NODE_ENV=production
PUPPETEER_CACHE_DIR=/home/pptruser/.cache/puppeteer
TMPDIR=/tmp
COPY package*.json ./
RUN npm ci --omit=dev
COPY src ./src
RUN mkdir -p /app/data /app/logs /home/pptruser/.cache
&& chown -R node:node /app /home/pptruser
USER node
EXPOSE 8080
ENTRYPOINT ["/usr/bin/tini", "--"]
CMD ["node", "src/scrape.js"]This skeleton assumes you add tini and every Chrome library required by your selected Puppeteer configuration in the image build. If Puppeteer downloads Chrome during npm ci, retain the cache in the final image; if you use a system browser, set and test its executable path explicitly. Do not mix an arbitrary Chrome binary with an untested Puppeteer release.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Build and run locally
docker build --tag vps-scraper:1.0.0 .
docker run --rm --init --cap-add=SYS_ADMIN
--shm-size=2g
--env TARGET_URL=https://example.invalid/catalog
--env ITEM_SELECTOR='.product-card'
--env OUTPUT_FILE=/app/data/latest.json
--publish 8080:8080
--volume "$PWD/data:/app/data"
vps-scraper:1.0.0Use a real permitted URL in your environment, not in source control. The published port is only needed for the health endpoint; bind it to localhost or a private interface unless an authenticated reverse proxy is in front of it.
Deploy on a Linux VPS
Compose service with conservative limits
services:
scraper:
image: vps-scraper:1.0.0
init: true
cap_add:
- SYS_ADMIN
shm_size: "2g"
restart: unless-stopped
env_file:
- .env
volumes:
- ./data:/app/data
- ./logs:/app/logs
ports:
- "127.0.0.1:8080:8080"
pids_limit: 256
mem_limit: 2g
cpus: 1.0
read_only: true
tmpfs:
- /tmp:size=512m
- /home/node/.cache:size=512mThe memory, CPU and temporary-space values are starting limits, not universal sizing rules. Observe the process under a representative workload and adjust. A read-only root filesystem improves containment but requires writable mounts for data, browser cache, profiles and temporary files.
Firewall and secrets
- Allow SSH only from trusted addresses or through a private network; expose the scraper health port on localhost or an internal network.
- Do not mount
/var/run/docker.sockinto the scraper. Access to that socket is effectively host-level control. - Store credentials, cookies and API keys in a root-readable environment file outside the repository or in the VPS secret manager. Set restrictive file permissions and rotate them.
- Inject
TARGET_URL, selectors and credentials at runtime. Never bake secrets into an image layer or log them. - Patch the host and Docker engine, and pin image digests or tested tags so an unattended pull cannot silently change the browser.
Scheduling choices
For one periodic job, a host cron entry is easy to audit:
15 * * * * cd /srv/puppeteer-vps-scraper && /usr/bin/docker compose run --rm scraper >> /var/log/scraper-cron.log 2>&1For a long-lived health endpoint, keep the service running with restart: unless-stopped and let the application trigger work on a timer, or use a systemd timer that invokes a one-shot Compose task. Prevent overlap: acquire a lock or enqueue a job so a slow run cannot create two browsers for the same target.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Logs and persistence
Emit one JSON event per attempt with target, duration, status and error class. Configure Docker’s json-file logging driver with rotation or forward logs to the host’s journald. Keep result files on a versioned volume, write atomically to a temporary file and rename after validation, and define how long screenshots and raw HTML remain available.
Shared memory, crashes and other failure modes
Chrome exits with a “no usable sandbox” or permission error
Run the official image with --cap-add=SYS_ADMIN and --init, as its Docker guide specifies. Confirm that your custom image includes an init binary and that the container is not stripping the sandbox unexpectedly. Avoid the unsafe habit of adding --no-sandbox unless you have deliberately accepted the isolation loss and documented why.
Chrome crashes under load
Docker’s default shared-memory mount is 64 MB. Browserless documents that this can crash Chrome under load and recommends a 2 GB setting in Compose or --shm-size=2g on the command line. Increase it only alongside RAM monitoring; shared memory is part of the host’s available memory. Lower page concurrency, close unused pages and cap navigation time if the VPS cannot sustain that size.
Zombie processes accumulate
Use Docker’s --init flag or a tiny init such as dumb-init/tini, and close every page and browser in finally blocks. Inspect process counts and restart the service after a failed run rather than allowing orphaned Chromium children to consume the VPS.
Navigation times out or returns empty data
- Check DNS, outbound firewall rules and the target’s response status from inside the container.
- Replace fixed sleeps with a selector, a specific response wait or a documented application-ready condition.
- Save a failure screenshot and HTML snapshot, then inspect whether the page requires JavaScript, a login, a region, or an interaction your script does not implement.
- Use exponential backoff for transient 5xx responses, but stop retrying authorization failures, persistent 4xx responses or a robots/terms prohibition.
Read-only mode causes profile or temporary-file errors
Mount writable directories for /tmp, the Puppeteer cache and any user-data directory. Keep those paths on ephemeral storage unless you intentionally need a persistent browser profile; persistent profiles can contain cookies and other sensitive data.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteHealth, queueing and safe scaling
A process that is “running” can still be unusable. Probe /healthz from the host or a private monitor, and make the endpoint fail when no successful job has occurred within the expected interval. Include last-success time, queue depth and the most recent error class in an authenticated diagnostic endpoint rather than returning scraped data.
Before adding workers, define:
- Concurrency: maximum simultaneous pages and browsers, derived from CPU and memory measurements.
- Queue length: a finite backlog so an outage does not create unbounded RAM use.
- Timeout: a deadline for navigation and the whole job.
- Retry budget: attempts per target and a delay schedule.
- Backpressure: what happens when the queue is full—reject, delay or drop the oldest permitted job.
Persist job status outside the worker if losing an in-memory queue would lose business-critical results. Add idempotency keys so a retry cannot duplicate a record.
Embedded Puppeteer or Browserless self-hosting?
Both approaches can run on a VPS. Embedded Puppeteer keeps browser control beside the scraper and has fewer moving parts. Browserless provides open-source images for Chromium, Chrome, Firefox, WebKit and Edge, plus Puppeteer WebSocket connectivity, REST APIs, health checks, sessions and a debugger. Choose based on the operational boundary, not on a promise that one option bypasses site controls.
| Decision area | Embedded Puppeteer container | Browserless self-hosted |
|---|---|---|
| Image maintenance | You maintain the application image and align its browser dependencies. | You maintain the Browserless image and its configuration, while clients can remain browser-agnostic. |
| Version control | Direct control of the Puppeteer package, Chrome build and lockfile. | Browser version is controlled by the selected Browserless image; pin and test its tag. |
| Sandbox and privilege | Configure SYS_ADMIN, init and writable paths in each worker. |
Configure those container requirements once for the browser service, then connect clients remotely. |
| Shared memory | Set shm_size per scraper container and size it for its concurrency. |
Set it on the central service; Browserless warns that Docker’s 64 MB default can crash Chrome and shows 2 GB as a Compose setting. |
| Concurrency and queues | You implement worker limits, queueing, timeouts and backpressure. | Configuration includes CONCURRENT, QUEUED and TIMEOUT; adapt values to VPS resources and target limits. |
| Authentication | Protect your own API or scheduler and keep secrets out of images. | Set TOKEN before exposing the service. Without it, every endpoint is unauthenticated, including /function, which executes Puppeteer code supplied in a request. |
| Observability | Add your own health endpoint, logs, screenshots and metrics. | Health checks, sessions and a debugger are available as part of the service, while application-level result checks remain your responsibility. |
| API surface | Best for one codebase calling Puppeteer directly. | Useful when several languages or teams need a common WebSocket or REST browser endpoint. |
| Proxy features | Bring and secure a proxy client yourself, subject to permission and provider terms. | Documentation describes residential routing at 6 units per MB and datacenter routing at 2 units per MB, with country, city and sticky-session options; these vendor units and prices can change. |
| Operating cost | Fewer services and potentially lower baseline resource use, but you own every reliability feature. | One shared browser service can reduce duplicated maintenance, while its extra memory, queue and security surface must be operated and paid for. |
The open-source Browserless image does not include stealth or CAPTCHA solving, and advanced unblock routes and managed proxies are cloud or enterprise features. Do not treat self-hosting it as authorization to defeat access controls.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Production launch checklist
- Confirm the target, fields, rate, retention and legal basis in writing.
- Verify Node 22.12 or newer and the supported Debian/Ubuntu architecture.
- Pin Puppeteer exactly, commit the lockfile and test the matching browser image.
- Exercise selectors, timeouts, retries, validation and graceful browser shutdown locally.
- Build a tagged image; scan it and keep Chrome’s cache and dependencies consistent.
- Run with an init process, the sandbox capability required by the chosen image, writable temporary paths and a deliberate shared-memory size.
- Mount persistent result storage, rotate logs and inject secrets at runtime.
- Lock down SSH and application ports, and never expose the Docker socket.
- Set one worker, finite queue and conservative timeout first; watch CPU, RAM,
/dev/shm, network and target responses. - Add a heartbeat, alert on missed runs, and document recovery steps before increasing concurrency.
- If multiple clients need remote sessions or a standard API, evaluate Browserless and set its token before any non-local exposure.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
