Downloading chrome fails with 404

[shouichi]

Orb version

1.2.1

What happened

Downloading chrome fails with 404.

Google Chrome is not currently installed; installing it
curl: (22) The requested URL returned error: 404

Downloading chrome fails only in CI. In other words, curl -I https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb works locally but not in CI. Maybe google restricted a certain range of IPs?

Expected behavior

Chrome is successfully installed.

[jacobgavin]

Same behavior on Orb Version 1.1.3

[mattops]

Doesn't work locally for me.

Perhaps google are having an issue or changed something on their download site, or CDN issue perhaps.

[benoittgt]

I tried to specify the version like:

    steps:
      - browser-tools/install-browser-tools:
          chrome-version: "92.0.4515.159"

But I have the same error in Circle CI.

[Prounckk]

Same issue with
Orb version
1.1.0

Google Chrome is not currently installed; installing it
curl: (22) The requested URL returned error: 404 

Exited with code exit status 22
CircleCI received exit code 22

[mzgajner]

Can confirm issue on orb versions 1.1.1 and 1.2.1, both when specifying version manually and letting it use latest/default.

Could definitely be Google blocking a range, as issue author is assuming.

[coding-bunny]

Just adding that I'm seeing the same behavior.
Commands all work fine locally on a Linux system, so either CircleCI has been blocked by Google, or something funky is going on with a CDN for their machines.

[chris-john-hopkins]

Does not work locally for me

[gmemstr]

Hey all, we're tracking this issue. From what we can tell it's an issue on Google's end. Failure/404 appears to be intermittent, both within our cloud pipelines and our local machines. We'll keep monitoring this issue and update when something changes.

[gmemstr]

Can't confirm anything concrete yet but this seems to be clearing up. Running ~20 requests in batches from time to time indicates fewer 404 errors but still monitoring.

[gmemstr]

As far as I can tell, this is resolved. If not, let me know -- keeping this issue open for a little longer.

[tagCincy]

Still experiencing this issue

[sourabhkt]

@gmemstr It doesn't seem to be working for us. could that be because it's cached at CircleCI end?

[gmemstr]

I hear you :) - digging in.

[mzgajner]

Not working for us either - tried rerunning after your initial post about things maybe clearing up and again after you reported it resolved, both failed.

[danielrozenberg]

This seems related to https://bugs.chromium.org/p/chromium/issues/detail?id=1245597, fix is already rolled out and should be deployed everywhere soon

[gmemstr]

@danielrozenberg Cheers! I failed to bring this up when trying to look for an official report of this issue.

As a sidenote, others have mentioned pinning the version is a workaround for this, and I recommend doing this by default where possible.

[lzilioli-prism]

Works for us now!

[gmemstr]

According to the aforementioned bug report, this should be fixed globally. Closing :)