Error Timed Out while waiting for handhsake - While setup docker
See original GitHub issueHello, my trouble here, is that I can’t ‘mup setup’…
When I try to run mup setup, I have this output :
Started TaskList: Setup Docker
[1.2.3.4] - setup docker
Error Timed out while waiting for handshake
So, I tried to see the logs, but even if I do mup logs, I have the same output… “Error timed out while waiting for handshake”
And this is my mup.js
module.exports = {
servers: {
one: {
host: '1.2.3.4',
username: 'root'
// pem:
// password:
// or leave blank for authenticate from ssh-agent
}
},
meteor: {
name: 'app',
path: '../app',
servers: {
one: {}
},
buildOptions: {
serverOnly: true,
},
env: {
ROOT_URL: 'app.com',
MONGO_URL: 'mongodb://localhost/meteor'
},
//dockerImage: 'kadirahq/meteord'
deployCheckWaitTime: 60
},
mongo: {
oplog: true,
port: 27017,
servers: {
one: {},
},
},
};
Issue Analytics
- State:
- Created 7 years ago
- Comments:20
Top Results From Across the Web
mup setup : Error: Timed out while waiting for handshake #865
Hi All, Problem here is when I am trying to run command mup setup there is error... Started TaskList: Setup Docker [54.186.xx.xxx] -...
Read more >mup setup : Error: Timed out while waiting for handshake
The problem may be that you cannot SSH with your current IP address. For instance, if you are using AWS, make sure that...
Read more >DigitalOcean timeout while waiting for handshake - Bobcares
Firstly, check for ssh misconfigurations. Check if there is any firewall rule, which is configured to limit ssh and port to your ip...
Read more >question - Microsoft Learn
SSH CONNECTION CLOSE - Error: Timed out while waiting for handshake while connecting to .scm.azurewebsites.net/webssh/host.
Read more >digitalocean timeout while waiting for handshake
First check the set of rules of your default UFW firewall: sudo ufw status numbered Now check the default port of your SSH:...
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 Free
Top 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
Hi All, I am also facing the same issue. My mup.js file looks like, ` module.exports = { servers: { one: { host:‘54.186.xx.xxx’, username: ‘ubuntu’, pem: ‘~/.ssh/mypem.pem’ } }, app: { name: ‘myapp’, path: ‘/var/www/meteor/myapp’, servers: { one: {}, }, buildOptions: { serverOnly: true, }, env: { ROOT_URL: ‘http://ec2-54-186-xx-xxx.us-west-2.compute.amazonaws.com’, MONGO_URL: ‘mongodb://127.0.0.1:27017/myapp’, PORT: 3027, },
docker: { image: ‘abernix/meteord:node-8.4.0-base’, }, deployCheckWaitTime : 60, enableUploadProgressBar: true }, mongo: { port:27017, version: ‘3.4.1’, servers: { one: {} } } }; `
Meteor version is 1.6. Thanks in advance!
@rollin-s http://prntscr.com/czluhp http://prntscr.com/czluyk open sftp http://prntscr.com/czlvqp find the folder opt and open it, that’s the folder where your app is deploy too http://prntscr.com/czlwnj http://prntscr.com/czm34s you might be able to change that in those to files. I’m doing a test really fast to make sure this work right tho. if that doesnt work, delete everything in opt and then meteor mup setup meteor mup deploy your folder will show back up. If you use digital ocean, you can delete your droplet and create a new one.