Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Firebase deploy fails with "Error: HTTP Error: 500, Internal error encountered."
See original GitHub issue[REQUIRED] Environment info
firebase-tools: 7.0.0
Platform: macOS
[REQUIRED] Test case
Deploying using firebase deploy produces the following error.
Error: HTTP Error: 500, Internal error encountered.
[REQUIRED] Steps to reproduce
Run firebase deploy
[REQUIRED] Expected behavior
To deploy successfully
[REQUIRED] Actual behavior
[2019-08-21T15:26:37.637Z] ---------------------------------------------------------------------- [2019-08-21T15:26:37.640Z] Command: /usr/local/bin/node /usr/local/bin/firebase deploy --debug [2019-08-21T15:26:37.640Z] CLI Version: 7.0.0 [2019-08-21T15:26:37.641Z] Platform: darwin [2019-08-21T15:26:37.641Z] Node Version: v10.16.0 [2019-08-21T15:26:37.642Z] Time: Wed Aug 21 2019 18:26:37 GMT+0300 (GMT+03:00) [2019-08-21T15:26:37.642Z] ----------------------------------------------------------------------
[2019-08-21T15:26:37.651Z] > 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”] [2019-08-21T15:26:37.652Z] > authorizing via signed-in user [2019-08-21T15:26:37.652Z] [iam] checking project PROJECT_NAME for permissions [“firebase.projects.get”,“firebasehosting.sites.update”] [2019-08-21T15:26:37.654Z] >>> HTTP REQUEST POST https://cloudresourcemanager.googleapis.com/v1/projects/PROJECT_NAME:testIamPermissions permissions=[firebase.projects.get, firebasehosting.sites.update] [2019-08-21T15:26:38.918Z] <<< HTTP RESPONSE 200 content-type=application/json; charset=UTF-8, vary=X-Origin, Referer, Origin,Accept-Encoding, date=Wed, 21 Aug 2019 15:26:38 GMT, server=ESF, cache-control=private, x-xss-protection=0, x-frame-options=SAMEORIGIN, x-content-type-options=nosniff, server-timing=gfet4t7; dur=772, alt-svc=quic=“:443”; ma=2592000; v=“46,43,39”, accept-ranges=none, transfer-encoding=chunked [2019-08-21T15:26:38.921Z] >>> HTTP REQUEST GET https://firebase.googleapis.com/v1beta1/projects/PROJECT_NAME
[2019-08-21T15:26:39.376Z] <<< HTTP RESPONSE 200 content-type=application/json; charset=UTF-8, vary=X-Origin, Referer, Origin,Accept-Encoding, date=Wed, 21 Aug 2019 15:26:39 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,39”, accept-ranges=none, transfer-encoding=chunked
=== Deploying to ‘PROJECT_NAME’…
i deploying hosting [2019-08-21T15:26:39.380Z] >>> HTTP REQUEST POST https://firebasehosting.googleapis.com/v1beta1/sites/PROJECT_NAME/versions , deployment-tool=cli-firebase [2019-08-21T15:26:40.654Z] <<< HTTP RESPONSE 500 vary=X-Origin, Referer, Origin,Accept-Encoding, content-type=application/json; charset=UTF-8, date=Wed, 21 Aug 2019 15:26:40 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,39”, accept-ranges=none, transfer-encoding=chunked [2019-08-21T15:26:40.654Z] <<< HTTP RESPONSE BODY code=500, message=Internal error encountered., status=INTERNAL
Error: HTTP Error: 500, Internal error encountered. [2019-08-21T15:26:40.658Z] Error Context: { “body”: { “error”: { “code”: 500, “message”: “Internal error encountered.”, “status”: “INTERNAL” } }, “response”: { “statusCode”: 500, “body”: { “error”: { “code”: 500, “message”: “Internal error encountered.”, “status”: “INTERNAL” } }, “headers”: { “vary”: “X-Origin, Referer, Origin,Accept-Encoding”, “content-type”: “application/json; charset=UTF-8”, “date”: “Wed, 21 Aug 2019 15:26:40 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,39"”, “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/PROJECT_NAME/versions”, “path”: “/v1beta1/sites/PROJECT_NAME/versions”, “href”: “https://firebasehosting.googleapis.com/v1beta1/sites/PROJECT_NAME/versions” }, “method”: “POST” } } }
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yes, it was just that there was a problem on the server side that was causing the internal errors and that got resolved. There are some details on the incident, but basically depending on where you were trying to deploy from you had a greater chance of it failing (but there was still a chance of failing worldwide).
That particular issue should be fixed now.
it’s still there…