firebase-tools: 7.15.1
Platform: macOS
"hosting": {
"public": "dist/browser",
"ignore": [
"firebase.json",
"**/.*",
"**/node_modules/**"
],
"rewrites": [
{
"source": "**",
"run": {
"serviceId": "vision",
"region": "europe-west4"
}
}
]
}

$ firebase deploy --only hosting --debug
[2020-03-22T20:56:03.997Z] ----------------------------------------------------------------------
[2020-03-22T20:56:03.999Z] Command: /Users/michael/.nvm/versions/node/v10.15.1/bin/node /Users/michael/.nvm/versions/node/v10.15.1/bin/firebase deploy --only hosting --debug
[2020-03-22T20:56:04.000Z] CLI Version: 7.15.1
[2020-03-22T20:56:04.000Z] Platform: darwin
[2020-03-22T20:56:04.000Z] Node Version: v10.15.1
[2020-03-22T20:56:04.003Z] Time: Sun Mar 22 2020 21:56:04 GMT+0100 (Central European Standard Time)
[2020-03-22T20:56:04.003Z] ----------------------------------------------------------------------
[2020-03-22T20:56:04.003Z]
[2020-03-22T20:56:04.042Z] > command requires scopes: ["email","openid","https://www.googleapis.com/auth/cloudplatformprojects.readonly","https://www.googleapis.com/auth/firebase","https://www.googleapis.com/auth/cloud-platform"]
[2020-03-22T20:56:04.042Z] > authorizing via signed-in user
[2020-03-22T20:56:04.042Z] [iam] checking project vision-88888 for permissions ["firebase.projects.get","firebasehosting.sites.update"]
[2020-03-22T20:56:04.044Z] >>> HTTP REQUEST POST https://cloudresourcemanager.googleapis.com/v1/projects/vision-88888:testIamPermissions
permissions=[firebase.projects.get, firebasehosting.sites.update]
[2020-03-22T20:56:04.965Z] <<< HTTP RESPONSE 200 content-type=application/json; charset=UTF-8, vary=X-Origin, Referer, Origin,Accept-Encoding, date=Sun, 22 Mar 2020 20:56:04 GMT, server=ESF, cache-control=private, x-xss-protection=0, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, server-timing=gfet4t7; dur=668, alt-svc=quic=":443"; ma=2592000; v="46,43",h3-Q050=":443"; ma=2592000,h3-Q049=":443"; ma=2592000,h3-Q048=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,h3-T050=":443"; ma=2592000, accept-ranges=none, transfer-encoding=chunked
[2020-03-22T20:56:04.967Z] >>> HTTP REQUEST GET https://firebase.googleapis.com/v1beta1/projects/vision-88888
[2020-03-22T20:56:05.231Z] <<< HTTP RESPONSE 200 content-type=application/json; charset=UTF-8, vary=X-Origin, Referer, Origin,Accept-Encoding, date=Sun, 22 Mar 2020 20:56:05 GMT, server=ESF, cache-control=private, x-xss-protection=0, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, alt-svc=quic=":443"; ma=2592000; v="46,43",h3-Q050=":443"; ma=2592000,h3-Q049=":443"; ma=2592000,h3-Q048=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,h3-T050=":443"; ma=2592000, accept-ranges=none, transfer-encoding=chunked
=== Deploying to 'vision-88888'...
i deploying hosting
[2020-03-22T20:56:09.529Z] >>> HTTP REQUEST POST https://firebasehosting.googleapis.com/v1beta1/sites/vision-88888/versions
rewrites=[glob=**, region=europe-west4, serviceId=vision], deployment-tool=cli-firebase
[2020-03-22T20:56:10.509Z] <<< HTTP RESPONSE 400 vary=X-Origin, Referer, Origin,Accept-Encoding, content-type=application/json; charset=UTF-8, date=Sun, 22 Mar 2020 20:56:10 GMT, server=ESF, cache-control=private, x-xss-protection=0, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, alt-svc=quic=":443"; ma=2592000; v="46,43",h3-Q050=":443"; ma=2592000,h3-Q049=":443"; ma=2592000,h3-Q048=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,h3-T050=":443"; ma=2592000, accept-ranges=none, transfer-encoding=chunked
[2020-03-22T20:56:10.510Z] <<< HTTP RESPONSE BODY code=400, message=Cloud Run region europe-west4 is not supported., status=INVALID_ARGUMENT
Error: HTTP Error: 400, Cloud Run region europe-west4 is not supported.
[2020-03-22T20:56:10.515Z] Error Context: {
"body": {
"error": {
"code": 400,
"message": "Cloud Run region europe-west4 is not supported.",
"status": "INVALID_ARGUMENT"
}
},
"response": {
"statusCode": 400,
"body": {
"error": {
"code": 400,
"message": "Cloud Run region europe-west4 is not supported.",
"status": "INVALID_ARGUMENT"
}
},
"headers": {
"vary": "X-Origin, Referer, Origin,Accept-Encoding",
"content-type": "application/json; charset=UTF-8",
"date": "Sun, 22 Mar 2020 20:56:10 GMT",
"server": "ESF",
"cache-control": "private",
"x-xss-protection": "0",
"x-frame-options": "SAMEORIGIN",
"x-content-type-options": "nosniff",
"alt-svc": "quic=":443"; ma=2592000; v="46,43",h3-Q050=":443"; ma=2592000,h3-Q049=":443"; ma=2592000,h3-Q048=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,h3-T050=":443"; ma=2592000",
"accept-ranges": "none",
"transfer-encoding": "chunked"
},
"request": {
"uri": {
"protocol": "https:",
"slashes": true,
"auth": null,
"host": "firebasehosting.googleapis.com",
"port": 443,
"hostname": "firebasehosting.googleapis.com",
"hash": null,
"search": null,
"query": null,
"pathname": "/v1beta1/sites/vision-88888/versions",
"path": "/v1beta1/sites/vision-88888/versions",
"href": "https://firebasehosting.googleapis.com/v1beta1/sites/vision-88888/versions"
},
"method": "POST"
}
}
}
Deploy and redirect to europe-west4
See error.
We may not have support for Hosting to connect to europe-west4 yet. Please file a feature request for Hosting so we can better track this request and get working on it.
Since this isn't something that can be fixed by the CLI, I'm closing this issue. Thanks for bringing this to our attention!
Is there a list that shows what Firebase Hosting supports? It's confusing because it is inconsistent with the official Google Cloud Run location list: https://cloud.google.com/run/docs/locations
Error: HTTP Error: 400, Cloud Run region
asia-east1is not supported.
From https://firebase.google.com/docs/hosting/full-config#direct_requests_to_a_function:
Important: Firebase Hosting supports Cloud Functions in us-central1 only.
So the Functions restrictions also apply to _Cloud Run_? I don't see documentation for that.
To the best of my knowledge - yes. Firebase Hosting originates in us-central1, that's why back end services must be deployed there too.
@merlinnot I don't think that's correct. Firebase Hosting hosts static files using a global CDN, although how it does routing to Cloud Run is not completely clear to me.
So to answer my own question, I literally just changed my firebase.json file to see what regions are available based on the error messages. Hopefully someone finds this useful.
Google/Firebase is constantly updating their infrastructure, so this is only accurate as of May 8th, 2020.
Hm, that's right. You can actually specify a region in Firebase Hosting for Cloud Run, didn't know that.
@aaron-ikb add new regions like asia-southeast1 for Not available list ! thanks
I agree that having a clear list somewhere would be very helpful, so I don't spend time looking for errors in my own code! On another note, has asia-northeast1 been removed from this imaginary "list"? Myself and a few others have found that it's suddenly no longer working.
Unfortunately, I don't plan on keeping that list up-to-date. I hope Firebase/Google would make an official, up-to-date one.
As for asia-northeast1, I know it used to work because I've deployed there before. @meguna what error message do you get?
@aaron-ikb Error: HTTP Error: 400, Cloud Run regionasia-southeast1is not supported.
Most helpful comment
@merlinnot I don't think that's correct. Firebase Hosting hosts static files using a global CDN, although how it does routing to Cloud Run is not completely clear to me.
So to answer my own question, I literally just changed my
firebase.jsonfile to see what regions are available based on the error messages. Hopefully someone finds this useful.Firebase Hosting to Cloud Run rewrite availability
Google/Firebase is constantly updating their infrastructure, so this is only accurate as of May 8th, 2020.
Available
Not available