Nonspecific error when running 'mup.cmd reconfig'

I’ve got an old Telescope Meteor App that I deployed a few years ago which I’m trying to ‘reconfig’ to point to a new database. (Compose.Io required me to upgrade Mongo versions)

I feel like I’ve almost got it… but am now getting sort of a ‘nonspecific’ error when I run ‘mup.cmf reconfig’

Started TaskList: Configuring App
[104.131.53.195] - Pushing the Startup Script
[104.131.53.195] - Pushing the Startup Script: SUCCESS
[104.131.53.195] - Sending Environment Variables
[104.131.53.195] - Sending Environment Variables: SUCCESS

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

          ------------------------------------STDERR------------------------------------
          tion closed
        at Object.Future.wait (/bundle/bundle/programs/server/node_modules/fibers/future.js:398:15)
        at new MongoConnection (packages/mongo/mongo_driver.js:213:1)
        at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:1)
        at Object.<anonymous> (packages/mongo/remote_collection_driver.js:38:1)
        at Object.defaultRemoteCollectionDriver (packages/underscore/underscore.js:750:1)
        at new Mongo.Collection (packages/mongo/collection.js:102:1)
        at AccountsServer.AccountsCommon (accounts_common.js:23:18)
        at new AccountsServer (accounts_server.js:16:5)
        at Package (globals_server.js:5:12)
        at /bundle/bundle/programs/server/packages/accounts-base.js:1814:4
        - - - - -
        at [object Object].<anonymous> (/bundle/bundle/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/server.js:608:24)
        at [object Object].emit (events.js:92:17)
        at [object Object].<anonymous> (/bundle/bundle/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:171:15)
        at [object Object].emit (events.js:98:17)
        at Socket.<anonymous> (/bundle/bundle/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/connection.js:550:12)
        at Socket.emit (events.js:95:17)
        at TCP.close (net.js:466:12)
    npm WARN deprecated This version of npm lacks support for important features,
    npm WARN deprecated such as scoped packages, offered by the primary npm
    npm WARN deprecated registry. Consider upgrading to at least npm@2, if not the
    npm WARN deprecated latest stable version. To upgrade to npm@2, run:
    npm WARN deprecated
    npm WARN deprecated   npm -g install npm@latest-2
    npm WARN deprecated
    npm WARN deprecated To upgrade to the latest stable version, run:
    npm WARN deprecated
    npm WARN deprecated   npm -g install npm@latest
    npm WARN deprecated
    npm WARN deprecated (Depending on how Node.js was installed on your system, you
    npm WARN deprecated may need to prefix the preceding commands with `sudo`, or if
    npm WARN deprecated on Windows, run them from an Administrator prompt.)
    npm WARN deprecated
    npm WARN deprecated If you're running the version of npm bundled with
    npm WARN deprecated Node.js 0.10 LTS, be aware that the next version of 0.10 LTS
    npm WARN deprecated will be bundled with a version of npm@2, which has some small
    npm WARN deprecated backwards-incompatible changes made to `npm run-script` and
    npm WARN deprecated semver behavior.
    npm WARN package.json meteor-dev-bundle@0.0.0 No description
    npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
    npm WARN package.json meteor-dev-bundle@0.0.0 No README data
    => Starting meteor app on port:80

    /bundle/bundle/programs/server/node_modules/fibers/future.js:278
                                                    throw(ex);
                                                          ^
    Error: connection closed
        at Object.Future.wait (/bundle/bundle/programs/server/node_modules/fibers/future.js:398:15)
        at new MongoConnection (packages/mongo/mongo_driver.js:213:1)
        at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:1)
        at Object.<anonymous> (packages/mongo/remote_collection_driver.js:38:1)
        at Object.defaultRemoteCollectionDriver (packages/underscore/underscore.js:750:1)
        at new Mongo.Collection (packages/mongo/collection.js:102:1)
        at AccountsServer.AccountsCommon (accounts_common.js:23:18)
        at new AccountsServer (accounts_server.js:16:5)
        at Package (globals_server.js:5:12)
        at /bundle/bundle/programs/server/packages/accounts-base.js:1814:4
        - - - - -
        at [object Object].<anonymous> (/bundle/bundle/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/server.js:608:24)
        at [object Object].emit (events.js:92:17)
        at [object Object].<anonymous> (/bundle/bundle/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:171:15)
        at [object Object].emit (events.js:98:17)
        at Socket.<anonymous> (/bundle/bundle/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/connection.js:550:12)
        at Socket.emit (events.js:95:17)
        at TCP.close (net.js:466:12)

    => Redeploying previous version of the app

Also - I already tried running: ‘npm -g install npm@latest’ on my local system… maybe I need to run that on the Digital Ocean droplet?

I guess I’m hesitant to mess with anything on the actual droplet because so much of it must be out of date from being deployed 3 years ago. I really thought I could just point it to the new database URL and be done with it.