-
-
Notifications
You must be signed in to change notification settings - Fork 280
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
Verifying Deployment: FAILED #280
Comments
I now have a new error:
|
This is most often because the verification is not waiting long enough for the app to finish starting up. See my issue #265 |
@mroftalp Are you trying to deploy your app and run it behind a reverse proxy (like Nginx)? |
@kyle-rader Is it because there's a comment in the mup.js? I haven't tried removing the comments, I'll try again later. No, I'm not running it behind a reverse proxy |
@mroftalp If the comment is proper JS then I wouldn't think that would cause an issue. |
Have the same/similar issue - see #267 (comment) I think it's due to 1.4.1 adding the warning message for bcrypt? Mup verifies it fine if i have the wait time set longer. Even with a short wait time, the app deploys without problems even with failed verification |
Fixed by removing comments in mup.js |
I have solved most error in deploy process, and write a file about the deploy.You can see at meteor-deploy Hope this helps |
@wwlweihai your link is not active |
I'm having this same problem (I've documented it here on this SO post), and removing the comments didn't make any difference. |
@blainehansen, can you post your entire log? |
I discovered my verification error was because my deploy account was using
425.241.7977 |
Check out my answer to the SO post it turned out to be the |
All the npm output about packages and versions and everything is a red herring and is throwing you off I think. Get more of the log ( |
@blainehansen definitely, for me it was trying to run make and didn't have build-essentials. That's why you really have to look at the entire logs @kyle-rader that seems odd, I thought most bash stuff was still compatible with zsh (i'm using zsh here) |
Previous instance I don't have a problem redeploying. I created a new instance in EC2 and I'm getting this error.
The text was updated successfully, but these errors were encountered: