If you see “508 Resource Limit Is Reached” when opening a website, it usually means the hosting account temporarily reached its assigned resource limits.
This can be caused by:
- a traffic spike (real visitors or bots),
- heavy WordPress plugins/themes,
- scheduled tasks or backups running at the same time,
- inefficient database queries,
- or repeated failed requests (for example, a broken script or brute‑force attempts).
Step 1 — Confirm it’s not DNS/caching
- Try reloading after 2–5 minutes (limits often reset quickly).
- Test in a private/incognito window.
- If you use Cloudflare/CDN, purge cache (and temporarily pause “cache everything” rules).
Step 2 — Check what is generating load
In Plesk you can review your website’s activity and logs:
- Open Plesk from My.GARMTECH.
- Go to Websites & Domains → Logs and look for repeated requests or suspicious URLs.
- If you have statistics enabled, review traffic patterns (spikes, repeated hits).
Step 3 — Reduce load (recommended actions)
- Enable caching: on WordPress use LiteSpeed Cache (LSCache) and make sure the cache is configured correctly.
- Update WordPress core, plugins, and theme.
- Disable heavy plugins temporarily to identify the cause.
- Block bad bots (for example, by rate limiting or blocking abusive IPs).
- Optimize images and enable lazy loading.
- Optimize database (clean post revisions, transients, etc.).
Step 4 — Check scheduled tasks
- If backups/cron jobs are running too frequently, move them to off‑peak hours.
- For WordPress, consider replacing WP‑Cron with a real cron job.
When an upgrade may be needed
If the 508 error happens often during normal traffic, it usually means the site needs more resources. Consider upgrading the hosting plan or moving to a VPS for dedicated resources.
Tip: when creating a support request, include the exact time the error happened and the affected domain/URL. This helps match it with server logs.
