Apply this guide to your situation
This answer covers “Estimate resource needs before choosing a plan”. Read it with the summary and confirm that the symptom and service match what you are experiencing. Available options can vary by plan and account setup.
- Before changing anything, note what you expected, what happened and roughly when. Check whether the issue affects one page or the whole service.
- Save the full error message and note recent changes. Hide passwords, access codes, personal data and keys before sharing screenshots or logs.
- If a step requires administrator access, restarting services or editing server files, stop if you do not administer that server. Send support the service name, error and checks you have already made.
Likely-cause and resolution matrix
Follow a branch only when evidence supports it. A symptom may have more than one cause; do not change layers by guesswork.
01Professional English translation pending.
Why it can happen: Professional English translation pending.
Professional English translation pending.Step-by-step resolution:
Professional English translation pending.
02Professional English translation pending.
Why it can happen: Professional English translation pending.
Professional English translation pending.Step-by-step resolution:
Professional English translation pending.
03Professional English translation pending.
Why it can happen: Professional English translation pending.
Professional English translation pending.Step-by-step resolution:
Professional English translation pending.
04Professional English translation pending.
Why it can happen: Professional English translation pending.
Professional English translation pending.Step-by-step resolution:
Professional English translation pending.
05Professional English translation pending.
Why it can happen: Professional English translation pending.
Professional English translation pending.Step-by-step resolution:
Professional English translation pending.
Prerequisites
- Current hosting metrics, backup and database sizes, email volume and expected growth.
Important warnings
- Features, prices, limits, coverage and tools depend on the current offer and provider. Confirm them for the specific service before subscribing.
Step-by-step walkthrough
1. Define the context
2. Check the scope
3. Compare the options
4. Record the decision
Troubleshooting & Solutions
The service reaches memory, process, disk or inode limits after migration or increased activity.
Root cause: Capacity was selected without measuring peaks or counting small files, email, staging or local backups.
Resolution: Identify the specific resource and its time series, remove only disposable data after backup, and compare an upgrade with workload optimisation.
Rollback and recovery plan
Before accepting an offer or migrating, keep the terms you reviewed and details of the current service. If you have already subscribed, do not cancel or change the source service until you confirm exit, refund and continuity options with the providers involved.
Related runbooks in this category:
Was this technical guide helpful?
Facing a production outage?
Hosting Anayil system administrators can directly intervene on your server infrastructure.