ERROR: connect ECONNREFUSED 127.0.0.1:27017
See original GitHub issueHello,
I try to run image from docker hub and i got this error .ERROR: connect ECONNREFUSED 127.0.0.1:27017
my docker-compose.yml
version: 3.7
services:
ytdl_material:
image: tzahi12345/youtubedl-material:nightly
container_name: youtubedl-material
restart: unless-stopped
volumes:
- ./data/appdata:/app/appdata
- ./data/audio:/app/audio
- ./data/video:/app/video
- ./data/subscriptions:/app/subscriptions
- ./data/users:/app/users
environment:
UID: 1006
GID: 1006
ALLOW_CONFIG_MUTATIONS: 'true'
ports:
- 17442:17442
networks:
- youtubedl-material
Issue Analytics
- State:
- Created a year ago
- Comments:15 (2 by maintainers)
Top Results From Across the Web
MongoError: connect ECONNREFUSED 127.0.0.1:27017
My apps stopped working after upgrading from Nodejs 14 to 17. The error I got was MongoServerSelectionError: connect ECONNREFUSED ::1:27017.
Read more >Connect ECONNREFUSED 127.0.0.1:27017 in ...
Means that NO mongod instance is running at the given host 127.0.0.1 and port 27017. Yes the solution is to start mongod. Mah_Neh:...
Read more >Mongodb connection error - YouTube
Hello guys, in this video i will tell you the solution of MongoNetworkError connect ECONNREFUSED 127.0.0.127017 while we try to run mongosh ...
Read more >ECONNREFUSED 127.0.0.1:27017 | Resolve the connection ...
This video will demonstrate a way how you can resolve the error " connect ECONNREFUSED 127.0.0.1:27017". So this is a connection issue that ......
Read more >Let solve this error together. [connect ECONNREFUSED ...
Let solve this error together. [ connect ECONNREFUSED 127.0.0.1:27017]. Mongodb compass connection. 447 views447 views. Oct 25, 2022.
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
I had the same problem and turned on logging for the mongodb container. Turns out that in my case mongodb was throwing an error and refusing to start. This is because on the newer versions of mongo (v5+) they have a requirement for ARM builds where the host CPU must meet the ARM spec ARMv8.2-A. I guess raspberry pi 4 doesn’t meet that or it can’t detect that it can when in docker. Either way I just set the image to an older version:
TL;DR mongodb version 5+ doesn’t work on raspberry pi 4 in docker, so I set the mongodb image to v4.4.6
Thanks for reply.
@GlassedSilver I was debugging and found that by default tries to connect to mongodb and when its not found after few retries it uses json.
So basically default image is working fine just need to wait few minutes.