8 replies

Using a browser on a VPS

✅Solved

Which option is best to give Clawdbot browser access on a VPS - or is there another way @Molty

message.txt4.84KB

Solution

node - <<'NODE'
const { chromium } = require('playwright');
(async () => {
  const browser = await chromium.launch({ 
    headless: true,
    args: ['--no-sandbox', '--disable-dev-shm-usage']
  });
  const page = await browser.newPage();
  await page.goto('https://example.com');
  console.log('✅ Title:', await page.title());
  await browser.close();
})();
NODE

node - <<'NODE'
const { chromium } = require('playwright');
(async () => {
  const browser = await chromium.launch({ 
    headless: true,
    args: ['--no-sandbox', '--disable-dev-shm-usage']
  });
  const page = await browser.newPage();
  await page.goto('https://example.com');
  console.log('✅ Title:', await page.title());
  await browser.close();
})();
NODE

The

--no-sandbox

--no-sandbox

flag is essential in Docker/containers because the nested container environment doesn't handle Chrome's sandbox properly. This is expected behavior, not a bug.

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•2mo ago•

8 replies

Ethan Tan

Using a browser on a VPS

✅Solved

Which option is best to give Clawdbot browser access on a VPS - or is there another way @Molty

message.txt4.84KB

Solution

node - <<'NODE'
const { chromium } = require('playwright');
(async () => {
  const browser = await chromium.launch({ 
    headless: true,
    args: ['--no-sandbox', '--disable-dev-shm-usage']
  });
  const page = await browser.newPage();
  await page.goto('https://example.com');
  console.log('✅ Title:', await page.title());
  await browser.close();
})();
NODE

node - <<'NODE'
const { chromium } = require('playwright');
(async () => {
  const browser = await chromium.launch({ 
    headless: true,
    args: ['--no-sandbox', '--disable-dev-shm-usage']
  });
  const page = await browser.newPage();
  await page.goto('https://example.com');
  console.log('✅ Title:', await page.title());
  await browser.close();
})();
NODE

The

--no-sandbox

--no-sandbox

flag is essential in Docker/containers because the nested container environment doesn't handle Chrome's sandbox properly. This is expected behavior, not a bug.

Jump to solution

Using a browser on a VPS

Similar Threads

Using a browser on a VPS

Similar Threads

Similar Threads

Similar Threads