[{"data":1,"prerenderedAt":180},["ShallowReactive",2],{"seo-verification":3,"blog-self-host-selenium-grid-vps-ci-ma-en":6,"promo-bar-likely":135},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"key":7,"data":8},"blog-self-host-selenium-grid-vps-ci-ma-en",{"id":9,"slug":10,"slugs":11,"title":15,"excerpt":16,"readTime":17,"views":18,"isPinned":19,"noindex":19,"publishedAt":20,"updatedAt":21,"category":22,"categories":27,"featuredImage":29,"bgImage":30,"posterImage":31,"relatedSolution":32,"intro":35,"keyPoints":36,"sections":37,"ctaTitle":120,"ctaBody":121,"ctaButton":122,"ctaUrl":123,"relatedPosts":124},590,"self-host-selenium-grid-vps-ci",{"fr":12,"en":10,"ar":13,"es":14},"self-host-selenium-grid-vps","استضافة-selenium-grid-على-vps","autoalojar-selenium-grid-vps","Selenium Grid on a VPS: browser tests for your CI pipelines","Install Selenium Grid on a VPS with Docker Compose: a password-protected remote Chromium, HTTPS behind nginx, and tests wired from your CI.",7,0,false,"2026-11-22T00:00:00+00:00","2026-11-22T18:19:00+00:00",{"id":17,"name":23,"slug":24,"color":25,"icon":26},"Self-hosting","self-hosting","bg-indigo-500\u002F10 text-indigo-400","cloud",[28],{"id":17,"name":23,"slug":24,"color":25,"icon":26},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Fself-host-selenium-grid-vps-poster.svg",{"categorySlug":33,"appSlug":34},"development","selenium-grid","Your end-to-end tests need a real browser. Installing Chrome and its driver on every CI runner costs time on every build, and the version changes from one machine to the next. Selenium Grid solves it differently: a WebDriver server that runs permanently and hands your tests a browser on request. This guide installs it on a VPS with the official docker-selenium image, protects it with a password, publishes it over HTTPS behind nginx and connects Python, JavaScript and GitHub Actions tests to it.",[],[38,42,52,79,82,101,105,108,111,114,117],{"type":39,"title":40,"body":41},"h2","What Selenium Grid does","Selenium Grid is the server of the **Selenium** project, published under the **Apache-2.0** license. It speaks the **WebDriver** protocol standardized by the W3C: a test written in Java, Python, JavaScript, C# or Ruby asks it for a session, the grid starts a browser, runs the commands (open a page, click, fill in a field, read a text) and returns the results.\n\nThe **docker-selenium** project publishes ready-to-use images. The `standalone` image bundles in a single container the **router** (the HTTP entry point), the **session queue** and a **node** that carries the browser. On a VPS it is the simplest form: one container, one port, and no driver to install on the host. Large distributed grids, with a hub and dozens of nodes, use the same images split differently.\n\nUnlike an online testing service billed by the minute, the grid belongs to you: tested pages, test accounts and screenshots stay on your server.",{"type":43,"title":44,"items":45},"ul","What the grid gives you",[46,47,48,49,50,51],"**A stable browser** — all your suites test the same Chromium version, whatever the runner.","**Shorter builds** — no more browser or driver installation on every run.","**A standard endpoint** — any WebDriver client connects to it without changing the test code.","**Parallel sessions** — several tests at once, within the VPS memory.","**A live view** — the grid interface shows the browser while it works.","**A shared grid** — several projects and several CIs can target the same address.",{"type":53,"title":54,"headers":55,"rows":58},"comparison","Chrome installed on the runner or a Selenium grid on your VPS",[5,56,57],"Chrome on every runner","Selenium Grid on your VPS",[59,63,67,71,75],[60,61,62],"Browser installation","On every build","Once, on the server",[64,65,66],"Tested version","Varies from runner to runner","Identical for all suites",[68,69,70],"Runner memory","Shared with the build","Free for the build",[72,73,74],"Watching a test","Screenshots afterwards","Live view in the interface",[76,77,78],"Sharing across projects","Impossible","One address for all",{"type":39,"title":80,"body":81},"Prepare the server","Plan an Ubuntu 24.04 VPS with **2 GB of RAM** and 2 vCPUs: the grid alone uses less than 300 MB at rest, but each Chromium session needs several hundred MB during a test. Move to **4 GB** to sustain two continuous sessions. 10 GB of disk is enough, the image weighs a little over a GB.\n\nInstall Docker with the Compose plugin, nginx and certbot. You also need a domain name (or a subdomain) pointing to the VPS: your pipelines will connect to the grid from outside, over HTTPS. In the examples, the address is `grid.example.com`.",{"type":83,"title":84,"steps":85},"steps","Install Selenium Grid with Docker Compose",[86,89,92,95,98],{"title":87,"body":88},"Prepare the folder and the password","The `.env` file holds the grid's username and password. This password also protects the live view.\n```bash\nmkdir -p \u002Fopt\u002Fselenium-grid && cd \u002Fopt\u002Fselenium-grid\ncat > .env \u003C\u003CEOF\nADMIN_USER=admin\nADMIN_PASSWORD=$(openssl rand -hex 16)\nEOF\nchmod 600 .env\n```",{"title":90,"body":91},"Write the docker-compose.yml file","A single service, the official image with Chromium. `shm_size` gives the browser the shared memory it needs; without it, tabs crash on heavy pages. The port is only published on the loopback: only nginx will be exposed to the Internet.\n```yaml\nservices:\n  selenium:\n    image: selenium\u002Fstandalone-chromium:4.53.0-20261120\n    restart: unless-stopped\n    shm_size: 2gb\n    environment:\n      SE_ROUTER_USERNAME: ${ADMIN_USER:-admin}\n      SE_ROUTER_PASSWORD: ${ADMIN_PASSWORD:?ADMIN_PASSWORD manquant}\n      SE_VNC_PASSWORD: ${ADMIN_PASSWORD:?ADMIN_PASSWORD manquant}\n      SE_NODE_MAX_SESSIONS: \"2\"\n      SE_NODE_OVERRIDE_MAX_SESSIONS: \"true\"\n      SE_NODE_SESSION_TIMEOUT: \"300\"\n    ports:\n      - \"127.0.0.1:4444:4444\"\n```",{"title":93,"body":94},"Start and check the grid","The image ships its own health check: `--wait` returns once the grid is ready. The `\u002Fstatus` page must answer `true`.\n```bash\ndocker compose up -d --wait\n. .\u002F.env\ncurl -s -u \"admin:$ADMIN_PASSWORD\" http:\u002F\u002F127.0.0.1:4444\u002Fstatus | jq .value.ready\n```",{"title":96,"body":97},"Publish the grid behind nginx","The `Upgrade` and `Connection` headers let the live view's websockets through, and the read timeout covers long commands.\n```nginx\nserver {\n    server_name grid.example.com;\n    location \u002F {\n        proxy_pass http:\u002F\u002F127.0.0.1:4444;\n        proxy_http_version 1.1;\n        proxy_set_header Host $host;\n        proxy_set_header Upgrade $http_upgrade;\n        proxy_set_header Connection upgrade;\n        proxy_read_timeout 300s;\n    }\n}\n```",{"title":99,"body":100},"Enable HTTPS","The grid password travels with every request: only expose it over HTTPS. Without credentials, `\u002Fstatus` must answer 401.\n```bash\ncertbot --nginx -d grid.example.com\ncurl -s -o \u002Fdev\u002Fnull -w '%{http_code}\\n' https:\u002F\u002Fgrid.example.com\u002Fstatus\n```",{"type":102,"title":103,"body":104},"tip","Never open the grid without a password","A Selenium grid reachable without authentication is a browser anyone can drive **from your server**: visit sites, fill in forms, get around IP-based filtering. The bots that sweep the Internet look precisely for port 4444. Keep `SE_ROUTER_PASSWORD`, leave the port on `127.0.0.1` and only open nginx's 443 to the public.",{"type":39,"title":106,"body":107},"Connect your tests to the grid","On the test side, only the browser start changes: instead of a local driver, you create a **RemoteWebDriver** pointing to the grid address, credentials included. The rest of the test stays the same. In Python:\n\n```python\nfrom selenium import webdriver\n\noptions = webdriver.ChromeOptions()\ndriver = webdriver.Remote(\n    command_executor=\"https:\u002F\u002Fadmin:PASSWORD@grid.example.com\",\n    options=options,\n)\ndriver.get(\"https:\u002F\u002Fexample.com\")\nprint(driver.title)\ndriver.quit()\n```\n\nIn JavaScript with `selenium-webdriver`, same principle. The Chromium node answers to the browser name `chrome`. Older clients that append `\u002Fwd\u002Fhub` to the address also work, the grid accepts both forms.\n\n```javascript\nconst { Builder } = require(\"selenium-webdriver\");\n\nconst driver = await new Builder()\n  .usingServer(\"https:\u002F\u002Fadmin:PASSWORD@grid.example.com\")\n  .forBrowser(\"chrome\")\n  .build();\n```",{"type":39,"title":109,"body":110},"Run the tests from GitHub Actions or GitLab CI","Keep the password in the CI **secrets** and build the address when the job runs. Your tests read `SELENIUM_URL` instead of starting a local browser:\n\n```yaml\n- name: Tests de bout en bout\n  env:\n    SELENIUM_URL: https:\u002F\u002Fadmin:${{ secrets.SELENIUM_PASSWORD }}@grid.example.com\n  run: pytest tests\u002Fe2e\n```\n\nThe same pattern works for GitLab CI (masked variable), Jenkins (credentials manager) or Gitea Actions. The tested site must be reachable **from the VPS**: a public or password-protected staging environment works, a development server started inside the runner does not, unless you expose it through a tunnel.",{"type":39,"title":112,"body":113},"Watch a session and unblock the grid","The `https:\u002F\u002Fgrid.example.com\u002Fui\u002F` interface lists running sessions. Click a session and then the camera icon to watch the browser; the password asked is the grid's. A test that crashes without calling `quit()` keeps its slot busy until the `SE_NODE_SESSION_TIMEOUT` delay (five minutes here). To free a stuck session right away:\n\n```bash\ncurl -s -u \"admin:$ADMIN_PASSWORD\" http:\u002F\u002F127.0.0.1:4444\u002Fstatus \\\n  | jq '.value.nodes[].slots[] | select(.session != null) | .session.sessionId'\ncurl -s -u \"admin:$ADMIN_PASSWORD\" -X DELETE http:\u002F\u002F127.0.0.1:4444\u002Fsession\u002F\u003Cid>\n```\n\nThe container logs (`docker compose logs -f selenium`) give the cause of a refused session: unknown requested capability, full queue or a browser that does not start.",{"type":39,"title":115,"body":116},"Capacity, memory and other browsers","The configuration above opens **two sessions** in parallel. Beyond that, requests wait in the queue, then fail after `SE_SESSION_REQUEST_TIMEOUT` (300 seconds by default). To scale up, increase the VPS RAM before `SE_NODE_MAX_SESSIONS`: a Chromium short on memory does not slow down, it crashes.\n\nThe `standalone-firefox` and `standalone-edge` images are used exactly the same way; Edge and Google Chrome are only published for x86-64 processors, Chromium and Firefox also exist for ARM. To test several browsers, run one service per image on different ports.",{"type":39,"title":118,"body":119},"Install Selenium Grid in one click from the ServOrbit Marketplace","The ServOrbit Marketplace installs this same configuration on your VPS: official image with Chromium, grid protected by the `admin` user and a generated password, port published on the loopback and nginx reverse proxy over HTTPS. Selenium Grid requires a domain, since your pipelines connect to it from outside: choose a subdomain of one of your domains, or the VPS's free subdomain, HTTPS included. The password is shown in your client area.","Your Selenium grid, on your VPS","A ServOrbit Ubuntu 24.04 VPS with 2 GB of RAM is enough for two parallel Chromium sessions. One-click installation from the Marketplace, generated password and HTTPS included.","Install Selenium Grid","\u002Fapplications\u002Fdevelopment\u002Fselenium-grid",[125,144,162],{"id":126,"slug":127,"slugs":128,"title":132,"excerpt":133,"readTime":17,"views":134,"isPinned":19,"noindex":135,"publishedAt":136,"updatedAt":137,"category":138,"categories":139,"featuredImage":29,"bgImage":30,"posterImage":141,"relatedSolution":142},515,"self-host-jenkins-ci-cd-server-vps",{"fr":129,"en":127,"ar":130,"es":131},"self-host-jenkins-vps","استضافة-jenkins-على-vps-خادم-ci-cd","autoalojar-jenkins-servidor-ci-cd-vps","Jenkins on a VPS: your open-source CI\u002FCD server with Docker","Install Jenkins LTS on a VPS with Docker Compose: Jenkinsfile pipelines, Git webhooks, HTTPS behind nginx and build agents isolated from the controller.",1,true,"2026-10-28T00:00:00+00:00","2026-11-04T16:30:29+00:00",{"id":17,"name":23,"slug":24,"color":25,"icon":26},[140],{"id":17,"name":23,"slug":24,"color":25,"icon":26},"\u002Fblog\u002Fcovers\u002Fself-host-jenkins-vps-poster.svg",{"categorySlug":33,"appSlug":143},"jenkins",{"id":145,"slug":146,"slugs":147,"title":151,"excerpt":152,"readTime":153,"views":134,"isPinned":19,"noindex":19,"publishedAt":154,"updatedAt":155,"category":156,"categories":157,"featuredImage":29,"bgImage":30,"posterImage":159,"relatedSolution":160},74,"host-gitea-on-your-own-vps",{"fr":148,"en":146,"ar":149,"es":150},"heberger-gitea","استضافة-gitea-على-خادم-vps-الخاص-بك","alojar-gitea-en-un-vps","Host Gitea on your own VPS in 2026","Deploy Gitea 1.25 on a VPS with Docker and SSL. Full guide: Gitea Actions CI\u002FCD, Gitea vs Forgejo v16 comparison, daily administration, SSH and HTTPS troubleshooting.",13,"2026-04-07T00:00:00+00:00","2026-11-08T16:32:50+00:00",{"id":17,"name":23,"slug":24,"color":25,"icon":26},[158],{"id":17,"name":23,"slug":24,"color":25,"icon":26},"\u002Fblog\u002Fcovers\u002Fheberger-gitea-poster.svg",{"categorySlug":33,"appSlug":161},"gitea",{"id":163,"slug":164,"slugs":165,"title":169,"excerpt":170,"readTime":171,"views":18,"isPinned":19,"noindex":19,"publishedAt":172,"updatedAt":173,"category":174,"categories":175,"featuredImage":29,"bgImage":30,"posterImage":177,"relatedSolution":178},288,"mailpit-self-hosted-smtp-testing-server-on-your-vps",{"fr":166,"en":164,"ar":167,"es":168},"self-host-mailpit-vps","mailpit-بديل-mailhog-لاختبار-البريد-على-vps","mailpit-servidor-smtp-de-pruebas-vps","Mailpit: self-hosted test SMTP server on your VPS","Deploy Mailpit on your VPS to intercept and inspect test emails. Full guide: Docker Compose, reverse proxy, CI\u002FCD with Laravel, Django and n8n, and troubleshooting.",8,"2026-01-14T00:00:00+00:00","2026-10-14T23:33:30+00:00",{"id":17,"name":23,"slug":24,"color":25,"icon":26},[176],{"id":17,"name":23,"slug":24,"color":25,"icon":26},"\u002Fblog\u002Fcovers\u002Fself-host-mailpit-vps-poster.svg",{"categorySlug":33,"appSlug":179},"mailpit",1795372075156]