troubleshoot-website
Diagnose and fix a website on Hostinger web hosting (Shared, Cloud or Agency plans) that is down, slow, erroring, insecure or failing to build. Checks the site from outside, reads builds, runtime logs, WordPress health, SSL, cache and PHP settings through the Hostinger MCP, names the cause with evidence, and applies the fix once the user agrees. Triggers: my site is down, site not loading, 500 / 502 / 503 error, white screen, error establishing a database connection, site is slow, SSL or certificate warning, not secure, changes not showing, Node.js build failed, app keeps crashing.
How do I install this agent skill?
npx skills add https://github.com/hostinger/api-mcp-server --skill troubleshoot-websiteIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill is designed for troubleshooting Hostinger-hosted websites using official MCP tools. While it possesses significant capabilities to modify hosting environments and read server logs, it includes a human-in-the-loop constraint requiring user approval before any changes are made. The primary security consideration is the processing of potentially untrusted data from website logs and configuration files.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
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
inputSchemathatsearchreturns before the first call of each operation. If a name below is rejected as unknown,searchfor what the step does (e.g. "ssl status"). - Batch reads with
multi-executeand 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. Whensearchcannot 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_listwithdomain— Shared and Cloud plans. The filter is a substring match, so take the entry whosedomainis exactly the one asked about. Keepusername,order_idandwebsite_type; everyhosting_*andwordpress_*call is keyed onusername+domain.agency-hosting_websites_list-planwithdomain— Agency Plan. Keepdetails.uid(thewebsite_uidof everyagency-hosting_*call),details.type,details.ipv4anddetails.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: hostingerandpanel: hpanel. Without them, or with DNS pointing elsewhere, traffic is not reaching this hosting — hand over to theconnect-domainskill. - Certificate or TLS errors → SSL.
5xx, a blank page or an error page → By website type.200with old content → cache:hosting_cache_clear(also purges the Hostinger CDN; passdirectoryfor WordPress in a subfolder), pluswordpress_litespeed-cache_purge-lite-speedfor WordPress; Agency:agency-hosting_cache_clear-website.- Slow first byte → Slow site. Behind the Hostinger CDN,
x-hcdn-upstream-rtis 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_get-deployment (the latest build with its log, failure analysis and stored settings), 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:hosting_get-deploymentalready holds theanalysis(fetched once per build — the API re-runs it on every call and allows 5 a minute). A wrongly detected framework, output directory or missingentry_fileis the usual cause: compare the returnedbuildSettingswith the project and deploy again with correctedappType,outputDirectory,buildScriptorentryFile; a Git deploy stores them, so pushes build correctly too. A site deployed on the hosted server from uploaded files has nohosting_deployto repeat: rebuild throughhosting_nodejs_start-buildwith the corrected values and store them withhosting_nodejs_update-build-settings. - Build
completedbut the app errors: read the runtime logs; entries older thanlast_deployed_atbelong to the previous deploy. A variable the code reads but the key list lacks is fixed with thedeploy-to-hostingskill's environment step.Access denied for user '…'@'::1'means the app connects tolocalhost—DB_HOSTmust be127.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_errornames 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 withwordpress_plugins_activateany that were not the cause. - Maintenance page stuck:
wordpress_maintenance_togglewithenabled: false. - "Error establishing a database connection":
hosting_databases_listwithdomain; corrupted tables are fixed byhosting_databases_repair(runs in the background).wp-config.phpcannot be read through the API because files with secrets are refused — for credential checks hand the userhosting_databases_phpmyadmin-link. - Memory or upload-size errors → PHP.
Static or PHP (other)
403or404at/:hosting_files_list-website-and-directorieswithmax_depth: 1.index.htmlorindex.phpmust sit at the document root; finding it one folder down means the archive was packed a level too deep — redeploy it flat with thedeploy-to-hostingskill.- Read
.htaccessor other config withhosting_files_website-content. - PHP errors → PHP.
PHP
hosting_php_get returns every extension and option (around 25 KB), so call it only for PHP problems. hosting_php_update changes the version, extensions and options in one call. Switching the version resets the extensions and options to their defaults, so pass the ones to keep in the same call. Option values are silently capped at the plan maximum (max in hosting_php_get), so read the applied value back. Agency: agency-hosting_php_list-options-for-website, then agency-hosting_php_replace-website-options — a full replace, so send every custom option that should stay.
Agency Plan sites
agency-hosting_websites_get shows state and quotas, agency-hosting_websites_list-processes shows failed jobs (SSL setup, backups), and agency-hosting_wordpress_settings shows core version, LiteSpeed, object cache and maintenance mode. When wordpress_installations_list does not return the site, plugins are managed from wp-admin.
SSL
Shared and Cloud, ssl in hosting_websites_get-settings:
not_installedorfailed(last_errorsays why): the domain must resolve to Hostinger, and any CAA record must allowletsencrypt.org, beforehosting_ssl_installcan succeed. Pollhosting_websites_get-settingsuntilssl.statusisactiveorfailed.installingorwaiting_for_retry: wait — another install request returns 422.- Free
*.hostingersite.comsubdomains use a platform certificate; installing returns 422 by design. - Browser still warns while the certificate is
active: turn on the redirect withhosting_websites_update-settings(httpsRedirect: true) whenis_https_redirect_enabledis false, otherwise the page loadshttp://assets (mixed content) that the app has to change.
Agency, agency-hosting_ssl_website-status for each domain: every domain allows three certificate setups per seven days and one request a minute. Check agency-hosting_websites_list-processes before agency-hosting_ssl_install-website or agency-hosting_ssl_reinstall-website, and never retry in a loop.
Slow site
- WordPress:
wordpress_litespeed-cache_show-lite-speed-statusandwordpress_object-cache_show-memcached-status. Turning on Memcached withwordpress_object-cache_toggle-memcachedis the usual quick win. - Other sites: server caching may be off or development mode left on.
hosting_websites_get-settingsshows both incache(is_enabled,is_cacheless_mode_enabled); fix them withhosting_websites_update-settings(cache: true,cachelessMode: false). Development mode takes a few minutes to turn off. - PHP 7.x runs markedly slower than 8.x; propose a supported 8.x version from
hosting_php_getwhen the app allows it. - Agency:
agency-hosting_metrics_list-order-resource-usagewithtime_frame_hours: 24shows CPU, memory and processes per website against the plan quota. - Shared and Cloud have no CPU or memory metrics in the API. When the evidence points at resource limits, send the user to hPanel's resource usage page.
Apply the fix
State the cause, the evidence and the single change proposed, and make it only after the user agrees. Then re-run the step 2 check, polling any queued job first, to show the symptom is gone. When the fix needs something the API cannot do, say so and name the hPanel page.
Not available through the API
- Website backups and restores — hPanel's Backups page.
- CPU, memory and process usage for Shared and Cloud plans.
- PHP error and access logs.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/hostinger/api-mcp-server/troubleshoot-website">View troubleshoot-website on skillZs</a>