Skip to content
Sudonix

Getting Eror When Started NodeBB

Solved Configure

Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

Related Topics
  • crazycellsundefined

    problem with search page and copyright in footer

    Solved Bugs
    13
    6 Votes
    13 Posts
    388 Views
    crazycellsundefined

    @phenomlab yes, search page is fixed 🙂 thanks 👍

  • cagatayundefined

    Loading Image Problem

    Bugs
    24
    6 Votes
    24 Posts
    2k Views
    cagatayundefined

    Thank you Mark.

  • mventuresundefined

    NodeBB: Upgrading to NodeBB v3.x

    Solved Configure
    6
    0 Votes
    6 Posts
    318 Views
    phenomlabundefined

    @mventures You’d need to connect to the server and execute it directly - not on your local terminal. Review the guide below, which will show you how to gain access via SSH to your server

    https://docs.ovh.com/gb/en/dedicated/ssh-introduction/

    Once you have access, you’ll need to navigate to the actual folder where NodeBB is installed

    You’ll then need to change to the directory as shown below

    /home/unbuntu/nodebb

    fdffe673-bf63-4b6d-a728-5506fddc1aff-image.png

    In most cases, initial access takes you to the root of the file system. You can always issue pwd in a Linux terminal which will show you the Present Working Directory. From there, you can issue the command

    cd /home/ubuntu/nodebb

    Once in the NodeBB directory, you’d use the below commands

    ./nodebb stop git fetch && git checkout develop && git reset --hard origin/develop ./nodebb upgrade ./nodebb start

    Line 1 stops the NodeBB instance
    Line 2 gets the latest files from GIT (repository) and then checks out the development branch. It then resets the version you are using to the development branch ready for v3
    Line 3 Runs the upgrade once the new branch is set, and code pulled
    Line 4 Restarts the NodeBB instance after the upgrade has completed

    Note that when you restart NodeBB and log back in, things will look very different to what you had in v2.

  • mventuresundefined

    NodeBB: Creating the Swatch modes

    Solved Configure
    2
    0 Votes
    2 Posts
    187 Views
    phenomlabundefined

    @mventures the swatch feature you refer to isn’t a NodeBB plugin, but a utility that I wrote that handles this. It is available for v2 (as you can see here) but I’ve stopped developing and releasing the code because it has been entirely rewritten to work for v3.

    If you’d like the code, this is possible, but you’ll need to upgrade to v3 first.

  • mventuresundefined

    NodeBB: Creating pages

    Solved Configure
    9
    0 Votes
    9 Posts
    477 Views
    mventuresundefined

    OK, I think I have figured out how to place a link in the footer which will click to a new page.

  • Pandaundefined

    restarting nodebb on boot

    Unsolved Configure
    3
    1 Votes
    3 Posts
    310 Views
    phenomlabundefined

    @eeeee said in restarting nodebb on boot:

    can I just run nodebb under nodemon for auto restarts?

    It’s a better method. Nodemon just looks for file system changes and would effectively die if the server was rebooted meaning you’d have to start it again anyway. Systemd is the defacto standard which is how the operating system interacts in terms of services, scheduled tasks etc.

  • cagatayundefined

    Gettin Erors NodeBB

    Solved Configure
    7
    0 Votes
    7 Posts
    440 Views
    cagatayundefined

    @phenomlab no forum is working goods.
    there is no eror message since yestarday.

  • kurulumuNetundefined

    nodebb dropdown menu

    Solved Configure
    5
    0 Votes
    5 Posts
    531 Views
    JACundefined

    @phenomlab said in nodebb dropdown menu:

    @kurulumu-net You set it like the below example taken from this site

    aae36790-3257-4bb2-ad5a-0d744309876a-image.png

    Which presents this

    77f47260-2941-4afe-9614-8e17dcfc8c19-image.png

    Very interesting…

    I actually thought this wasn’t possible, as I remember it being asked in the NodeBB forum.

    Is this something new that’s been implemented? I’ll 100% be doing that when I’m on the laptop over the weekend.