Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

[solved] NPM install killed during recent install

Bug Reports

2

3

2555

Log in to reply

Tanner Plugin & Theme Dev last edited by Tanner

Here's the gist of the error that I got:

Seems that something in the process killed it, on a brand new install.
1 Reply Last reply
Reply Quote 0
Julian Lam GNU/Linux Admin last edited by

OSError: [Errno 12] Cannot allocate memory this might have something to do with it?
1 Reply Last reply
Reply Quote 0
Tanner Plugin & Theme Dev @julian last edited by

@julian That's got to be it, thanks mate!
1 Reply Last reply
Reply Quote 0

Suggested Topics

H

Install nodeBB on Windows Server
General Discussion • problem install error compiler • • Hectopascal

11

1
Votes

11
Posts

5811
Views

H

Thank you for your support 👍
K

[Solved] There was an error updating your profile! Email not available!
Bug Reports • • kelso

3

0
Votes

3
Posts

1189
Views

K

@julian You know, I didnt even think of that. Yes, changing emails, and I will check that out (will feel stupid now lol)
S

Fresh install - User bugs again
Bug Reports • online user install clean • • Scuzz

12

0
Votes

12
Posts

4063
Views

S

noticed it here too. I'll update and see if it fixes.
R

Installing NodeBB on Google Cloud Platform
Technical Support • google cloud platform nodebb install config • • Raydekk

5

0
Votes

5
Posts

3120
Views

R

ok, I think I solved it.

Apparently, after executing commands like

sudo firewall-cmd --zone=public --add-masquerade --permanent
sudo firewall-cmd --zone=public --add-forward-port=port=80:proto=tcp:toport=8000 --permanent
sudo iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 8000

somewhat screwed up the firewall rules in the google console. The catch was that I could only acces the website from port 80, by trying to acces it from 8000(node's actual) didn't work. I deleted the rules, and added them again in the platform console (Networking->Firewall rules) and then restarted nodebb and it worked!
S

[Solved] Bug when logging in
Bug Reports • • San1ty

8

0
Votes

8
Posts

1986
Views

Ok - at present the underlying websockets library will attempt to connect using websockets first, and failing that, drops down to ajax polling. This is why it takes a couple seconds.

As long as you eventually get connected, it's okay, although we do realise that it is a problem for some people.

| |

Copyright © 2021 NodeBB | Contributors

1 / 1