Help installing nodeBB on a VPS

General Discussion

Suggested Topics


  • 0 Votes
    2 Posts
    92 Views

    Ok, I think I got it - had to drop the original db before restoring. Now it seems to work #fingerscrossed

  • 0 Votes
    5 Posts
    328 Views

    I'm not really sure what you're trying to do here - if you want to copy a repository to a local folder you should use git clone and not git checkout - the latter is used for switching branches and generally moving to a different version of a repository.
    However, got should not be used to install a plugin. NPM is the utility you're looking for. It supports two methods of authentication for GitHub private repositories - OAuth and SSH.

    For OAuth you'll need to generate a personal access token (settings>developer settings>personal access tokens) with permission to read private repositories (just repository permissions if I remember correctly), and then go to the main NodeBB directory and use npm install git+https://<github_token>:[email protected]/NodeBB/nodebb-plugin-xxx.git

    If you prefer to use SSH instead, follow the instructions here to generate the keys and add to your account, and then run in the main NodeBB folder npm install git+ssh://[email protected]/NodeBB/nodebb-plugin-xxx.git

  • 0 Votes
    2 Posts
    1k Views

    Hmm. I figured it out. My miniscule understanding of iptables does not allow me to explain this, but if I move the rule for port 4567 up in the chain, it works. I thought they should just be going down the chain rules. Missing something here. Anyway, the issue seems to be resolved. If someone could explain why - this would be interesting to know.

    Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
    pkts bytes target prot opt in out source destination
    2590K 1747M ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
    159 13356 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0
    222 13300 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0
    25 1420 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22
    0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:4567
    0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:2080
    54 2736 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:443
    0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:1002
    0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:5666
    0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:8140
    0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:4545
    0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:5222
    0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:5269
    574 45099 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:161
    0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:162
    11540 1407K REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited
    0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:6379
    0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:80

  • 0 Votes
    5 Posts
    2k Views

    @julian Not a problem. It's back. Hope to find gold!

  • 0 Votes
    4 Posts
    2k Views

    Thanks, @julian. I just finished the hardware migration of these VMs and I want to move them to a more stable hypervisor/host than my former Windows 7 desktop with VMWare workstation, so this is timely advice.