406. The session identifier is missing

  • Getting this on ALL my providers…. NOPE my hosting php variables etc have NOT changed since it WAS working… ALL i did was upgrade to latest verion of the plugin and now i get this error – I AM flipping out as this is a CRITICAL issue with our users…..

    WSL worked like a DREAM for me before on a few sites, now i am stuffed

    406. The session identifier is missing

    YES i also tried this fix

    If you did encounter The session identifier is missing or You cannot access this page directly, it means that PHP sessions are not working as expected by WSL on your web server. This issue may have many reasons:

    File permissions.

    If you see an error Warning: session_start() [function.session-start]: open(/tmp/sess_… on the top of this page or in the Error log file, then most likely because of a file permissions problem. The solution is to make a trouble ticket with your web host.

    For advanced users: alternatively, you can create the sessions folder in your root directory, then add session_save_path(‘/path/to/writable/folder’) at the top of the following files:

    wp-config.php
    wp-content/plugins/wordpress-social-login/wp-social-login.php
    wp-content/plugins/wordpress-social-login/hybridauth/index.php

    https://www.ads-software.com/plugins/wordpress-social-login/

Viewing 4 replies - 1 through 4 (of 4 total)

  • And where do I find my root directory?

    Penner, they are talking about the site root for the wordpress site. Clearly, the writable folder could be anywhere but in most cases, it is better to keep it all within a known part of the system and not allow your web user to write to places all over your server. Depending on your setup, you might also want to create it one level below your site root so it cannot be accessed by any web sites.

    Maddog, this error occurs for one of two reasons. The first is is the PHP session data cannot be written for any reason, then when WSL looks for the configuration, it doesn’t find it and falls over. This will be related to all kinds of things like how your session is setup to work and whether the client has cookies enabled etc. You might have to write a test page to at least see if PHP sessions work on the server at all with your browser.

    The second reason is related and occurs if, for example, you have finished the authentication in a different browser than you started in. I have seen this where the user has reset their OAuth2 account during sign-in and returns to the browser from somewhere else. The session is different per-browser, so the plugin fails again and gives the same error. I don’t know if this is a design decision or whether it is just a big related to the way the plugin is designed.

    I don’t know of any recent changes that caused this but it might be worth having a look at the recent github history to see if anything jumps out!

    Maddog, this answer: https://www.ads-software.com/support/topic/406-the-session-identifier-is-missing-1 talks about the php directories being moved with a server upgrade so maybe that’s the issue or are you saying that you have tried to write sessions somewhere else and it still fails?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘406. The session identifier is missing’ is closed to new replies.