Blog Sections Open
When session-keepalive.php Starts Overloading Shared Hosting
How to investigate high CPU usage tied to session-keepalive.php and what to change before a host disables your Evolution CMS account.
If a host reports heavy CPU use from session-keepalive.php, the problem is usually not a public-site attack. More often it is a manager-side session script being called too often, across too many tabs, or on a hosting setup with slow session storage.
What to Check
- How many managers keep the backend open all day in multiple browser tabs.
- Whether session storage lives on slow disk or a crowded network filesystem.
- Whether third-party manager scripts call keepalive more often than expected.
- Whether PHP session garbage collection or locking is misconfigured on the host.
Reduce unnecessary manager tabs, test with keepalive frequency lowered, and ask the host where PHP session files are stored.
Planning Automatic Cloud Backups for Evolution CMS with Cron
A practical backup strategy for shared-host Evolution CMS projects: make a local dump, run it on cron, and push the archive to cloud storage safely.
Fixing WebLogin Sessions That Work Only After Clearing Cache
Why WebLogin or WebLoginPE may appear to work only after a cache clear, and what to check in session handling, cached resources, and login flow.