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 💗

  • crazycellsundefined

    problem with search page and copyright in footer

    Solved Bugs
    13
    6 Votes
    13 Posts
    87 Views
    crazycellsundefined

    @phenomlab yes, search page is fixed 🙂 thanks 👍

  • cagatayundefined

    Loading Image Problem

    Bugs
    24
    6 Votes
    24 Posts
    1k Views
    cagatayundefined

    Thank you Mark.

  • Pandaundefined

    Composer options on nodebb

    Solved Configure
    8
    3 Votes
    8 Posts
    289 Views
    phenomlabundefined

    @Panda You should be able to expose the CSS for these using F12 to get into console

    3591518c-e3a3-4ada-a43c-6b32a5e0359c-image.png

    a2b8ed46-4157-4ff2-85f0-576543380107-image.png

    That should then expose the element once selected

    89d9c545-a47a-40d1-98f4-80cf3b958e8f-image.png

    Here’s the below CSS you need based on the screenshot provided.

    .composer .formatting-bar .formatting-group li[data-format="picture-o"], .composer .formatting-bar .formatting-group li[data-format="spoiler"] { display: none; }
  • mventuresundefined

    NodeBB: Consent page

    Solved Configure
    16
    4 Votes
    16 Posts
    559 Views
    phenomlabundefined

    @DownPW I still do not see any issues.

  • mventuresundefined

    NodeBB: Upgrading to NodeBB v3.x

    Solved Configure
    6
    0 Votes
    6 Posts
    229 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 pages

    Solved Configure
    9
    0 Votes
    9 Posts
    279 Views
    mventuresundefined

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

  • mventuresundefined

    NodeBB: Privileges for the Announcement channel

    Solved Configure
    6
    1 Votes
    6 Posts
    188 Views
    phenomlabundefined

    Up to you really 🙂

  • marusakyundefined

    Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    783 Views
    phenomlabundefined

    @marusaky based on the work completed thus far (in relation to PM exchanges), I’m going to mark this completed. Sending email from the server itself works fine without issue, and DNS appears to be clean (valid SPF, DMARC, and DKIM records).

    It appears that only Gmail marks incoming messages from your domain as spam - perhaps because of the domain age, which there is nothing we can do to prevent this. Mail delivery to all other domains appears to work fine in al of my tests.