A browser timeout can have several causes. DNS may be wrong, a certificate may have expired, or the application may be waiting on its database. Separating those cases early saves time and avoids unnecessary restarts.
Describe the precise symptom
Unresponsive can mean DNS failure, a TLS error, connection timeout or slow application response. These happen at different layers. Record the URL, time, status and whether other users or websites are affected.
Test externally as well as locally. A locally working site can be unreachable through public DNS or network policy. A healthy provider status page says little about one application’s database connection.
Follow the request path
Check the resolved destination and certificate, then the web service, PHP runtime and application dependencies. A working static page does not prove a dynamic checkout works. Separate web-server errors from application errors.
Workers can queue behind slow database queries or external APIs. Increasing their limit may create more simultaneous waits and a busier dependency. Inspect representative requests while protecting private log data.
Look for overlapping workloads
Backups, imports, mail scanning and traffic bursts can overlap. Disk exhaustion can stop writes even with free RAM. An account hitting a configured boundary can fail differently from a host exhausting physical resources.
Compare account evidence with host observations from the same incident window. A measurement taken after a restart may no longer describe the failure. Preserve enough context to separate cause and symptom.
Recover narrowly and test again
Use the smallest supported action justified by evidence, with rollback for configuration changes. Broad restarts can disrupt healthy customers. Some failures need application work or provider help rather than a panel action.
Repeat the original user action afterward and watch for recurrence. EzePanel’s recovery workflow records eligibility and verification for supported actions; it does not promise to repair every application or external dependency.
Put the guide in context
Controlled RecoveryServer HealthSources and review notes
Checked 17 October 2026. Vendor terms, supported versions and prices can change. Follow the official source before a purchase or server change.
