Failed default login about semaphore HOT 7 CLOSED

From past experience, this seems like a sessions issue. Either sessions aren't being persisted or the sessions middleware is updated and doesn't work as expected..

For some reason we don't have a lockdown on dependency versions yet so it might have happened that you installed a too-new version of the session middleware.

from semaphore.

Try the following:

1. Copy this file to npm-shrinkwrap.json
2. Delete node_modules folder
3. npm install again
4. report back

from semaphore.

Hello,

After replacing the file it says "Login successful" briefly, then redirect to login page.

from semaphore.

Hmm but you need to re-install all node dependencies. The file tells npm which version to install.

Are you running redis?

from semaphore.

No redis. I think i did the npm install after deleting node_modules before, but however now i get

npm WARN unmet dependency /home/andreas/semaphore/node_modules/bower/node_modules/inquirer requires chalk@'^0.5.0' but will load
npm WARN unmet dependency /home/andreas/semaphore/node_modules/bower/node_modules/chalk,
npm WARN unmet dependency which is version 1.1.1
npm WARN unmet dependency /home/andreas/semaphore/node_modules/bower/node_modules/handlebars/node_modules/uglify-js requires async@'~0.2.6' but will load
npm WARN unmet dependency /home/andreas/semaphore/node_modules/async,
npm WARN unmet dependency which is version 1.4.2

so probably i need to reinstall all ..

from semaphore.

Hmm you need to have redis. It might be failing quietly.

All sessions are stored in redis.

from semaphore.

thank you., that was it!

2015-12-07 12:15 GMT+01:00 Matej Kramny [email protected]:

Hmm you need to have redis. It might be failing quietly.

All sessions are stored in redis.

—
Reply to this email directly or view it on GitHub
#52 (comment)
.

from semaphore.