Fatal Error in Gdn_Session.start(); [UPDATE 2.8.3 to 3.1]

Fatal Error in Gdn_Session.start();

Call to a member function getSession() on null

The error occurred on or near: /var/www/vanilla/library/core/class.session.php

438:         // Now retrieve user information.
439:         if ($this->UserID > 0) {
440:             // Instantiate a UserModel to get session info
441:             $this->User = $userModel->getSession($this->UserID);
443:             $userSignedIn = false;
444:             if ($this->User) {
445:                 $this->permissions->setPermissions($this->User->Permissions);

Need Help?

If you are a user of this website, you can report this message to a website administrator.

If you are an administrator of this website, you can get help at the Vanilla Community Forums.

Additional information for support personnel:

  • Application: Vanilla
  • Application Version: 2.8.3
  • PHP Version: 7.3.8-1+0~20190807.43+debian9~1.gbp7731bf
  • Operating System: Linux
  • Server Software: nginx/1.10.3
  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
  • Request Uri: /utility/update

Hello everyone

I'm here to ask you for help.

I wanted to update vanilla from version 2.8.3 to version 3.1 and since when I want to access https://vanilla.example.com/utility/update, the above message appears.

I work with ngnix.

 I would like to point out that I took the opportunity to update php7.2 to php7.3

Do you have any advice for me, please.

Thank you.


  • R_JR_J Cheerleader & Troubleshooter Munich Moderator

    A little late, sorry...

    I do not see an obvious explanation or even a possible explanation for the above error message. So in order of simplicity I would do the following (and retry /utility/update after each step):

    • Delete everything inside the /cache folder
    • Re-upload all files, followed by deleting the contents of the cache folder
    • Disable all plugins and switch to default theme

    Since this is the first time I saw someone mentioning the error above, I would assume that this problem can be eliminated with one of the steps above

Sign In or Register to comment.