Troubleshooting

Save & verify fails

Save & verify mints a real Cloudpath JWT against the Core surface, so a failure is always in the credentials chain. In order of likelihood:

1. Wrong password or username. Re-enter the password — it is write-only, so you can’t inspect what’s stored. A bad login surfaces as login_failed.
2. FQDN not a bare hostname. The field must be a hostname only — no https:// and no path. https://host/foo is rejected with “fqdn must be a bare hostname (no scheme, no path)”.
3. Self-signed or untrusted TLS certificate. See below.
4. Host unreachable. A DNS or network failure to the FQDN surfaces as invalid_host.

My Cloudpath uses a self-signed certificate

It won’t work. Cloudflare Workers reject self-signed certificates on outbound HTTPS and offer no skip-verify option. Install a publicly trusted certificate on your Cloudpath server. Cloud-hosted Cloudpath at *.cloudpath.net already presents a valid certificate. See Security model.

The connector won’t authorize

• Redirect loop or “too many redirects” — a cookie problem during the Google sign-in hop. Use a normal (non-private) window, allow cookies for cp-mcp.lanpulse.com, remove the connector, and add it again.
• “Not authenticated” on every call — the token was revoked, or the connector was added before sign-in completed. Remove and re-add it.
• Connector connects, but calls fail on credentials — MCP auth is fine and Cloudpath auth isn’t. Go re-run Save & verify in the dashboard.

See Connecting to Claude.

”No Cloudpath credentials configured”

The connector is authorized but you haven’t saved Cloudpath credentials for this account — or you deleted them. Sign in to the dashboard and save your FQDN, username, and password. This surfaces to Claude as the no_credentials error.

Property-surface calls fail

• missing_property_portal — a property.call was made without propertyMgmtPortalGuid. Every Property Management call must be scoped to a portal GUID. See The three API surfaces.

A call returns ok: false but nothing threw

That’s by design — call never throws on an HTTP error; it returns a result with ok: false and the status. Inspect status and body to see what Cloudpath said. See Calling conventions.

A portal logo or favicon uploaded but appears blank

The multipart text field name was wrong or missing. Cloudpath reads the filename field for logos and iconFilename for favicons — the wrong name returns 200 OK but silently clears the stored image. See Generating portal images.

Still stuck?

Contact support with the FQDN, the surface you were calling, and the status and body from the failing call.