Firebase Serve命令失败,错误为404
每当我在mac上运行firebase Service时,我都会收到一个404错误…这以前从未发生过,我只是在开始发生之前5分钟使用本地开发服务器。我已经删除了firebase.json文件并重新初始化它,重新安装了firebase工具,但每次都失败。以下是在调试模式下运行命令的结果Firebase Serve命令失败,错误为404,firebase,firebase-hosting,firebase-cli,Firebase,Firebase Hosting,Firebase Cli,每当我在mac上运行firebase Service时,我都会收到一个404错误…这以前从未发生过,我只是在开始发生之前5分钟使用本地开发服务器。我已经删除了firebase.json文件并重新初始化它,重新安装了firebase工具,但每次都失败。以下是在调试模式下运行命令的结果 firebase serve --debug [2018-09-11T16:12:25.873Z] ------------------------------------------------------
firebase serve --debug
[2018-09-11T16:12:25.873Z] ----------------------------------------------------------------------
[2018-09-11T16:12:25.876Z] Command: /usr/local/bin/node /usr/local/bin/firebase serve --debug
[2018-09-11T16:12:25.877Z] CLI Version: 4.2.1
[2018-09-11T16:12:25.877Z] Platform: darwin
[2018-09-11T16:12:25.877Z] Node Version: v6.11.3
[2018-09-11T16:12:25.878Z] Time: Tue Sep 11 2018 11:12:25 GMT-0500 (CDT)
[2018-09-11T16:12:25.878Z] ----------------------------------------------------------------------
[2018-09-11T16:12:25.890Z] > 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"]
[2018-09-11T16:12:25.890Z] > authorizing via signed-in user
[2018-09-11T16:12:25.893Z] >>> HTTP REQUEST GET https://admin.firebase.com/v1/projects/skadaddle-10f24
[2018-09-11T16:12:26.210Z] <<< HTTP RESPONSE 200 server=nginx, date=Tue, 11 Sep 2018 16:12:26 GMT, content-type=application/json; charset=utf-8, content-length=114, connection=close, x-content-type-options=nosniff, strict-transport-security=max-age=31536000; includeSubdomains, cache-control=no-cache, no-store
[2018-09-11T16:12:26.212Z] >>> HTTP REQUEST GET https://cloudresourcemanager.googleapis.com/v1/projects/skadaddle-10f24
[2018-09-11T16:12:26.385Z] <<< HTTP RESPONSE 200 content-type=application/json; charset=UTF-8, vary=X-Origin, Referer, Origin,Accept-Encoding, date=Tue, 11 Sep 2018 16:12:26 GMT, server=ESF, cache-control=private, x-xss-protection=1; mode=block, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, alt-svc=quic=":443"; ma=2592000; v="44,43,39,35", accept-ranges=none, connection=close
=== Serving from '/Users/Kevin/Desktop/Source/Skadaddle'...
[2018-09-11T16:12:26.388Z] >>> HTTP REQUEST GET https://mobilesdk-pa.googleapis.com/v1/projects/255074367563/clients/_:getWebAppConfig
[2018-09-11T16:12:26.514Z] <<< HTTP RESPONSE 404 vary=X-Origin, Referer, Origin,Accept-Encoding, content-type=application/json; charset=UTF-8, date=Tue, 11 Sep 2018 16:12:26 GMT, server=ESF, cache-control=private, x-xss-protection=1; mode=block, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, alt-svc=quic=":443"; ma=2592000; v="44,43,39,35", accept-ranges=none, connection=close
[2018-09-11T16:12:26.514Z] <<< HTTP RESPONSE BODY code=404, message=Requested entity was not found., status=NOT_FOUND
Error: HTTP Error: 404, Requested entity was not found.
[2018-09-11T16:12:26.519Z] Error Context: {
"body": {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
},
"response": {
"statusCode": 404,
"body": {
"error": {
"code": 404,
"message": "Requested entity was not found.",
"status": "NOT_FOUND"
}
},
"headers": {
"vary": "X-Origin, Referer, Origin,Accept-Encoding",
"content-type": "application/json; charset=UTF-8",
"date": "Tue, 11 Sep 2018 16:12:26 GMT",
"server": "ESF",
"cache-control": "private",
"x-xss-protection": "1; mode=block",
"x-frame-options": "SAMEORIGIN",
"x-content-type-options": "nosniff",
"alt-svc": "quic=\":443\"; ma=2592000; v=\"44,43,39,35\"",
"accept-ranges": "none",
"connection": "close"
},
"request": {
"uri": {
"protocol": "https:",
"slashes": true,
"auth": null,
"host": "mobilesdk-pa.googleapis.com",
"port": 443,
"hostname": "mobilesdk-pa.googleapis.com",
"hash": null,
"search": null,
"query": null,
"pathname": "/v1/projects/255074367563/clients/_:getWebAppConfig",
"path": "/v1/projects/255074367563/clients/_:getWebAppConfig",
"href": "https://mobilesdk-pa.googleapis.com/v1/projects/255074367563/clients/_:getWebAppConfig"
},
"method": "GET"
}
}
}
firebase服务--调试
[2018-09-11T16:12:25.873Z]----------------------------------------------------------------------
[2018-09-11T16:12:25.876Z]命令:/usr/local/bin/node/usr/local/bin/firebase-service——调试
[2018-09-11T16:12:25.877Z]CLI版本:4.2.1
[2018-09-11T16:12:25.877Z]平台:达尔文
[2018-09-11T16:12:25.877Z]节点版本:v6.11.3
[2018-09-11T16:12:25.878Z]时间:2018年9月11日星期二11:12:25 GMT-0500(CDT)
[2018-09-11T16:12:25.878Z]----------------------------------------------------------------------
[2018-09-11T16:12:25.890Z]>命令需要作用域:[“电子邮件”、“openid”和https://www.googleapis.com/auth/cloudplatformprojects.readonly","https://www.googleapis.com/auth/firebase","https://www.googleapis.com/auth/cloud-platform"]
[2018-09-11T16:12:25.890Z]>通过登录用户进行授权
[2018-09-11T16:12:25.893Z]>>>HTTP请求获取https://admin.firebase.com/v1/projects/skadaddle-10f24
[2018-09-11T16:12:26.210Z]>HTTP请求获取https://cloudresourcemanager.googleapis.com/v1/projects/skadaddle-10f24
[2018-09-11T16:12:26.385Z]>HTTP请求获取https://mobilesdk-pa.googleapis.com/v1/projects/255074367563/clients/_:getWebAppConfig
[2018-09-11T16:12:26.514Z]Firebase员工在这里
CLI部署存在已知问题。正在调查中。您可以在此处跟踪停机情况:
每当遇到类似这样的CLI故障时,请直接与Firebase支持部门联系,并提供所有相关详细信息:
问题在于谷歌。当您运行firebase Service
时,它发出一个请求,该请求当前抛出404错误
通过在node\u modules/firebase tools/lib
中编辑3个文件,我得以绕过这个(临时修复)
在api.js
的第99行是调用错误URL的地方。只需将其更改为任何有效的非404 url
然后,在fetchWebSetup.js
中,将“GET”
之后第9行的参数更改为空字符串(例如返回api.request(“GET”,”,{
对第51行的functionsConfig.js
执行与上面相同的操作
这应该可以让你现在就开始运行,但是当Google修复这个URL时,这应该可以解决问题。我只能通过删除.firebaserc
然后再次运行firebaseinit
来解决这个问题。只需确保你不会错误地覆盖现有的配置。同样的问题。对我来说,函数可以工作,但是sting没有。编辑:函数开始,我实际上没有尝试使用它们。感谢更新。它是否必须在我们firebase每次提供服务时获取这些URL?是的,它每次都做相同的事情。我从今天开始收到此错误,这是否作为问题再次出现?