无法在Firebase Hosting后面调用Google Cloud Function-状态503，但状态页面上没有指示 [英] Cannot call Google Cloud Function behind Firebase Hosting - Status 503 but no indication on status pages
问题描述
我在访问暴露的Google Cloud HTTP函数时遇到问题通过Firebase托管.我认为CDN存在问题，因为该功能没有更改，但是我在状态页上看不到任何内容:
I have a problem accessing a Google Cloud HTTP Function that is exposed through Firebase Hosting. I assume there is an issue with the CDN, because the function has not changed, but I do not see anything on the status pages:
- https://status.firebase.google.com/-托管为绿色
- https://status.cloud.google.com/- Google Cloud功能是绿色的
- https://status.firebase.google.com/ - Hosting is green
- https://status.cloud.google.com/ - Google Cloud Fuctions is green
直接访问该功能，即不是通过Firebase托管而是使用https://{region}{app}.cloudfunctions.net/{name} URL似乎遇到了同样的问题.
Accessing the function directly, i.e. not through Firebase Hosting but using the https://{region}{app}.cloudfunctions.net/{name} URL seems to be running into the same issues.
最初，我在近两分钟后收到了此回复
Initially, I received this response after close to two minutes
content-type: text/plain;charset=US-ASCII
date: Tue, 06 Oct 2020 14:10:01 GMT
fastly-host: cache-hhn4049-HHN
server: Varnish
status: 503
Timed out while waiting on cache-hhn4049-HHN
这似乎表明Fastly存在问题(列为 Firebase的子处理器)，但其状态页面显示一切正常.
This seems to indicate a problem with Fastly (listed as a subprocessor for Firebase), but their status page shows everything as operational.
一段时间后，我似乎在15到30秒的超时后得到了另一方的答复:
After some time, I seem to be getting responses from a different party after a timeout of 15-30s:
(为了便于阅读，剥离了HTML)
(stripped HTML for readability)
accept-ranges: bytes
content-length: 323
content-type: text/html; charset=UTF-8
date: Tue, 06 Oct 2020 14:17:22 GMT
fastly-restarts: 1
server: Google Frontend
status: 500
vary: x-fh-requested-host, accept-encoding
x-cache: MISS
x-cache-hits: 0
x-cloud-trace-context: 234db5d36bf48ff0a385ed838e14676c
x-served-by: cache-hhn4049-HHN
x-timer: S1601993817.546227,VS0,VE25795
Error: Server Error
The server encountered an error and could not complete your request.
Please try again in 30 seconds.
当然，等待30秒无济于事.
Of course, waiting for 30 seconds does not help.
在云功能日志中，我确实看到一些请求正在进行，并且花费了400-500ms的时间才能正常执行.我可以看到一次崩溃"在54毫秒内完成，两次更长的执行时间在20秒左右，一次超时(60秒).该功能用作自定义身份验证过程的一部分，因此通常会有很多请求.
In the cloud functions log I do see some requests going through and taking between 400-500ms for normal execution. I can see one 'crash' finishing in 54ms, two longer executions at around 20s, and one timeout (60s). The function is used as a part of a custom authentication process, so there are usually a lot of requests.
关于我该怎么做才能理解问题的任何建议?或状态页面实际上可以告诉我在哪里可以找到问题?
Any advice on what I can do to understand what is the issue? Or a status page that can actually tell me where I can look for a problem?
推荐答案
firebaser此处
在过去大约一个小时内部署Cloud Functions确实存在问题.我们正在努力将问题添加到Firebase状态页面.
There were indeed issues with deploying Cloud Functions in the past hour or so. We're working on adding the issue to the Firebase status page.
现在它应该大致恢复正常了.有关当前状态，请参见 Google Cloud信息中心顶部的黄色横幅.如果没有黄色横幅，则问题可能已完全解决.
It should now mostly be back to normal. For the current status, see the yellow banner at the top of the Google Cloud dashboard. If there is no yellow banner, the problem is likely completely fixed.
这篇关于无法在Firebase Hosting后面调用Google Cloud Function-状态503，但状态页面上没有指示的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
