Session Timeout

All websites that need to know who you are, store your details in a session token on the server, with a reference to this in a Session Cookie stored on your client computer. These session tokens can’t live forever and the Moodle sessions are set to last four hours.  When you log into Moodle, a session token and cookie is created and you are automatically logged into Pydio using the same access details, so you don’t have to login again. However, if you close browser windows without logging out, or perhaps start an e-learning session and leave the tab open for an extended period, your Moodle session token, or that of Pydio may have timed out or become invalid. This means when you follow a link to a document in Pydio, You may be presented with the Pydio login screen as shown here.


It is better if you don’t try to log in here as the system will lock you out after three bad attempts and a bug in the software is corrupting the synchronised password, so this may well happen. Instead of logging in here, close the Pydio tab/window (and any others you have open). Log out of Moodle if it thinks you are still logged in. When you log back into Moodle it will start a new session token and you will be able to follow the links to Pydio files with being prompted to login again. In some cases, invalid token cookies can be cached on your machine. If this happens log out of Moodle properly and close all browser windows. When you restart your browser and log back into Moodle you should be OK. If not you may need to re-boot your computer and/or clear your browser cache. If there are still problems, you will need to raise a Help Ticket.




Login problems can have a number of different causes. These are usually either forgotten or incorrect username and/or password or you simply don’t have a user account.

When you login to the e-learning site, three different session cookies are set, these session cookies allow the system to remember who you are as you move around the site. If you are connected for a long time, or perhaps don't logout properly, these sessions can get out sync and one of the sessions may have expired. If this happens, you may get the screen shown below or you could get an "invalid token" message.