Quick troubleshooting view
The web service is temporarily unavailable or refuses new requests.
- Maintenance
- Server Saturation
- PHP/application unavailable
- Check if the problem is global
- Control resources
- Read the logs.
- Restoring the workers/services.
- Correct Overload.
- Reduce application burden or increase resources if necessary.
Contextual technician plan
Test several pages and users.
“Check if the problem is global” should produce an observation that clearly confirms or rules out “Maintenance”.
If the observation is normal, lower “Maintenance” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Maintenance” first. Related action: Restoring the workers/services.
CPU, RAM, workers, connections.
“Control resources” should produce an observation that clearly confirms or rules out “Server Saturation”.
If the observation is normal, lower “Server Saturation” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Server Saturation” first. Related action: Correct Overload.
Look for overload or maintenance messages.
“Read the logs.” should produce an observation that clearly confirms or rules out “PHP/application unavailable”.
If the observation is normal, lower “PHP/application unavailable” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “PHP/application unavailable” first. Related action: Reduce application burden or increase resources if necessary.
A quota or platform incident can produce 503.
“Check the host.” should produce an observation that clearly confirms or rules out “Connection limit”.
If the observation is normal, lower “Connection limit” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Connection limit” first.
Repeat the same validation test after the correction and confirm the original symptom is gone. Validate stability before closing the incident.
Before changing configuration, record the current value and a way back.
Escalate if 503 is from a limit or incident of the host.
The web service is temporarily unavailable or refuses new requests.
Causes probables
- Maintenance
- Server Saturation
- PHP/application unavailable
- Connection limit
- Protection against abuse
Diagnostic étape par étape
- 1
Check if the problem is global
Test several pages and users.
- 2
Control resources
CPU, RAM, workers, connections.
- 3
Read the logs.
Look for overload or maintenance messages.
- 4
Check the host.
A quota or platform incident can produce 503.
Solutions possibles
- Restoring the workers/services.
- Correct Overload.
- Reduce application burden or increase resources if necessary.
Escalate if 503 is from a limit or incident of the host.