Embark on a journey of knowledge! Take the quiz and earn valuable credits.
Take A QuizChallenge yourself and boost your learning! Start the quiz now to earn credits.
Take A QuizUnlock your potential! Begin the quiz, answer questions, and accumulate credits along the way.
Take A QuizGeneral Tech Bugs & Fixes 2 years ago
Posted on 16 Aug 2022, this text provides information on Bugs & Fixes related to General Tech. Please note that while accuracy is prioritized, the data presented might not be entirely correct or up-to-date. This information is offered for general knowledge and informational purposes only, and should not be considered as a substitute for professional advice.
No matter what stage you're at in your education or career, TuteeHub will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
General Tech 10 Answers
General Tech 7 Answers
General Tech 3 Answers
General Tech 9 Answers
Ready to take your education and career to the next level? Register today and join our growing community of learners and professionals.
manpreet
Best Answer
2 years ago
So I installed MongoDB v4.0 on an Ubuntu 18.10 VM running on Google Compute Engine. Installed successfully, working well with the
mongo
shell via SSH. Now I wanted to access the database remotely from my desktop.Following this guide, I edited my
/etc/mongod.conf
file and commented out thebind_ip
line in the following code:net:
port: 27017
# bindIp: 127.0.0.1
Restarted the service
service mongod restart
Also opened the TCP port 27017 on the Google Cloud Platform Firewall.
However, the database is still inaccessible via all means, i.e. the
mongo
shell installed on my local machine, MongoDB Compass, theserver_ip:27017
format on Google Chrome, all fail to connect.I ran
sudo netstat -tlnp
via SSH on the VM,I only got the following line for MongoDB:
tcp 0 0 127.0.0.1:27017 0.0.0.0:* LISTEN 18490/mongod
The
0.0.0.0
line which should have been there indicating that it is open to all connections was still missing.Can this possibly be a configuration error or is some internal firewall blocking the connection?
Edit: I even made sure iptables isn't causing this. Issued the commands
iptables -A INPUT -p tcp --destination-port 27017 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -p tcp --source-port 27017 -m state --state ESTABLISHED -j ACCEPT
Still no luck