Server at mongodb:27017 reports maximum wire version 5, but this version of the Node.js Driver requires at least 6
  • 17-May-2023
Lightrun Team
Author Lightrun Team
Server at mongodb:27017 reports maximum wire version 5, but this version of the Node.js Driver requires at least 6

Server at mongodb:27017 reports maximum wire version 5, but this version of the Node.js Driver requires at least 6

Lightrun Team
Lightrun Team

Explanation of the problem


The issue arises when using the Mup (Meteor Up) deployment tool with the provided configuration. After attempting to start the Meteor app using the mup command, the deployment verification fails, and an error is encountered. The error message indicates a connection refusal to the specified port (3000) on the server ( Additionally, a MongoDB server selection error is reported, indicating a version incompatibility between the Node.js driver and the MongoDB server. The following code blocks illustrate the relevant sections of the configuration and the encountered errors:


  "servers": {
    "one": {
      "host": "",
      "username": "root",
      "password": "password"
  "app": {
    "name": "my-app",
    "docker": {
      "image": "zodern/meteor:latest",
      "imagePort": 3000
    "mongo": {
      "version": "3.4.1"
    // Other app configurations...
  // Other Mup configurations...




Started TaskList: Start Meteor
[] - Start Meteor
[] - Start Meteor: SUCCESS
[] - Verifying Deployment
[] x Verifying Deployment: FAILED

(7) Failed to connect to port 3000: Connection refused
MongoServerSelectionError: Server at mongodb:27017 reports maximum wire version 5, but this version of the Node.js Driver requires at least 6 (MongoDB 3.6)


Troubleshooting with the Lightrun Developer Observability Platform


Getting a sense of what’s actually happening inside a live application is a frustrating experience, one that relies mostly on querying and observing whatever logs were written during development.
Lightrun is a Developer Observability Platform, allowing developers to add telemetry to live applications in real-time, on-demand, and right from the IDE.

  • Instantly add logs to, set metrics in, and take snapshots of live applications
  • Insights delivered straight to your IDE or CLI
  • Works where you do: dev, QA, staging, CI/CD, and production

Start for free today

Problem solution for: Server at mongodb:27017 reports maximum wire version 5, but this version of the Node.js Driver requires at least 6


To resolve the encountered issues, the following steps can be taken:

  1. Addressing the Connection Refusal Error: The connection refusal error suggests that the specified port (3000) on the server ( is not accessible. This can be due to various reasons, such as a misconfiguration or a firewall restriction. To troubleshoot and resolve the issue, the following considerations can be helpful:
    • Ensure that the server’s IP address, username, and password are correct in the Mup configuration.
    • Verify that the necessary network ports are open and accessible for the application to function properly.
    • Check for any firewall rules or security groups that may be blocking the connection to the specified port.
    • Review the server logs or error messages for any additional insights into the connection refusal.
  2. Resolving the MongoDB Version Incompatibility: The MongoDB server selection error indicates a mismatch between the Node.js driver version and the MongoDB server version. To address this, the following steps can be followed:
    • Upgrade the MongoDB server to a version that supports a wire version of at least 6 (e.g., MongoDB 3.6 or higher).
    • Update the Mup configuration to specify the correct MongoDB version that matches the server’s version. In this case, setting "version": "3.6" in the "mongo" section of the configuration might resolve the compatibility issue.
    • Ensure that the connection string ("MONGO_URL") in the app’s environment variables is correctly pointing to the MongoDB server and includes the appropriate authentication credentials if required.

By addressing these steps, it should be possible to resolve the connection refusal error and the MongoDB version incompatibility, allowing the Meteor app to deploy and function properly.


Problems with meteor-up


Problem 1: Deployment Failure with Meteor-Up (Mup)

Problem Description: One common issue encountered when using Meteor-Up (Mup) for deployment is a failure during the deployment process. This can manifest in various ways, such as a failed task or an error message indicating an unsuccessful deployment attempt. The following code block demonstrates an example of a failed deployment output:


Started TaskList: Start Meteor
[] - Start Meteor
[] - Start Meteor: SUCCESS
[] - Verifying Deployment
[] x Verifying Deployment: FAILED


Solution: To resolve the deployment failure with Mup, several steps can be taken:

  1. Review Deployment Logs: Start by reviewing the deployment logs for more specific error messages or hints about the cause of the failure. Logs can provide valuable information to identify the underlying issue and guide the troubleshooting process.
  2. Check Configuration: Verify the accuracy and completeness of the Mup configuration file. Ensure that all required fields, such as server details, app name, Docker image settings, and other relevant options, are correctly specified. Pay attention to any syntax errors or missing values in the configuration.
  3. Debugging and Troubleshooting: Use debugging techniques to identify the root cause of the deployment failure. This may involve checking server logs, examining network connectivity, investigating dependencies, or running specific commands for further diagnostics.

Problem 2: Connection Issues with MongoDB

Problem Description: Another common problem encountered with Meteor-Up involves connection issues with MongoDB. This can be due to incorrect MongoDB settings or misconfigurations in the Mup configuration file. Symptoms of this problem can include MongoDB connection errors or failures to access the database during the deployment process.

Solution: To address MongoDB connection issues in Mup, follow these steps:

  1. Verify MongoDB Configuration: Double-check the MongoDB configuration within the Mup file. Ensure that the MongoDB version specified in the configuration matches the actual version installed on the server. Additionally, review the MongoDB connection string ("MONGO_URL") and confirm that it accurately points to the MongoDB server and includes the necessary authentication credentials if applicable.
  2. Test Database Connectivity: Validate the connectivity to the MongoDB server from the deployment environment. This can involve executing MongoDB client commands or using tools like mongo or mongodump to establish a connection and interact with the database.
  3. Check Firewall and Network Settings: Ensure that the necessary network ports are open and accessible for the MongoDB server. Confirm that any firewalls or security groups are not blocking the connection between the deployment server and the MongoDB server.

Problem 3: Version Compatibility Issues

Problem Description: Version compatibility issues can arise when deploying with Meteor-Up if there are discrepancies between the versions of Meteor, Node.js, or other dependencies specified in the project and the Mup configuration. These discrepancies can lead to runtime errors or failures during the deployment process.

Solution: To resolve version compatibility issues in Meteor-Up, consider the following steps:

  1. Update Dependencies: Ensure that the Meteor app and its dependencies are up to date. This includes updating the versions of Meteor packages, Node.js, npm, and any other relevant dependencies. It is recommended to follow the official documentation and release notes for the respective tools and packages to identify any specific version requirements or compatibility considerations.
  2. Verify Mup Compatibility: Confirm that the version of Meteor-Up being used is compatible with the versions of Meteor and Node.js in the project. Check the Meteor-Up repository, release notes, or documentation for information about compatibility and recommended version combinations.
  3. Pin Dependencies: If necessary, explicitly specify the versions of dependencies in the project’s package.json or other configuration files. This helps ensure consistent versions across different deployment


A brief introduction to meteor-up


Meteor-Up (Mup) is a deployment tool designed specifically for Meteor applications. It provides a streamlined process for deploying Meteor apps to remote servers, making it easier to manage and scale applications in production environments. Mup leverages Docker and other technologies to simplify the deployment workflow and ensure consistency across different deployments.

With Mup, developers can define their deployment configuration using a JavaScript-based configuration file. This configuration file allows specifying various settings, such as server details, app name, Docker image settings, environment variables, and more. Mup takes care of bundling the Meteor app, transferring it to the remote server, and setting up the necessary infrastructure components, such as Node.js, MongoDB, and proxy configurations. It automates the deployment process, saving developers time and effort.

Mup also provides features like environment variable management, SSL certificate integration, and rollback capabilities. It supports deploying to multiple servers, making it suitable for scaling applications across clusters or load-balanced environments. Mup simplifies the management of infrastructure and provides a consistent deployment experience, making it a popular choice among Meteor developers for deploying their applications efficiently.


Most popular use cases for meteor-up


  1. Deployment Automation: Meteor-Up (Mup) simplifies the deployment process for Meteor applications by automating various tasks. It allows developers to define their deployment configuration using a JavaScript-based file, specifying details such as server information, app name, and Docker image settings. Here’s an example of a Mup configuration file:


module.exports = {
  servers: {
    one: {
      host: '123.456.789.0',
      username: 'root',
      password: 'password',
  app: {
    name: 'my-app',
    path: '/path/to/app',
    servers: {
      one: {},
    buildOptions: {
      serverOnly: true,
    env: {
      ROOT_URL: '',
      MONGO_URL: 'mongodb://mongodb:27017/my-app',


  1. Scalability and Load Balancing: Mup supports deploying Meteor applications to multiple servers, allowing for scalability and load balancing. By configuring multiple servers in the Mup configuration file, developers can distribute the application workload across multiple instances, improving performance and handling higher traffic volumes. This can be achieved by defining server clusters or utilizing load balancers in conjunction with Mup.
  2. Infrastructure Management: Mup simplifies the management of infrastructure components required for running Meteor applications. It automates the setup of essential components like Node.js, MongoDB, and reverse proxies. Mup handles the bundling and transfer of the Meteor app to the remote server, ensuring a consistent deployment experience. Developers can easily manage environment variables, SSL certificates, and rollback capabilities through the Mup configuration file, streamlining the management of the application’s infrastructure.



It’s Really not that Complicated.

You can actually understand what’s going on inside your live applications.

Try Lightrun’s Playground

Lets Talk!

Looking for more information about Lightrun and debugging?
We’d love to hear from you!
Drop us a line and we’ll get back to you shortly.

By submitting this form, I agree to Lightrun’s Privacy Policy and Terms of Use.