Buy Hosting

Website auto stop

Unsolved Bug Reports

Suggested Topics

  • JaredBuschJ

    Composer preview auto size issue

    Bug Reports
    0 Votes
    3 Posts
    2k Views
    JaredBuschJ

    @baris said in Composer preview auto size issue:

    This is already reported here https://github.com/NodeBB/NodeBB/issues/5208

    Cool

  • П

    NodeBB v1.0.4-auto.2 many crashes

    Bug Reports
    0 Votes
    1 Posts
    837 Views
    П

    NodeBB v1.0.4-auto.2

    29/5 02:45 [782] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised. 29/5 02:45 [779] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised. (node) warning: possible EventEmitter memory leak detected. 11 connect listeners added. Use emitter.setMaxListeners() to increase limit. 29/5 02:45 [774] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised. Trace at Socket.addListener (events.js:252:17) at Socket.Readable.on (_stream_readable.js:673:33) 29/5 02:45 [779] - info: [app] Database connection closed. 29/5 02:45 [774] - info: [app] Database connection closed. at Socket.once (events.js:278:8) 29/5 02:45 [779] - info: [app] Web server closed to connections. 29/5 02:45 [774] - info: [app] Web server closed to connections. at Socket.unref (net.js:1013:10) 29/5 02:45 [779] - info: [app] Shutdown complete. 29/5 02:45 [774] - info: [app] Shutdown complete. at Connection.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/connection/connection.js:453:23) at /home/wing/nodebb/node_modules/mongodb-core/lib/connection/pool.js:189:7 at Array.forEach (native) at Pool.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/connection/pool.js:182:15) at Server.destroy (/home/wing/nodebb/node_modules/mongodb-core/lib/topologies/server.js:1072:31) at Server.close (/home/wing/nodebb/node_modules/mongodb/lib/server.js:417:17) 29/5 02:45 [782] - info: [app] Database connection closed. 29/5 02:45 [782] - info: [app] Web server closed to connections. 29/5 02:45 [782] - info: [app] Shutdown complete. [cluster] Child Process (774) has exited (code: 0, signal: null) [cluster] Child Process (779) has exited (code: 0, signal: null) [cluster] Child Process (782) has exited (code: 0, signal: null)
  • S

    When you update Nodebb to latest code,guest and normal user can't see the website.

    Bug Reports
    0 Votes
    8 Posts
    3k Views
    julianJ

    @song19891121 The permissions were refactored so that by default, if a category has no permissions checked (in the Access Control modal), nobody can access it.

    This is a departure from the previous behaviour, which was:

    Registered users can access and post Guests can access but cannot post

    Which was confusing for some.

    Long story shot

    The upgrade script should transparently convert your existing permissions properly, but clearly there are some bugs. When you upgrade, go through all of your categories and ensure the permissions are set correctly.

  • S

    after I using git pull,I can't start my website.

    Bug Reports
    0 Votes
    10 Posts
    4k Views
    ?

    Ah, after some sleep and reviewing your post again, I can confirm that the net.js error message you are seeing is caused by a plugin. If you paste your entire console log here, we'll be able to show you where it is giving the plugin issue.

    I'm simply having the issue of my NodeBB will start in dev mode, but will not start in normal mode.

  • TannerT

    Stopped and will not start again

    Bug Reports
    0 Votes
    23 Posts
    6k Views
    D

    Anytime 😉

Copyright © 2023 NodeBB | Contributors