firebase-tools: Firebase hosting: HTTP Error: 404, Requested entity was not found

Update: We think there is a server-side error. We are investigating and addressing this. This is an error that affects users using the pinTags feature, which includes all web frameworks users while the feature is available.

Fortunately, pintags is still an experiment and can be disabled without downgrading your CLI. If you turn off this experiment, you’ll lose atomic rollbacks and preview channels with server-side content, but you’ll be able to deploy to production again while we figure this out. To disable the experiment, run:

firebase experiments:disable pintags

You will permanently lose the feature until we either remove the experiment guard or until you reenable the feature with

firebase experiments:enable pintags

It was an unrelated update. There was a bad server-side update in Cloud Run that affected tagged URLs. The change has been rolled back and you should be able to reenable pintags. Note that you will need to push to production with pintags enabled before you can create a new preview with pintags (otherwise the preview would modify prod).

I am facing the same problem with deploying the NextJS project. It seems it is not related to firebase-tools library directly and instead, there was some Google Cloud + Firebase Hosting integration change on their side. The error started happening without any local config changes. Tried multiple firebase-tools versions, no luck. Tried creating a new hosting profile/app, and it’s not able to even deploy the first deployment. The thing is, the deployment succeeds, it created a Cloud Run instance, but it creates an incorrect URL (not Firebase Hosting URL). Started happening a couple of days ago or so.

At this point, this is a critical outage from our side as we’re not able to deploy any new updates via the current flow.

It seems that the behavior of the updateVersion API has changed. It started returning 404 responses today.

A quick hack for people with PRD impact while waiting for the proper fix:

1. Go to your Cloud Run service YAML section
2. Under traffic copy the tag value of the entry that’s one before the last one. (For me it’s the one above - percent: 100
3. Edit your api.js file of firebase-tools (node_modules\firebase-tools\lib\hosting\api.js)

Find updateVersion method and hardcode the tag to one that you copied

Like that:

async function updateVersion(site, versionId, version) {
    version["config"]["rewrites"][0]["run"]["tag"] = "fh-bd0d4fbb2xxxxxxxxx";
    const res = await apiClient.patch(`projects/-/sites/${site}/versions/${versionId}`, version, {
        queryParams: {
            updateMask: proto.fieldMasks(version, "labels", "config").join(","),
        },
    });
    return res.body;
}

It will deploy the previously failed deployment.

I have also been encountering this bug. I’m not aware of any fix, but right now I can reproduce it using the simplest possible SvelteKit demo app. Specifically:

yarn create vite

(Follow instructions to create a SvelteKit project.)

cd vite-project
npm install
firebase init

(Follow instructions to create a project with only hosting enabled, and connect it to a Firebase app on the Blaze plan.)

firebase deploy

I then encounter the exact same error:

i  functions: updating Node.js 18 (2nd Gen) function firebase-frameworks-*****:ssr*****(asia-east1)...
+  functions[firebase-frameworks-*****:ssr*****(asia-east1)] Successful update operation.
Function URL (firebase-frameworks-*****:ssr*****(asia-east1)): https://ssr*****-***-de.a.run.app
i  functions: cleaning up build files...
i  hosting[*****]: finalizing version...

Error: HTTP Error: 404, Requested entity was not found.

This error seems especially inconsistent to me. For instance, a couple of weeks ago I had the error on my main firebase project, but when I tried to reproduce with a sample project (as above), the sample project actually worked.

Same here. Thank you!

Hopefully they’ll communicate on it at some point. It was a pain just to find this issue. https://status.firebase.google.com/ doesn’t show anything yet.

Agreed. This issue should be in the status page, otherwise that page can’t be trusted.

Edit: they added a message there.

I also shared mine: case 10238751

Hey, thanks @aalej! Just in case no one has done it yet, I have shared my firebase-debug.log and project ID to firebase support.

Case 10239154

Hi everyone, sorry for the extra hoop here, but we would like to ask if anyone can share their firebase-debug.log and project ID to Firebase Support. Our team has an idea of what might be causing this issue, but we would need to take a look into the project to verify.

Also, please mention this GitHub issue in the support ticket.

Same problem for me (on a sveltekit project) I have provided support with debug output from my deploy. firebase deploy --debug

Just be carful sharing that file however, it contains your private key. I redacted mine before sharing with support.

Also happening here… Incredibly frustrating having things just break…

@aalej
It fails on finalizing version for hosting.

[2023-07-11T14:57:07.277Z] <<< [apiv2][status] PATCH https://firebasehosting.googleapis.com/v1beta1/projects/-/sites/rotmg-trade/versions/80b63ff8d33b7de1 404
[2023-07-11T14:57:07.277Z] <<< [apiv2][body] PATCH https://firebasehosting.googleapis.com/v1beta1/projects/-/sites/rotmg-trade/versions/80b63ff8d33b7de1 {"error":{"code":404,"message":"Requested entity was not found.","status":"NOT_FOUND"}}

Error: HTTP Error: 404, Requested entity was not found.
[2023-07-11T14:57:07.336Z] Error Context: {
  "body": {
    "error": {
      "code": 404,
      "message": "Requested entity was not found.",
      "status": "NOT_FOUND"
    }
  },
  "response": {
    "statusCode": 404
  }
}