error message after unsuccesful login attempts with not exist user

<baris>

Please check your nodebb logs for any errors.

fstdesk

thank you @baris

i runned ./nodebb log and there is no error in the log.

runned ./nodebb dev and result is ;

15/5 18:23:29 [4220] - error: Error: listen EADDRINUSE 0.0.0.0:4567
at Object.exports._errnoException (util.js:870:11)
at exports._exceptionWithHostPort (util.js:893:20)
at Server._listen2 (net.js:1237:14)
at listen (net.js:1273:10)
at net.js:1382:9
at nextTickCallbackWith3Args (node.js:452:9)
at process._tickCallback (node.js:358:17)
15/5 18:23:29 [4220] - error: NodeBB address in use, exiting...
3 restarts in 10 seconds, most likely an error on startup. Halting.

julian

That's not the error @baris needs. That's related to your NodeBB already running and you attempting to run it again.

Please stop NodeBB completely and start again, and try logging in with a non-existant user, and then check the logs via (./nodebb log)

fstdesk

@julian thanks
i made everything you said. but not fixed.

root@ip-172-5:/home/ubuntu# cd /var/www/NodeBB
root@ip-172-5:/var/www/NodeBB# ./nodebb stop
Stopping NodeBB. Goodbye!
root@ip-172-5:/var/www/NodeBB# ./nodebb start

Starting NodeBB
"./nodebb stop" to stop the NodeBB server
"./nodebb log" to view server output
"./nodebb restart" to restart NodeBB

root@ip-172-5:/var/www/NodeBB# ./nodebb log

Hit Ctrl-C to exit

node_redis: Warning: Redis server does not require a password, but a password was supplied.
16/5 17:24:53 [9723] - info: [socket.io] Restricting access to origin: http://mydomain.com
node_redis: Warning: Redis server does not require a password, but a password was supplied.
node_redis: Warning: Redis server does not require a password, but a password was supplied.
node_redis: Warning: Redis server does not require a password, but a password was supplied.
node_redis: Warning: Redis server does not require a password, but a password was supplied.
16/5 17:24:53 [9723] - info: Routes added
16/5 17:24:53 [9723] - info: NodeBB Ready
16/5 17:24:53 [9723] - info: Enabling 'trust proxy'
16/5 17:24:53 [9723] - info: NodeBB is now listening on: 0.0.0.0:4567

fstdesk

i tried everyting, reinstalled nodebb. but i get same error. Any idea please.

thanks

julian

Those logs do not show a NodeBB crash, unfortunately, so we cannot help you yet.

fstdesk

today nodebb stopped suddenly and my site turn 502. after i start nodebb again the error has disappeared. how can i learn why nodebb stopped. there is no data in log.

note; error came back after 1 hour.

fstdesk

i tried more times, i installed nodebb more times ( with redis). same issue. when i try to login with non exist user nodebb stops ( to test when i try 5 times to login with non exist user nodebb stops) . and i get Internal Error. Oops! Looks like something went wrong! error. i read all instrunctions but no success. *server is ubuntu 16.04 on aws ec2 *

fstdesk

finally fixed.

i think it was an issue about redis. i reinstalled nodebb with mongo and there is no error.

notes;

when i was trying to login with non-exist user with nodebb/redis it was giving errors and error message was only Login Unsuccessful and nodebb was stopping after 5 attemps.

and now if i try to login with non-exist user with nodebb/mongo error message is Login Unsuccessful
invalid-login-credentials
and nodebb does not stop.

the only thing i am wondering now is ./nodebb dev results.

they are;

19/5 15:25:42 [1707] - error: Error: listen EADDRINUSE 0.0.0.0:4567
at Object.exports._errnoException (util.js:1018:11)
at exports._exceptionWithHostPort (util.js:1041:20)
at Server._listen2 (net.js:1258:14)
at listen (net.js:1294:10)
at net.js:1404:9
at _combinedTickCallback (internal/process/next_tick.js:83:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
19/5 15:25:42 [1707] - error: NodeBB address in use, exiting...
3 restarts in 10 seconds, most likely an error on startup. Halting.

<baris>

Looks like a bug on that only happens when using redis, thanks for reporting.