Skip to content

Upgrade Problem from 2.8.9 to 2.8.10

Moved 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
  • Nodebb and emails

    Solved Configure
    25
    4 Votes
    25 Posts
    15 Views

    @Panda experience, plus this

    https://www.fastmail.help/hc/en-us/articles/1500000279921-IMAP-POP-and-SMTP

  • Test of youtube embeds

    Solved Configure
    14
    11 Votes
    14 Posts
    250 Views

    @phenomlab Perfect!!! Many thanks.

  • Pulling YouTube videos using RSS

    Configure
    5
    6 Votes
    5 Posts
    134 Views

    The perfect solution and walkthrough Mark, appreciated as always!

  • MogoDB v6 to v7 upgrade

    Solved Configure
    5
    1 Votes
    5 Posts
    505 Views

    @Panda if you used the Ubuntu PPA, I think this only goes as far as 6.x if I recall correctly.

  • Getting Eror When Started NodeBB

    Solved Configure
    7
    2 Votes
    7 Posts
    506 Views

    @phenomlab yes i did.

    i deleted one of plugin then it started to work normally.

  • mongodb replica set

    Configure
    11
    2 Votes
    11 Posts
    526 Views

    @veronikya said in mongodb replica set:

    The host’s local dns resolution is not configured. The problem of the host’s hosts being unable to be resolved in docker has been solved. Surprisingly
    Solution:
    Edit the /etc/resovel.conf file
    Add 127.0.0.53

    One immediate issue I can think of here is that editing resolv.conf directly is no longer supported and not recommended (because the changes do not survive a reboot) - unless you install the resolvconf package?

  • Category For User

    Solved Configure
    11
    12 Votes
    11 Posts
    534 Views

    3.5.1 has now been released. I’ve just deployed it, so safe to do so!

  • NodeBB: Upgrading to NodeBB v3.x

    Solved Configure
    6
    0 Votes
    6 Posts
    329 Views

    @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.