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.

3. By website type

website_type (Shared/Cloud) or details.type (Agency) picks the branch. builder and horizons sites are not managed by these operations — send the user to hPanel.

Node.js (nodejs)

Batch hosting_nodejs_list-builds (per_page: 3), hosting_nodejs_runtime-logs (period: "1h", levels: ["ERROR", "WARN"]) and hosting_nodejs_list-environment-variables (keys only; values always come back masked).

• Latest build failed: call hosting_nodejs_analyse-failed-build once for that build — every call re-runs the analysis and the limit is 5 a minute. When it returns nulls, read hosting_nodejs_build-logs. A wrongly detected framework, output directory or missing entry_file is the usual cause: compare hosting_nodejs_build-settings with the project, rebuild with corrected values through hosting_nodejs_start-build, and store the same values with hosting_nodejs_update-build-settings so Git pushes build correctly too.
• Build completed but the app errors: read the runtime logs; entries older than last_deployed_at belong to the previous deploy. A variable the code reads but the key list lacks is fixed with the deploy-to-hosting skill's environment step. Access denied for user '…'@'::1' means the app connects to localhost — DB_HOST must be 127.0.0.1.
• Hung process: hosting_nodejs_restart-application (restarts without rebuilding).

WordPress (wordpress)

wordpress_installations_list with username and domain gives the install id — the software parameter of every wordpress_* call. Batch wordpress_installations_check-if-are-valid (software_ids: [id], force: true), wordpress_plugins_list-installed and wordpress_maintenance_show-status.

• Invalid install: validation_error names the problem.
• Broken after a plugin or theme change: deactivate suspects one at a time with wordpress_plugins_deactivate (queued — allow a few seconds), re-run the step 2 check after each, and reactivate with wordpress_plugins_activate any that were not the cause.
• Maintenance page stuck: wordpress_maintenance_toggle with enabled: false.
• "Error establishing a database connection": hosting_databases_list with domain; corrupted tables are fixed by hosting_databases_repair (runs in the background). wp-config.php cannot be read through the API because files with secrets are refused — for credential checks hand the user hosting_databases_phpmyadmin-link.
• Memory or upload-size errors → PHP.