Failed to connect to 172.17.0.5 port 80 in Verifying Deployment stage
See original GitHub issueI am getting the below error in the verifying deployment stage of mup deploy:
Mup version: 1.4.4
Mup config
{
"servers": {
"one": {
"host": "1.2.3.4",
"username": "root",
"password": "password"
}
},
"proxy": {
"domains": "xxxx.com",
"ssl": {
"letsEncryptEmail": "xxxx@gmail.com",
"forceSSL": true
}
},
"mongo": {
"version": "3.4.1",
"servers": {
"one": {}
}
},
"app": {
"name": "my-app",
"path": "../xxxx",
"volumes": {
"/images": "/images"
},
"servers": {
"one": {}
},
"buildOptions": {
"serverOnly": true
},
"env": {
"ROOT_URL": "https://host.com",
"MONGO_URL": "mongodb://mongodb:27017/my-app",
"VIRTUAL_HOST": "xxxx.com",
"HTTPS_METHOD": "redirect",
"HTTP_FORWARDED_COUNT": 1,
"LETSENCRYPT_HOST": "xxxx.com",
"LETSENCRYPT_EMAIL": "xxxx@gmail.com"
},
"docker": {
"image": "programthis/meteor-gm",
"args": [
"--link=mongodb:mongodb"
]
},
"enableUploadProgressBar": true,
"type": "meteor"
}
}
Output of command
[159.203.61.14] - Verifying Deployment
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to 172.17.0.5 port 80: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to 172.17.0.5 port 80: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to 172.17.0.5 port 80: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to 172.17.0.5 port 80: Connection refused
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to 172.17.0.5 port 80: Connection refused
Which is then followed by:
[159.203.61.14] x Verifying Deployment: FAILED
------------------------------------STDERR------------------------------------
or-node-stubs/node_modules/events
http-browserify@1.7.0 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/http-browserify
Base64@0.2.1 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/Base64
https-browserify@0.0.1 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/https-browserify
os-browserify@0.2.1 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/os-browserify
path-browserify@0.0.0 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/path-browserify
process@0.11.9 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/process
punycode@1.4.1 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/punycode
querystring-es3@0.2.1 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/querystring-es3
readable-stream@2.2.10 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/readable-stream
process-nextick-args@1.0.7 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/process-nextick-args
safe-buffer@5.0.1 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/safe-buffer
string_decoder@1.0.1 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/string_decoder
util-deprecate@1.0.2 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/util-deprecate
stream-browserify@2.0.1 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/stream-browserify
timers-browserify@1.4.2 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/timers-browserify
tty-browserify@0.0.0 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/tty-browserify
url@0.11.0 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/url
punycode@1.3.2 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/url/node_modules/punycode
querystring@0.2.0 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/querystring
vm-browserify@0.0.4 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/vm-browserify
indexof@0.0.1 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/indexof
balanced-match@0.4.2 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/balanced-match
brace-expansion@1.1.7 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/brace-expansion
concat-map@0.0.1 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/concat-map
fs.realpath@1.0.0 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/fs.realpath
glob@7.1.2 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/glob
inflight@1.0.6 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/inflight
once@1.4.0 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/once
wrappy@1.0.2 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/wrappy
minimatch@3.0.4 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/minimatch
path-is-absolute@1.0.1 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/path-is-absolute
rimraf@2.6.1 /bundle/bundle/programs/server/npm/node_modules/meteor-node-stubs/node_modules/rimraf
mongo-object@0.1.2 /bundle/bundle/programs/server/npm/node_modules/mongo-object
simpl-schema@1.5.0 /bundle/bundle/programs/server/npm/node_modules/simpl-schema
sweetalert2@7.19.3 /bundle/bundle/programs/server/npm/node_modules/sweetalert2
{
"npm": "5.3.0",
"ares": "1.10.1-DEV",
"cldr": "31.0.1",
"http_parser": "2.7.0",
"icu": "59.1",
"modules": "57",
"nghttp2": "1.22.0",
"node": "8.4.0",
"openssl": "1.0.2l",
"tz": "2017b",
"unicode": "9.0",
"uv": "1.13.1",
"v8": "6.0.286.52",
"zlib": "1.2.11"
}
added 136 packages in 65.32s
=> Starting meteor app on port:80
=> Redeploying previous version of the app
------------------------------------STDOUT------------------------------------
=> Container status:
restarted: 0 times {"Bridge":"","SandboxID":"53c4aa70e6f28a91c379b1f24504d49e7bc5f3db9c87a0290822e5adc30dedba","HairpinMode":false,"LinkLocalIPv6Address":"","LinkLocalIPv6PrefixLen":0,"Ports":{"80/tcp":null},"SandboxKey":"/var/run/docker/netns/53c4aa70e6f2","SecondaryIPAddresses":null,"SecondaryIPv6Addresses":null,"EndpointID":"3ff5d46d8bdf9263c0a0aa453c9e62e7a3c63ea78ca450297efd3ab8060243d0","Gateway":"172.17.0.1","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"IPAddress":"172.17.0.5","IPPrefixLen":16,"IPv6Gateway":"","MacAddress":"02:42:ac:11:00:05","Networks":{"bridge":{"IPAMConfig":null,"Links":null,"Aliases":null,"NetworkID":"9094e5dea0457f2d8cc18a782a78b69a5a2282b9b1b7c10a4df8c7cf445f72a0","EndpointID":"3ff5d46d8bdf9263c0a0aa453c9e62e7a3c63ea78ca450297efd3ab8060243d0","Gateway":"172.17.0.1","IPAddress":"172.17.0.5","IPPrefixLen":16,"IPv6Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"MacAddress":"02:42:ac:11:00:05","DriverOpts":null}}} {"Status":"running","Running":true,"Paused":false,"Restarting":false,"OOMKilled":false,"Dead":false,"Pid":31481,"ExitCode":0,"Error":"","StartedAt":"2018-05-06T23:54:40.333255605Z","FinishedAt":"0001-01-01T00:00:00Z"}
=> Logs:
To see more logs type 'mup logs --tail=200'
------------------------------------------------------------------------------
Issue Analytics
- State:
- Created 5 years ago
- Comments:19 (3 by maintainers)
Top Results From Across the Web
Mup deploy failed at verification, 172.17.0.4 port 80
0.3 to 172.17.0.4 to 172.17.0.5 . So far the deployment still fails at verification, with the same error messages but IP Address is...
Read more >Troubleshooting "Port 80 in use issue" - Anash's Knowledge ...
Symptoms. The reason for this error is that some other application is already using port 80. Only one application can listen to a...
Read more >Docker & Kubernetes : Pods and Service definitions - 2021
TargetPort: a port on the Pod where an actual web server is running, port 80. This is called target port because that's the...
Read more >Troubleshooting - NGINX Ingress Controller - Kubernetes
One possible reason for this error is lack of permission to bind to the port. Ports 80, 443, and any other port <...
Read more >Kubernetes DNS for Services and Pods - Medium
See how to install kubectl here. First, let's create a Deployment with three Python HTTP servers that listen on the port 80 for...
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
Thanks @99darwin, comparing your mup configuration with mine helped me fix the issue.
Everyone, change the
docker.image
to ‘abernix/meteord:node-8.4.0-base’ and the error will be gone. There is a problem with ‘abernix/meteord:base’.@programthis Mup might not have waited long enough for the app to start. This is fixed by Prepare Bundle, which is only enabled by default for certain images. Setting
app.docker.prepareBundle
totrue
in your config should fix it.@marcoschwartz could you please show the output after
Verifying Deployment
when runningmup deploy --verbose
?