Connection lost to the forum

Technical Support

Suggested Topics


  • the count of emails that forum sends

    Unsolved Technical Support
    3
    0 Votes
    3 Posts
    258 Views

    email statistics of the forum · Issue #10598 · NodeBB/NodeBB

    https://community.nodebb.org/topic/16478/the-count-of-emails-that-forum-sends It would be nice to see how many emails forum is sending each day/week/month... We think we are coming close to our free" tier" email plan with our daily usage...

    favicon

    GitHub (github.com)

  • 0 Votes
    1 Posts
    452 Views

    Hey there!

    I have a nodebb instance i've been customizing through theming and plugins.

    I recently came across an issue that has prevented me from running ./nodebb start

    Clustering enabled: Spinning up 4 process(es).

    2019-07-22T06:23:35.139Z [4567/15633] - info: Initializing NodeBB v1.12.2 https://kratomwatchdog.com 2019-07-22T06:23:35.431Z [4567/15633] - error: NodeBB could not connect to your Mongo database. Mongo returned the following errorconnect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"],"stack":"MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017\n at Socket.err (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:287:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at emitErrorNT (internal/streams/destroy.js:66:8)\n at _combinedTickCallback (internal/process/next_tick.js:139:11)\n at process._tickCallback (internal/process/next_tick.js:181:9)"} 2019-07-22T06:23:35.443Z [4567/15633] - error: connect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"]} 2019-07-22T06:23:35.446Z [4568/15638] - error: NodeBB could not connect to your Mongo database. Mongo returned the following errorconnect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"],"stack":"MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017\n at Socket.err (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:287:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at emitErrorNT (internal/streams/destroy.js:66:8)\n at _combinedTickCallback (internal/process/next_tick.js:139:11)\n at process._tickCallback (internal/process/next_tick.js:181:9)"} 2019-07-22T06:23:35.448Z [4568/15638] - error: connect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"]} 2019-07-22T06:23:35.449Z [4569/15640] - error: NodeBB could not connect to your Mongo database. Mongo returned the following errorconnect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"],"stack":"MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017\n at Socket.err (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:287:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at emitErrorNT (internal/streams/destroy.js:66:8)\n at _combinedTickCallback (internal/process/next_tick.js:139:11)\n at process._tickCallback (internal/process/next_tick.js:181:9)"} [cluster] Child Process (15633) has exited (code: 0, signal: null) 2019-07-22T06:23:35.454Z [4569/15640] - error: connect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"]} [cluster] Child Process (15638) has exited (code: 0, signal: null) [cluster] Child Process (15640) has exited (code: 0, signal: null) 2019-07-22T06:23:35.462Z [4570/15645] - error: NodeBB could not connect to your Mongo database. Mongo returned the following errorconnect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"],"stack":"MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017\n at Socket.err (/home/ubuntu/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connect.js:287:16)\n at Object.onceWrapper (events.js:315:30)\n at emitOne (events.js:116:13)\n at Socket.emit (events.js:211:7)\n at emitErrorNT (internal/streams/destroy.js:66:8)\n at _combinedTickCallback (internal/process/next_tick.js:139:11)\n at process._tickCallback (internal/process/next_tick.js:181:9)"} 2019-07-22T06:23:35.464Z [4570/15645] - error: connect ECONNREFUSED 127.0.0.1:27017 {"name":"MongoNetworkError","errorLabels":["TransientTransactionError"]} [cluster] Child Process (15645) has exited (code: 0, signal: null)

    I am able to run nodebb in dev mode, and have had to run it in a screens session to keep the forum online until i'm able to resolve the issue.

  • too connection lost error

    Technical Support
    22
    0 Votes
    22 Posts
    4k Views

    @pichalite said in too connection lost error:

    @sanatisharif use "port": ["4567", "4568", "4569"]

    in cluster mod I have lots of connection lost err in front end ( for mobile users )

  • 0 Votes
    3 Posts
    2k Views

    @Dravere I tried this but it didn't seem to resolve the problem for me. I don't have the sites in sub-folders - I'm using different ports instead i.e 4567 and 4566

    I added the code here:

    Made the session cookie aware of the possible relative path by Dravere · Pull Request #4663 · NodeBB/NodeBB

    When you run two NodeBB forums on the same host but in different subfolders (e.g. http://example.com/tf1/ and http://example.com/tf2/) the session cookies will interfer with each other, because their path is set to '/'. This small change sets the path of the session cookies to the relative path if the relative path is set. The cookies for the socket.io have their path already set correctly. So no change is necessary there.

    favicon

    GitHub (github.com)

  • 1 Votes
    8 Posts
    16k Views

    @Absam-Sibsam you saved me bro, worked perfectly!