NodeBB 1.19.3

[phenomlab]

@DownPW Potentially dumb question, but why is the path /home/nodebb/nodebb ?

Also, why are you trying to install the 18.x branch when you should be using 19.x ?

I see

cd /home/nodebb
git clone -b v1.18.x https://github.com/NodeBB/NodeBB.git nodebb
cd nodebb

This should be

cd /home/nodebb
git clone -b v1.19.x https://github.com/NodeBB/NodeBB.git nodebb
cd nodebb

[DownPW]

I have test to install 1.19.x too and i have error too

[phenomlab]

@DownPW and you are executing ./nodebb setup from the correct directory ?

[DownPW]

@phenomlab

yes

[DownPW]

I think they really have a problem on the github and coincidentally it’s a plugin on which they had big problems that was in question. (emoji)

[phenomlab]

@DownPW Looking at the error message, I’d say you’re right.

[DownPW]

@phenomlab

here a gif for the problem of perf.
On a clean install of nodeBB on a clean install server VM

The problem is just when I refresh the page entierly or ACP access

No problem on 1.18.x or 1.19.2

very odd

[phenomlab]

@DownPW Looks like that’s waiting for a response from something. Have you run this site through the F12 developer tools -> Network tab to see where the delay is ?

[DownPW]

@phenomlab

Thanks for the tip

chance

[phenomlab]

@DownPW 8ms is nothing - less than one second… ?

[DownPW]

@phenomlab

you not see at the good place
EDIT:

coincidence? Emoji CSS failed !
I don’t believe

I think we put the finger on something

[phenomlab]

@DownPW Yes, you’re right. For some strange reason, that CSS file is not being served - but should be on your server if you check the path.

[DownPW]

yes it still here

EDIT:

I have remove the directory when I have the problem of install with 1.18.x

But when I upgrade to 1.19.3, he have reinstalled by default

[phenomlab]

@DownPW I see this

[DownPW]

@phenomlab on your website ?

[phenomlab]

@DownPW No - on yours.

[DownPW]

ha lol ok

[DownPW]

@phenomlab

because you are guest maybe because not me

[DownPW]

test admin:nodebb

[phenomlab]

@DownPW Same error when logged in