Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

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

Installation via shell access

matamrd last edited by

Hello all,
Because of budget issues, I would like to install nodebb on shared hosting only. I have access to shell. I guess I can install if i have access to shell. Could you please say procedure as I can't find anywhere. Namecheap shared hosting uses cloudlinux OS and gives users to access shell
Reply Quote 0
1 Reply Last reply

1
Posts

52
Views

Suggested Topics

M

Fresh Install Admin Forbidden. Is 32 bit a problem?
Technical Support • • merp

3

1
Votes

3
Posts

1248
Views

M

Pulling from Master helped. However the webpage that starts NodeBB after setting up the DB through the webpage, doesn't restart it now. I had to kill the command line, and manually start nodeBB. But then it works fine. Just an FYI.
S

Websocket connection problems via ssl on special port
Technical Support • • suparomana

7

1
Votes

7
Posts

2511
Views

@suparomana said in Websocket connection problems via ssl on special port: Apache 2.2 can not handle websockets Ahh, thanks. Okay, that makes sense now. It sounds like it's failing because of the special port. Since that port is sending directly to NodeBB and not through the Apache proxy, NodeBB does not know the SSL key, so it will fail the connection. I think there used to be a way to feed the SSL Key path to NodeBB in config.json, but I don't see any docs on it anymore, and I'm not even sure if that would work. I think your best bet is to try getting websockets to work through Apache2, there seems to be several methods even though there's no official support.
B

Installing from docker Hub results in v0.5?
Technical Support • • baretomas

1

0
Votes

1
Posts

373
Views

B

Hello and thanks for a great forum software! I've been playing with a docker hosted nodeBB instance, but all I'm getting from the docker hub is a v0.5 of NodeBB. Is there any reason the docker hub has such an old version? Can I avoid this somehow? Thanks! Tomas
Upgrade: show progress
Feature Requests • upgrade shell progress • • Nicolas

1

0
Votes

1
Posts

959
Views

Would be nice to see upgrade progress for ./nodebb upgrade. Thanks
L

Installing on Digital Ocean
Technical Support • • Luchris

8

0
Votes

8
Posts

1775
Views

K

It is okay to see that package.json is there. use this command npm install -g http-server@latest or npm init -y and populate package.json file later with your taste.

| |

Installation via shell access

Suggested Topics

Fresh Install Admin Forbidden. Is 32 bit a problem? Technical Support • • merp

Websocket connection problems via ssl on special port Technical Support • • suparomana

Installing from docker Hub results in v0.5? Technical Support • • baretomas

Upgrade: show progress Feature Requests • upgrade shell progress • • Nicolas

Installing on Digital Ocean Technical Support • • Luchris

Fresh Install Admin Forbidden. Is 32 bit a problem?
Technical Support • • merp

Websocket connection problems via ssl on special port
Technical Support • • suparomana

Installing from docker Hub results in v0.5?
Technical Support • • baretomas

Upgrade: show progress
Feature Requests • upgrade shell progress • • Nicolas

Installing on Digital Ocean
Technical Support • • Luchris