Troubleshooting

Solutions to common Hostinger Connector issues: Node.js requirements, OAuth sign-in failures, missing tools in your AI assistant, and clean uninstall steps.

Solutions to the most common issues with Hostinger Connector.

Connection issues

The Connect button is disabled

The Connector requires Node.js 18 or later. Check the Node.js status in the Hostinger sidebar:

• "Node.js not detected" or "needs 18+" — click Install / Update in the red banner, or install Node.js 18+ manually from nodejs.org and restart your editor.

• "npx not found" — your Node.js installation is incomplete. Reinstall Node.js from the official installer, which includes npx.

OAuth sign-in fails or times out

• The sign-in must be completed within 3 minutes. Click 1-Click Connect and try again.

• If the browser doesn't open, look for the sign-in link printed in the editor's terminal and open it manually.

• On Windows, the sign-in runs in a terminal window named "Hostinger OAuth". Don't close it until sign-in completes — closing it cancels the login.

API token doesn't work

• Verify the token was copied fully, with no leading or trailing spaces.

• Tokens can be revoked or expire. Generate a new one in hPanel → API and reconnect.

Tools not appearing in your assistant

In VS Code (Copilot)

• Reload the window (Developer: Reload Window from the Command Palette).

• In Copilot Chat, click the Tools button and check that Hostinger tools are enabled.

In Cursor, Windsurf, Devin Desktop, or Antigravity

• These editors read the MCP configuration on startup. Fully quit and reopen the editor (not just the window).

• Verify the configuration file exists:

  • Cursor: ~/.cursor/mcp.json

  • Windsurf / Devin: ~/.codeium/windsurf/mcp_config.json

  • Antigravity: ~/.gemini/antigravity/mcp_config.json

• If the file is missing, disconnect and reconnect from the Hostinger sidebar.

A product's tools are missing

Check that the product group is enabled in the Hostinger sidebar. Ecommerce and VPS are disabled by default.

Errors when the assistant uses tools

Authentication or "unauthorized" errors

Your session may have expired or the token was revoked. Run Hostinger: Disconnect, then reconnect. If you use an API token, generate a fresh one in hPanel.

Tools fail immediately after connecting

The MCP servers are downloaded on first use via npx, which requires internet access. Check your network and any proxy or firewall that might block npm registry access.

Windows-specific notes

• OAuth sign-in opens a visible cmd.exe terminal — this is expected and required on Windows.

• If you see duplicate Hostinger entries in your assistant's tool list, update to the latest extension version, then disconnect and reconnect.

Uninstalling cleanly

1. Run Hostinger: Disconnect first. This removes credentials and cleans up MCP configuration in all managed editors and CLIs.

2. Then uninstall the extension from the Extensions panel.

Disconnect works even if Node.js has been removed from your system — the Connector deletes the stored credentials file directly.

Still stuck?

• Check the Hostinger API documentation for API-level details.

• Contact Hostinger support — available 24/7.

---

Last updated: July 21, 2026