troubleshoot-website

Troubleshoot a website

One website and one symptom in; a named cause, the evidence for it, and a fix out. Stay read-only until the cause is stated and the user agrees to the fix.

Calling the operations

• Read the inputSchema that search returns before the first call of each operation. If a name below is rejected as unknown, search for what the step does (e.g. "ssl status").
• Batch reads with multi-execute and pass values between steps with $steps.<i>.<path>, e.g. "$steps.0.data.0.username". A batch stops at its first failure.
• The Hostinger Connector runs each product as its own MCP server (hosting, wordpress, agency-hosting, domains, dns), so a batch can only chain operations from one server. When search cannot find an operation, that product group is switched off in the Connector — ask the user to enable it.

1. Find the website

Run both lookups, and keep the result for every later call:

• hosting_websites_list with domain — Shared and Cloud plans. The filter is a substring match, so take the entry whose domain is exactly the one asked about. Keep username, order_id and website_type; every hosting_* and wordpress_* call is keyed on username + domain.
• agency-hosting_websites_list-plan with domain — Agency Plan. Keep details.uid (the website_uid of every agency-hosting_* call), details.type, details.ipv4 and details.domains.

Neither finds it: the domain is not a website on this account — say so and show where it points (step 2).

2. Look at it from outside

Run these alongside step 1:

curl -sS -o /dev/null -w "%{http_code} ttfb=%{time_starttransfer}s %{redirect_url}\n" https://DOMAIN/
curl -sSI https://DOMAIN/
dig +short NS DOMAIN; dig +short A DOMAIN; dig +short CAA DOMAIN

• Hostinger responses carry platform: hostinger and panel: hpanel. Without them, or with DNS pointing elsewhere, traffic is not reaching this hosting — hand over to the connect-domain skill.
• Certificate or TLS errors → SSL.
• 5xx, a blank page or an error page → By website type.
• 200 with old content → cache: hosting_cache_clear-website (also purges the Hostinger CDN; pass directory for WordPress in a subfolder), plus wordpress_litespeed-cache_purge-lite-speed for WordPress; Agency: agency-hosting_cache_clear-website.
• Slow first byte → Slow site. Behind the Hostinger CDN, x-hcdn-upstream-rt is the origin's own response time in seconds; a small value there means the server is not the bottleneck.