Anyone else on AMS2 through digital ocean?

General Discussion

Suggested Topics

  • 1 Votes
    19 Posts

    Hey mate 🙂

    Why do I get the error below:
    2015-04-01T07:02:19.625-0400 E QUERY Error: couldn't add user: not authorized on nodebb to execute command { createUser: "user, roles: [ "readWrite" ], digestPassword: false, writeConcern: { w: "majority", wtimeout: 30000.0 } }
    at Error (<anonymous>)
    at DB.createUser (src/mongo/shell/db.js:1066:11)
    at (shell):1:4 at src/mongo/shell/db.js:1066

    I get error like this whenever i tried to do sometime like show collections or show databases

    Why do i get this error?

  • 1 Votes
    7 Posts

    @luke said:

    @a_5mith Even if you need to update NodeBB?

    Believe so. Taken from this blog post

    I'm glad to say that I did end up figuring out the second problem, and NodeBB now comes with a "Reload" functionality in addition to the existing "Restart":

    The results?

    Reloads are now transparent and do not kick existing connections off. Admins used to be afraid to swap plugins because a server restart incurred downtime. Not anymore!

    Occasionally, incompatible plugins break NodeBB. The new reload system will catch errors as they occur, display them to the admin, and continue serving the old assets, meaning NodeBBs will no longer be left dead in the water when a plugin breaks.

    End users won't notice a reload, as connections are maintained. Restart downtimes are reduced to near-zero, as a parallel instance is started and seamlessly switched over when ready.

  • 0 Votes
    5 Posts


    I'm not sure how well it will work with digital ocean though. Works well with a dedicated server though!

  • 0 Votes
    8 Posts

    DO support helped. My site is up again :happy:

  • 0 Votes
    20 Posts

    @julian They judge that DO claims rights to do things with user content, like publishing it, beyond reason, and it's too much to the potential disadvantage to the user.