Verifying Deployment: FAILED
See original GitHub issuePrevious instance I don’t have a problem redeploying. I created a new instance in EC2 and I’m getting this error.
Verifying Deployment: FAILED
-----------------------------------STDERR-----------------------------------
e/lib/connection/connection.js:170:10)
at Socket.g (events.js:260:16)
at emitNone (events.js:67:13)
> meteor-dev-bundle@0.0.0 install /bundle/bundle/programs/server
> node npm-rebuild.js
{
"meteor-dev-bundle": "0.0.0",
"npm": "3.10.5",
"ares": "1.10.1-DEV",
"http_parser": "2.5.2",
"icu": "56.1",
"modules": "46",
"node": "4.4.7",
"openssl": "1.0.2h",
"uv": "1.8.0",
"v8": "4.5.103.36",
"zlib": "1.2.8"
}
npm WARN meteor-dev-bundle@0.0.0 No description
npm WARN meteor-dev-bundle@0.0.0 No repository field.
npm WARN meteor-dev-bundle@0.0.0 No license field.
=> Starting meteor app on port:80
Note: you are using a pure-JavaScript implementation of bcrypt.
While this implementation will work correctly, it is known to be
approximately three times slower than the native implementation.
In order to use the native implementation instead, run
meteor npm install --save bcrypt
in the root directory of your application.
=> Redeploying previous version of the app
-----------------------------------STDOUT-----------------------------------
To see more logs type 'mup logs --tail=50'
----------------------------------------------------------------------------
Issue Analytics
- State:
- Created 7 years ago
- Comments:15
Top Results From Across the Web
Verify your deployment - Google Cloud
You can configure Google Cloud Deploy and Skaffold to verify that an application that you have deployed to any target is working correctly....
Read more >Verifying Deployment: FAILED using MUP for my meteor app
I am developing under Windows: Node V8.9.0; NPM V5.5.1. My app working well locally without any issue. Need help to solve this problem...
Read more >Mup Deploy verifying deployment failed · Issue #923 - GitHub
Mup fails at the last step of deployment. I am using VulcanJs. Mup version 1.4.3 Mup config { "servers": { "one": { "host":...
Read more >Re-running a failed container deployment job - IBM
If the deployment of a container fails, first investigate and address the cause for the failure. Check the ibacc.log file for details of...
Read more >Step 5: Verify your deployment - AWS CodeDeploy
To verify the deployment was successful, follow the instructions in View CodeDeploy deployment details , and then return to this page. If the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is most often because the verification is not waiting long enough for the app to finish starting up. See my issue #265
@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)