The CRM-NG sign-in relay answered, but refused the request or returned a result your site could not read.

This article is for sites using One-Click Setup where the relay replies with a refusal: sign-in relay refused or sign-in result could not be read.

What this error means

Every request your site sends to the relay is signed with your site's own key, and every result the relay sends back is sealed so that only your site can open it. The relay refuses a request when the signature does not match, when the sign-in took longer than ten minutes, when the return address is not on your site, or when it is receiving too many requests from one site. Your site rejects a result it cannot open. Nothing is stored in either case.

Common causes

• The sign-in took too long. The round trip from Sign in to coming back must finish within ten minutes.
• The site address changed between starting the sign-in and coming back, for example moving from http to https or from www to the bare domain.
• Two sites share one database copy (a staging copy of production), so both present the same key and the relay sees a mismatch.
• Too many attempts in a short time from the same site.

How to fix it

1. Click Sign in again and finish the sign-in without leaving the browser tab.
2. Make sure Settings → General → WordPress Address and Site Address are the address you actually use, with the same scheme and host.
3. On a copied site, click Disconnect and sign in again on that copy so it gets its own connection.
4. If the relay reports too many attempts, wait a few minutes before trying again.