Hosting & Control Panels

A site that loads over HTTP but fails over HTTPS may have an invalid certificate, missing chain, wrong virtual host, forced redirect loop, or application-generated secure URL pointing to another hostname. What to check Check the certificate names and expiration, chain, domain assignment, HTTPS virtual host, redirect rules, and application base URL....

Small messages may send successfully while larger attachments fail because of message-size limits, mailbox quotas, client timeouts, provider restrictions, or encoding overhead. Several systems can impose different limits along the delivery path. What to investigate Capture the exact error and size, compare webmail and mail-client behavior, check...

Bandwidth use can increase because of larger media, repeated downloads, crawlers, hotlinked files, backup transfers, or a real rise in visitors. A hosting graph alone may not show which files or routes account for the traffic. What to check Review bandwidth reports with web access logs, response sizes, cache hit rates, referral patterns, and backup...

A production domain may unexpectedly redirect to a staging hostname after a migration, plugin update, or configuration restore. The redirect can come from application settings, rewrite rules, a control-panel redirect, or a cached response. What to check Trace each redirect response and identify which layer issued it. Check the application’s canonical...

A site may work normally except for one directory that returns 404 because of rewrite rules, directory naming, case sensitivity, document-root mapping, or a missing index. Linux paths are case-sensitive even when a developer’s local system is not. What to check Compare the requested path with actual file and directory names, inspect rewrite rules and...

Changing an account’s primary domain can affect document roots, redirects, certificates, email routing, and application base URLs. Some parts may update automatically while custom configuration remains tied to the previous name. What to check Check domain mappings, document roots, application URLs, redirects, certificate coverage, email records, and...

An administrator may see a site because of a logged-in session, cached content, a local hosts override, or privileged file access. Public visitors can still encounter a permission error, maintenance mode, or incorrect domain mapping. What to check Test in a clean unauthenticated session and compare response status, document root, access rules, cache,...

A website can stop working after enabling, disabling, or updating a PHP extension. The selected PHP version may be correct while a required module is absent, incompatible, or configured differently for web requests and command-line jobs. What to check Review the PHP error log, active handler and version, loaded modules, per-domain settings, and any...