"WARN Cookie members-ssr not found" each GET command

Hey everyone

I am a new Ghost user but really love the platform. I am seeing this following WARN in ghost log on every command that gets logged, post view, url, page etc.
WARN Cookie members-ssr not found

Strange that Google offers no answers on this one. The error was happening on Ghost 2.26.x as it is on 2.28.0 after upgrade.

Running ghost log in -V mode shows no additional information, Only other thing i see in the log is this which seems to happen sometimes. I am running on an AWS t2micro free tier:
NAME: HelperWarning
CODE: SLOW_GET_HELPER
MESSAGE: {{#get}} helper took 359ms to complete
level: normal

Thanks in advance for any suggestions.

The first warning shouldn’t be an issue for now, feel free to ignore it

The second warning (SLOW_GET_HELPER) suggests that your theme is using the get helper, and might be querying a lot of data - it took 359ms for the get query to finish. While not absolutely necessary, you might want to look at your theme and see where the get helper is used, and if you can make it more efficient.

2 Likes

Hey @vikaspotluri123
Thanks so much for the super fast response and clarifying the cookies message.
I will dig through the theme and see if i can figure it out :slight_smile:

Thanks!

1 Like

This is a funny one. In my logs I see Cookie ghost-members-ssr not found but everything works as expected.

Question: What does this message means?

logs

Many people has it in their logs:

  • How was Ghost installed and configured? v3.40.1, docker
  • What Node version, database, OS & browser are you using? node 14, sqlite, chrome
  • What errors or information do you see in the console? see above
  • What steps could someone else take to reproduce the issue you’re having?

I think it means Ghost was unable to find an active member because the cookie was not found. As far as I know, ghost-members-ssr is used to authenticate members.

@vikaspotluri123 thank for you reply :slight_smile: I guess my real question is: Do you know how to fix this warning ? Does it has something to do with ads/script blockers on browsers?

I don’t think it’s fixable. If you open the site incognito, I’m guessing you will see that it caused a warning to be printed. I think any anonymous user will trigger the warning.

ok thanks!