Diagnosing website problems with error logs and account information

1. Begin by recording the affected URL, what you expected to happen, the exact message or status shown and the time with timezone.
2. Note whether the problem affects every page, one feature, all visitors or just your connection.
3. Also record recent changes such as an application update, a deployment, a PHP change or a DNS edit.

These details help narrow the investigation to a manageable set of causes.

A missing page, an access-denied response and an application failure can look similar to a visitor but have different explanations. Check that the domain reaches the intended website, then inspect the relevant error entries and account usage near the recorded time. If a form fails while the rest of the site works, focus on that request and its application logs rather than assuming that the entire hosting service is unavailable.

Make a backup before changing live files or configuration, apply one focused correction and repeat the affected action to confirm the result. A successful page refresh alone may not prove that an intermittent problem is resolved. Our Hosting AI Engineer can help interpret evidence and investigate supported account-level causes, and our team can review issues requiring further access. When sharing logs, include a useful excerpt rather than an entire private dataset, and remove passwords, access tokens and unrelated customer information. If a required log is unavailable in your account, tell us which symptom and time period need investigation.

Use an observation record like this when a form stops working. The values below describe an illustrative test, not a live Nabtech incident.

Affected action: Submit the contact form at /contact
Expected result: Confirmation and a message to the business mailbox
Observed result: The submission returns HTTP 500
Test time: 14:02 UTC, [date]
Other checks: Homepage and ordinary mailbox email work
Recent change: Application deployment earlier the same day
Relevant evidence: Error entry matching the form request and time

This narrows the starting point to the submitted request and its application code or configuration. It does not prove that the deployment caused the error. Inspect the matching log entry, make one justified correction with a recovery copy, then repeat the same form submission and verify actual message delivery.

1. Reproduce one failing action and record its URL and time with timezone.
2. Find the matching error or access entry and compare it with recent deployments, configuration changes and usage information.
3. Make a focused correction with a recovery copy, then repeat the same action and check for a fresh error.

Do not upload a full private log when a short redacted extract identifies the problem. A stale entry from yesterday can mislead an investigation into today's failure. If a log is unavailable, provide the exact symptom and time so we can locate the relevant server-side evidence.

• Activating free SSL and resolving HTTPS warnings
• Changing PHP versions, extensions and application limits
• Understanding CPU, RAM, storage, inodes and data transfer
• Accessing the new management tools as an existing hosting customer

• Nabtech Web Hosting