Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firebase-cli commands returning error #387

Closed
kr05 opened this issue Jul 6, 2017 · 9 comments
Closed

Firebase-cli commands returning error #387

kr05 opened this issue Jul 6, 2017 · 9 comments

Comments

@kr05
Copy link

kr05 commented Jul 6, 2017

I am trying to use the "firebase deploy" but it's returning the following error:

Error: An unexpected error has occurred.
It was working fine this morning and it suddenly stopped, and I haven't made any changes. I tried updating firebase-cli, firebase init, and firebase login, but none of these fixed the problem.

Here's the firebase-debug.txt file:

firebase-debug.zip

@laurenzlong
Copy link
Contributor

Thanks for reporting, we have an outage due to a dependency (Google's Oauth2 service). The relevant teams have been paged, and are working actively to fix it.

@laurenzlong
Copy link
Contributor

@kr05 Can you try again now?

@kr05
Copy link
Author

kr05 commented Jul 6, 2017

Yes, it works perfect now. Deployment got stuck at 98% for a bit longer than usual, but aside from that no issues. Thanks!

@mding5692
Copy link

mding5692 commented Jul 7, 2017

Hi @laurenzlong I actually have the same issue and its been going on for a while, just tried now and accidentally even updated to node 8.1.0 from issue #356 , it says 503 Error which i presume is the outage?

Heres the error in the debug.log:

[debug] [2017-07-07T00:22:59.604Z] <<< HTTP RESPONSE 200

[info] i  functions: packaged functions (6.47 KB) for uploading

[debug] [2017-07-07T00:23:02.238Z] >>> HTTP REQUEST GET https//hidden-as-personal-material.com  
 Thu Jul 06 2017 20:23:02 GMT-0400 (EDT)

[debug] [2017-07-07T00:23:02.352Z] <<< HTTP RESPONSE 503

[debug] [2017-07-07T00:23:02.353Z] <<< HTTP RESPONSE BODY undefined

[debug] [2017-07-07T00:23:02.355Z] TypeError: Cannot read property 'error' of undefined
[error] 

[error] Error: An unexpected error has occurred.

Much thanks.

@laurenzlong
Copy link
Contributor

Hi @mding5692 , you're right, the outage is back. Sorry for the inconvenience. You can follow along in https://status.firebase.google.com/ for the latest status.

@mding5692
Copy link

Also just a note to others who might have an issue from the outage and get an error like this after the outage is reported to be fixed:

Server Error. connect EHOSTUNREACH

Try reinstalling firebase-tools again via:

npm install -g firebase-tools

because it might help and yep after fixing that one, I've been able to upload my cloud functions

@reyou
Copy link

reyou commented Sep 24, 2017

@mding5692

npm install -g firebase-tools

worked like a charm. Thanks!

@imMarkdeVries
Copy link

I'm having a problem with uploading functions due to a
self signed certificate in certificate chain

Does anybody know what to do. I tried the reinstall. Also stopped the virus protection.

Here is what happens

firebase deploy --only functions

=== Deploying to 'firestore-d1320'...

i  deploying functions
Running command: npm --prefix $RESOURCE_DIR run lint

> functions@ lint D:\projecten\InputGenerator\functions
> eslint .

+  functions: Finished running predeploy script.
i  functions: ensuring necessary APIs are enabled...
+  functions: all necessary APIs are enabled
i  functions: preparing functions directory for uploading...
i  functions: packaged functions (52.62 KB) for uploading
!  functions: Upload Error: Server Error. self signed certificate in certificate chain
i  functions: updating function firestoreEmail...
!  functions[firestoreEmail]: Deployment error.
Failed to retrieve function source code


Functions deploy had errors. To continue deploying other features (such as database), run:
    firebase deploy --except functions

Error: Functions did not deploy properly.

@cvharris
Copy link

@imMarkdeVries I believe it's due to gRPC not handling Mac self-signed certs well. This is especially a problem with companies that require all employee devices to have their own security certs for decrypting traffic. It's not clear how to have gRPC trust certs on a per-device basis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants