[BUG] - Error: Failed to download chromium ETIMEDOUT, cannot install

See original GitHub issue

Context:

  • Playwright Version: 1.8.0
  • Operating System: Linux
  • Node.js version: 14
  • Browser: Chromium
  • CI Platform: Azure DevOps
  • Location: UK

Apologies, this is unrelated to the Playwright codebase but wouldn’t know where to go otherwise, I’m running an NPM install to grab Chromium from within a bionic:playwright container using Azure DevOps and it’s returning a timeout when trying to download the executable.

Error: Failed to download chromium, caused by deasync@0.1.20 install /__w/1/s/investor-zone/node_modules/deasync Error: connect ETIMEDOUT 13.107.246.13:443

Browsing to the URL yields: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>08oImYAAAAABLHLg5vDiFR72GN1/9tBvdTUFOMzBFREdFMDcyMQBFZGdl

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:2
  • Comments:9 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
thebibcommented, Feb 16, 2021

So this only seems to be occurring in an Azure Pipeline, Locally it’s fine.

The URL the pipeline would be trying to download from would be: https://playwright.azureedge.net/builds/chromium/844399/chromium-linux.zip

This works fine locally. Browsing to the IP Address directly is what returns that message. However doing a nslookup on ‘https://playwright.azureedge.net’ with the IP you get back also comes back with the same error page.

image

I’m now thinking because of that this might be an networking issue out of Azure DevOps. I’m investigating this now. I will update this when I’ve run some tests on the build agents.

1reaction
jonathanpmartinscommented, Jun 16, 2021

Same problem here trying to install the latest version (1.12.2) with NPM. yarn add playwright doesn’t work as well!

This is bad for new users, they will try to install playwright following the docs npm i -D playwright, and it will not work.

The error that I encounter was the following:

npm ERR! command failed
npm ERR! command sh -c node install.js
npm ERR! (node:22337) UnhandledPromiseRejectionWarning: Error: Failed to download chromium, caused by
npm ERR! Error: connect ETIMEDOUT 13.107.246.33:443
npm ERR!     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)

Is this out of service since February?

Read more comments on GitHub >

github_iconTop Results From Across the Web

vue.js - Failed to download Chromium r579032
My current work-around is to manually download Chromium with the specific version above. Then I add its install path to my environment path ......
Read more >
ERROR: Failed to download Chromium r686378!
When utilizing Puppeteer you may intermittently encounter a build failure with the following error message: ERROR: Failed to download ...
Read more >
Error: connect ETIMEDOUT 13.107.42.20:443
This problem was caused by us being switched to the new https://dev.azure.com url. Once we switched back to the old url everything worked...
Read more >
Investigate why CI appears to be downloading Chromium on ...
Command: node install.js Arguments: Directory: /builds/gitlab-org/gitlab-ui/node_modules/puppeteer Output: ERROR: Failed to download ...
Read more >
windows node_tls_reject_unauthorized
npm install error - unable to get local issuer certificate ... install browsers Error: Failed to download chromium v1000, caused by Error: connect...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found