Stuck in a loop during install

Technical Support

Suggested Topics


  • 0 Votes
    2 Posts
    165 Views

    Why did you run the repair command? What's the output of the mongo -u admin -p your_password --authenticationDatabase=admin command?

  • 0 Votes
    1 Posts
    330 Views

    Hi everyone !!

    I am trying to install NodeBB in my local environment to test how everything goes but I am unable to perform the installation.

    I manage to do

    docker run nodebb/docker

    And it says that is live in 4567. However, when I launch localhost:4567 its stuck in a loading white screen.

    I also tried this installation with docker guide, but I am not able to install Redis, and it is the first step:

    When I try any of these commands:

    docker run --name my-forum-redis -d -p 6379:6379 nodebb/docker:centos-redis docker run --name my-forum-redis -d -p 6379:6379 nodebb/docker:ubuntu-redis

    It returns: Error response from daemon: manifest for nodebb/docker:centos-redis not found: manifest unknown: manifest unknown

    Does anybody know how to perform the installation with Docker?
    Thanks in advance.

  • 0 Votes
    2 Posts
    176 Views

    It should be essentially the same. I can't think of anything that would be different.

  • 0 Votes
    2 Posts
    1k Views

    Hmm looks like sharp isn't installing correctly. If you wanna try out some stuff, here's this:

    https://sharp.dimens.io/en/stable/install/

  • 1 Votes
    1 Posts
    620 Views

    Hi,

    I'm having some troubles getting NodeBB up-and-running on Heroku. I've followed the official documentation and I seem to have followed every step correctly. I am however having troubles with the very last step unfortunately and I was hoping someone might be able to help me!

    Step 13: Initialise a single dyno: heroku ps:scale web=1

    Here's what happens in Terminal:

    MacBook-Pro% heroku ps:scale web=1
    Scaling dynos... !
    ▸ Couldn't find that formation.

    I've searched around the net already and some have mentioned it may be an issue with having an extension on the Procfile. I have checked this and there is no extension.

    I'm so close but yet so far! Has anyone encountered this issue before?! Any help would be greatly appreciated!

    Best regards,

    Marty.