Troubleshooting

The sign-in code never arrives#

1. 1

   Check spam, then check the address you typed.

2. 2

   Ask whether your mail provider quarantines external senders.

   Corporate filters are the usual cause. Allow-listing signlos.com fixes it for everyone at your company at once.

3. 3

   Try the SMS option, or a passkey if you have registered one.

My custom domain shows a certificate error#

1. 1

   Confirm the CNAME resolves.

   dig +short feedback.yourcompany.com should return the SignlOS host, not your own web server.

2. 2

   Turn proxying off until issuance completes.

   Cloudflare's orange cloud in front of an unissued certificate is the single most common cause.

3. 3

   Give it a few minutes. Issuance is not instant.

The API returns 401#

• The header must be Authorization: Bearer sk_live_…. A bare key with no Bearer prefix is rejected.
• The key may be revoked or expired — check Settings → API keys.
• If the teammate who created the key has left the workspace, the key stopped working with them. Create a new one.

The API returns 403#

• INSUFFICIENT_SCOPES — the key is valid but lacks the scope for that route. Scopes cannot be edited; create a new key.
• API_KEY_SCOPE — the key was used outside /api/v1. Only the versioned API accepts keys.

Claude cannot see my workspace#

• The URL must be https://api.signlos.com/mcp — no trailing path.
• The key goes in an Authorization: Bearer … header, exactly as for REST.
• If tools are listed but every call is refused, the key is missing the scope those tools need — see Connect Claude to SignlOS.

Still stuck#

Email support@signlos.com with your workspace name and, for an API problem, the code field from the response body. That field tells us in one word what a paragraph of description usually cannot.