Hi Victor, in order to diagnose the problem we would need more info:
- Do the resources load even if you see the disconnect message?
- How many users do you have accessing to the server simultaneously?
If you have many concurrent users, let’s say more than 30, bearing in mind the changes from the previous versions, there’s something you can try:
- In the kolibri config folder (https://kolibri.readthedocs.io/en/latest/manage/get_support.html#locate-kolibri-log-files), you must see a file called options.ini. Do a backup of it before changing it. Then, edit the file options.ini adding this:
[Server]
CHERRYPY_THREAD_POOL = 30
You must restart the kolibri server afterwards and test if your clients go better now.
If kolibri doesn’t start you likely broke the syntax of that file. In such case, restore the backup you previously did and attach it here so I can edit it for you.