@dark-shy maybe it's just because you don't have any traffic yet. Is any other functionality broken?
Group Details Private
Staff
Employees & Interns of NodeBB
Member List
-
RE: have problem with install on vm
-
RE: have problem with install on vm
@dark-shy You got it coming out, nice!
Do you see any errors in the browser developer console?
-
RE: Section name not being included in breadcrumb
No no no no no. Comment out the line with
var meta
. The one that shows up at the top of the error message you posted. Make sure you uncomment all of those other things.This is not a bug in NodeBB. As the error message clearly says, the variable
meta
was already declared in that scope in library.js. (Asconst meta ...
) -
RE: help 安装出错,帮我看看
@qiancsf I deleted your new topic. Please don't make new ones
-
RE: Search bar navigation fails if user clicks slowly
This should be fixed on master and on this forum as well.
-
RE: have problem with install on vm
@dark-shy if it's working on
http://localhost:80
then it's likely not an nginx problem given your config. You can runlsof -n -i:80
to make sure, you should see nginx there. -
RE: help 安装出错,帮我看看
@qiancsf it's because you're running as root that npm can't kind find the git executable. As I said before, create a new unprivileged user and install and run nodebb under it.
-
RE: help 安装失败
@qiancsf don't install NodeBB as root. Create an unprivileged user to install and run NodeBB under.
You need to install
git
. -
RE: have problem with install on vm
@dark-shy the fix is to update those plugins so they use
require.main.require('./src/user')
instead ofmodule.parent.require('./user')
. But if you aren't the developer of those plugins, there's nothing you can do, so just disable them or ignore the errors for now. They aren't causing the issue.Since you can access NodeBB on
http://localhost:4567
, this means NodeBB is running.Since you can access NodeBB on
http://localhost:80
, this means that nginx is (at least partially) working.Since you cannot access NodeBB on
http://your.ip:80
, this means that there's something blocking requests into your server. It may be a firewall on your server, or it may be something upstream from that. Do you mind sharing more information about your setup?