Warning: connect.sid session cookie not detected. User may have cookies disabled or session cookie has expired

[Matthew de Detrich]

I have a website using SS in production and I have gotten these errors

Warning: connect.sid session cookie not detected. User may have cookies disabled or session cookie has expired

It seems that the issue is the cookies have expired due to time reasons. Is there a way to set cookies to never expire through SS

[Kyle Mueller]

I'm sure this doesn't apply to your install, but I've also run into this error and thought that I might document it in case someone else runs into the issue.

After pushing my code to a new machine, I started to receive this error. After thinking about how I'd set up session storage, I remembered that I'd enabled the following configuration:

ss.session.store.use('redis'); 

It turns out I had not installed redis and therefore the redis server wasn't available on the new box.

After I installed and started redis on the new box, the issue went away.

This most likely won't help you. But, I thought I would share the info anyway.

Good luck!

[Matthew de Detrich]

Just come to say, I am getting this problem again, and I can guarantee that redis is working fine in my case (I am inspecting the redis database in realtime and sessions are being added/stopped)

Owen can you give some insight into this matter, its causing production apps to stop working?

[Anephenix]

Hi, are you still being affected by this issue?

[Matthew de Detrich]

Well the problem hasn't come up yet, as I said it happens randomly and after long periods of time (its happening on apps that are running for extended periods of time on nodejitsu). It makes it incredibly difficult to diagnose

[Anephenix]

From: https://github.com/socketstream/socketstream/blob/master/doc/guide/en/sessions.md

Are you setting this in your app.js file?

ss.session.options.maxAge = 8640000;  // one day in milliseconds

The default in SocketStream is 30 days:

    https://github.com/socketstream/socketstream/blob/master/lib/http/index.js#L22

Hope that helps,

Paul

[Matthew de Detrich]

No I am not, but thanks for showing it to me

I guess I need to make it expire in years or something (or to set it to net expire)