Hi and thanks @baris,
Just switched to v.1.7.0 and it works like a charm 🙂
I try to install NodeBB with PuTTY on VPS(Debian 7) but i've problem with Redis.
$ ── UNMET PEER DEPENDENCY redisearch@^0.0.6
$ └─┬ email@example.com
$ └── firstname.lastname@example.org
$ npm WARN email@example.com requires a peer of redisearch@^0.0.6 but none was installed.
Someone can help me ? i think i don't do error on my code, i've followed https://docs.nodebb.org/vi/latest/installing/os/debian.html
@Noksouls try installing redisearch
npm i redisearch
npm ERR! Linux 3.2.0-4-amd64
npm ERR! argv "node" "/usr/bin/npm" "install" "redissearch"
npm ERR! node v0.10.29
npm ERR! npm v3.5.1
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/redissearch
npm ERR! 404
npm ERR! 404 'redissearch' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! Please include the following file with any support request:
npm ERR! /root/nodebb/npm-debug.log
npm r redisearch npm i redisearch
10/12 21:41  - info: Now configuring redis database:
Host IP or address of your Redis instance (...)
Host port of your Redis instance (22)
Password of your Redis database
Which database to use (0..n) (1)
Configuration Saved OK
Populating database with default configs, if not already set...
10/12 21:41  - error: Error: Auth error: 2.0-OpenSSH_6.0p1 Debian-4+deb7u2
at Command.callback (/root/nodebb/node_modules/redis/index.js:212:43)
at RedisClient.return_error (/root/nodebb/node_modules/redis/index.js:558:25)
at ReplyParser.<anonymous> (/root/nodebb/node_modules/redis/index.js:305:18)
at ReplyParser.emit (events.js:95:17)
at RedisClient.on_data (/root/nodebb/node_modules/redis/index.js:534:27)
at Socket.<anonymous> (/root/nodebb/node_modules/redis/index.js:91:14)
at Socket.emit (events.js:95:17)
at Socket.<anonymous> (_stream_readable.js:748:14)
Someone can help me ? I don't understand my error ...
Auth error suggests that there is a problem with username/password - check config.json
If that is not the case, then check that you can connect to redis as that user, using that password.
Ok i think it's the password, but i don't know what is my Redis Database password, where i can find it?
Are you connecting to the right IP & port? (According to the installer you have used port 22 before)
This is the IP and the port of my VPS, i think it is good ^^
So your Redis install is locally installed? As on your own VPS.
I think yes
@Noksouls What host do you use?
VPS on OVH, i use PuTTY for control ^^
@Noksouls port 22 is for SSH (default anyways). Don't think your redis is running on port 22. Check the port and specify the correct port in the NodeBB config file.
I try the port 80
$ Populating database with default configs, if not already set...
$ 11/12 18:47  - error: NodeBB could not connect to your Redis database. Redis returned the following error: Redis connection to XX.XXX.XXX.XX:80 failed - connect ECONNREFUSED
The IP it's the IP of my VPS, i don't know if it's good
@Noksouls it won't be running on port 80. Default port for redis is 6379. First check if you have redis installed.
Enter this at the prompt
redis-cli. If redis is installed and running, the prompt will change and will most likely show you the port number redis is running on.
It's good !!! Thank you very much
But when i'm connecting to the adress there is a problem :ERR_CONNECTION_REFUSED
I think it's a problem with my VPS but i don't know where it is.
I do "forum IN A XX.XXX.XXX.XX" on my NDD (the IP is the IP of my VPS)
My NodeBB config :
$ URL used to access this NodeBB (forum.guilde-arkadia.fr)
$ Please enter a NodeBB secret (X)
$ Wich database to use (redis)
$ Host IP or adress of your Redis instance (127.0.0.1)
$ Host port of your Redis instance (6379)
$ Password of your Redis database
$ Wich database to use (0..n) (1)
But when i try to connect to the adress forum.guilde-arkadia.fr i have the message : ERR_PROXY_CONNECTION_FAILED
You think it's a problem with the config or with the VPS?