Topic on Project:Support desk

Hi!

I'm seting up a private wiki (nly logged in users can read and edit it) on a free hosting (it's installed as an app ). After a few days, as I'm editing a page, whe I save I get this message:

"Sorry! We could not process your edit due to a loss of session data.

You might have been logged out. Please verify that you're still logged in and try again. If it still does not work, try logging out and logging back in, and check that your browser allows cookies from this site."

When I try to log out. I get this message: "Log out failed due to session error. Please try again."

Then I try to log in in a different browser and I get this message:

"There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Please resubmit the form."

It has happened twice, after another clean install. I can't start it over again!

I've tried setting $wgSessionCacheType = CACHE_DB; in LocalSettings.php, but the problem is NOT solved.

System information:

MediaWiki: version 1.31.5

PHP: version 7.1.33 (cgi-fcgi)

MySQL: 5.7.20-log

I've installed only one extra extension: SimpleTooltip.

Can you help me?? Thanks!

How long you are editing? Do you have enabled cookies on your computer?

Idk, I've been editing all day until it has happened again.Cookies are enabled. The other users also can't login from their pcs.

Do you know how much RAM you have to run the wiki? Could that be related?

I couldn't find the specs, it's a free hosting. Do you think it can be a RAM problem?

RAM would probably only be related if using CACHE_ACCEL, and the shm_size was kept small to save ram. If you are using CACHE_DB its probably unrelated to RAM [If your site is super slow to load, that is probably related to RAM]

Its hard to know what is causing this, although its definitely weird if you're using CACHE_DB. I would guess that the cheap host is maybe doing something to be cheap... but i don't really know.

Free hosts have limited database size. You may have reached the limit of your quota and doesn't let you insert more data on the database

Thanks, Ciencia Al Poder. You were rigth, the problem was related to the database quota.