NPM package versions and NodeBB
-
Does anyone know of a good set of working versions?
I am about fed up with trying to get a new install spun up.
See my thread over on the NodeBB forums..
https://community.nodebb.org/topic/9915/new-install-leaves-me-with-session-mismatch-invalid-csrf
I made my instruction thread using current versions. I have tried older versions.
The install completes fine, but the system is not usable.
-
Will get you the ML versions when I can. On the road right now.
-
@scottalanmiller said in NPM package versions and NodeBB:
Will get you the ML versions when I can. On the road right now.
I am trying to find a reason for the failures here. My gaming forum is running nodejs 6.9.0 and i just updated to 1.4.0 (git pull on the v1.x.x tag) from 1.3.0 with no problems last night.
So I have no idea what is different that is causing the problem.
My game forum uses Redis, while I am trying to setup this new system with Mongo.
-
It looks like I used nvm originally.
[root@daermabb ~]# nvm --version 0.13.1
And I installed node v0.12.7 and v0.12.9
But something has upgrade/changed it since then as npm says it is using v6.9.1
[root@daermabb ~]# npm version { npm: '3.10.8', ares: '1.10.1-DEV', http_parser: '2.7.0', icu: '50.1.2', modules: '48', node: '6.9.1', openssl: '1.0.1e-fips', uv: '1.9.1', v8: '5.1.281.84', zlib: '1.2.7' } [root@daermabb ~]#
-
/sigh this is so frustrating. I feel like I am going to have break down and just export the existing VM for my personal site and import it for this.
I have no idea why things are not working.
-
ML is using NodeJS 6.9.1
-
Here is what we have...
[root@lnj-lnx-mangolassi ~]# npm version { npm: '3.10.8', ares: '1.10.1-DEV', http_parser: '2.7.0', icu: '50.1.2', modules: '48', node: '6.9.1', openssl: '1.0.1e-fips', uv: '1.9.1', v8: '5.1.281.84', zlib: '1.2.7' }
-
We, we seriously match. LMAO
-
@JaredBusch Did you see this thread?
-
@Danp said in NPM package versions and NodeBB:
@JaredBusch Did you see this thread?
No, but I get the issue when going direct to the local private ip and port http://10.254.0.35:4567
So that should not apply.
-
@JaredBusch What about the cookieDomain portion?