Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7818049
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 2, 20262026-06-02T06:26:42+00:00 2026-06-02T06:26:42+00:00

After updating my mongo client to 2.0.2 the error has changed significantly. New issue

  • 0

After updating my mongo client to 2.0.2 the error has changed significantly.

New issue opened here: MongoDB connect error

when I try to connect to my mongo server, running on a Vagrant VM, CentOS 6, i get this magical error shown here: http://pastium.org/view/7efba4e90f0ba228ccad377204bb9f17.

Vagrant forwards the standard mongo part to 37017.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-02T06:26:43+00:00Added an answer on June 2, 2026 at 6:26 am

    Turns out this was an issue with IP Tables so the forwarded port was getting blocked.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

After updating to php 5.3 one of our systems has developed an interesting bug.
I get a strange PHP error after updating my php version to 5.4.0-3. I
after updating my grails app's security plugins, i get the following error when deploying
I try updating my database after updating the dataset, but evenafter calling the data
This error happened after updating to latest may 2009 CTP. Sometimes I do not
Each document of couchdb will have a new version after updating, and the previous
After updating my ubuntu from 10.04 to 11.04, I opened eclipse and wondered why
After updating to rubygems 1.5.0, I get this error message when trying to run
I am running into a VerifyError after updating my Xoom to 3.1. Here is
Is it possible to get the number of affected rows, after updating data? Here

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.