Problem Connecting to mongodb

Discussion in 'ISPConfig 3 Priority Support' started by conductive, Apr 10, 2019.

  1. conductive

    conductive Member HowtoForge Supporter

    I am having a problem connecting with mongodb.

    [email protected]:/etc# mongo
    MongoDB shell version: 3.2.11
    connecting to: test
    > show dbs
    admin 0.000GB
    gDev 0.000GB
    local 0.000GB
    myCustomers 0.000GB

    My firewall Open TCP ports: 20,21,22,25,53,80,110,143,443,587,993,995,3306,8080,8081,10000, 27017, 27018, 27019, 9090
    Open UDP ports: 53,3306

    #bind_ip =
    port = 27017

    # Enable journaling,

    # Enables periodic logging of CPU utilization and I/O wait
    #cpu = true

    # Turn on/off security. Off is currently the default
    #noauth = true
    auth = true


    Host is up (0.097s latency).
    rDNS record for xx.xx.xx.xx:
    Not shown: 983 filtered ports
    20/tcp closed ftp-data
    21/tcp open ftp
    22/tcp open ssh
    25/tcp open smtp
    53/tcp open domain
    80/tcp open http
    110/tcp open pop3
    143/tcp open imap
    443/tcp open https
    587/tcp open submission
    993/tcp open imaps
    995/tcp open pop3s
    3306/tcp open mysql
    8080/tcp open http-proxy
    8081/tcp open blackice-icecap
    9090/tcp closed zeus-admin
    10000/tcp closed snet-sensor-mgmt

    Nmap done: 1 IP address (1 host up) scanned in 29.88 seconds

    What do I need to do here?

    Thanks for your help.
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    I've never used MongoDB and it is not part of ISPConfig setups, so I can't help you with that problem.
  3. conductive

    conductive Member HowtoForge Supporter

    mongo the NOSQL is supposed to be easier but I am wondering.

    Shouldn't I at least be able to see it at this point? could it be UDP or??
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    You can use e.fg. netstat to find out to which IP and port mongodb is listening on. Try e.g.:

    netstat -tap | grep mongo
  5. conductive

    conductive Member HowtoForge Supporter

    Thanks Till,
    I am attempting to use 27017. Does this look OK?

    [email protected]:~# netstat -tap | grep mongo
    tcp 0 0 localhost.localdo:27017* LISTEN 3022/mongod
    tcp 0 0 localhost.localdo:59964 localhost.localdo:27017 ESTABLISHED 26340/mongo
    tcp 0 0 localhost.localdo:27017 localhost.localdo:59964 ESTABLISHED 3022/mongod
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    MongoDB listens on localhost only, so you can connect only from the same server and not from another external client or server.

    try e.g.:

    bind_ip = ::,

    in mongodb.conf to let it bind to all IPv4 and IPv6 IP addresses.

Share This Page