When Tiny Cloud detects a problem, it will show an editor notification containing information about the problem. This page describes the cause and solution for common Tiny Cloud error notifications.
|The wording of the notifications shown here may differ from the actual notifications from Tiny Cloud.|
"This domain is not registered with Tiny Cloud. Please see the quick start guide or create an account."
This notification is only shown when either:
apiKeyis not provided in the script tag.
no-api-keyis provided as the API key.
<script src="https://cdn.tiny.cloud/1/no-api-key/tinymce/6/tinymce.min.js" referrerpolicy="origin"></script>
src URL to include your (website or application developer’s) Tiny Cloud API Key. Your API key should replace the string
no-api-key. For example, if your API is
<script src="https://cdn.tiny.cloud/1/abcd1234/tinymce/6/tinymce.min.js" referrerpolicy="origin"></script>
To retrieve your API key, or to sign up for an API key, visit: Tiny Cloud.
"The API key you have entered is invalid. Please review your API key."
This notification is shown when the API key provided cannot be found on the Tiny Cloud server.
apiKey must be:
An exact length,
comprised of certain characters, and
created with a Tiny Cloud account on the Tiny Account page.
apiKey provided in the script tag:
Remove any leading or trailing spaces.
Any other characters that are not in your API key. If you are using variable substitution, ensure that the variable is substituting properly.
Matches the API key shown at https://www.tiny.cloud/my-account.
"This domain is not registered with Tiny Cloud. Please review your approved domains."
This notification is shown when the Referer of the page does not match the list of approved domains stored against your
apiKey. Tiny Cloud verifies the domain TinyMCE is loading from by checking the domain portion of the Referer header in the network request. You can view a list of your approved domains on your Tiny Account.
Sometimes the domain in the Referer header does not match with the URL in the browser’s address bar. To check the Referer header:
Open your browser’s Developer’s Tools.
Open the Network tab.
Find and select the request being made to load TinyMCE from Tiny Cloud with your API key.
Click on the Headers tab.
In the section called Request Headers there should be a field for Referer. This is the value that TinyMCE is checking against your approved domains. It must match one of your approved domains listed on your Tiny Account.
Referer is correct for the site, ensure that the domain is included in your list of approved domains on Tiny Account. If the
Referer is not what you are expecting, you may need to adjust your application’s Referer header settings.
"We’re unable to check your domain because the referer header is missing. Please read the Guide on how to ensure your referer header is present, so we can then customize your editor experience."
This notification is shown if the Referer header is absent for the network request when loading TinyMCE from Tiny Cloud. Tiny Cloud verifies the domain TinyMCE is loading from by checking the domain of the Referer header in the network request.
Referer headers are sometimes removed by browser settings or browser extensions. Tiny Cloud only needs the domain in the Referer header, so for improved performance and privacy Tiny recommends setting the
origin when requesting Tiny Cloud resources.
Identify which browser setting or extension is responsible for blocking the Referer being sent. A common extension is
Once you have identified the setting or extension, modify it to allow just the
Origin of the
Referer to be sent. Alternatively, disable the extension or setting for any pages using Tiny Cloud.
"The _ premium plugin is not enabled on your API key. Upgrade your account."
This notification is shown when your API key does not have access to the premium plugin being requested. This could be the result of a trial expiring, and your TinyMCE configuration attempting to load premium plugins you can no longer access.
You may also be seeing this notification if you are using the wrong API key. Ensure that you are using the API key that has the right entitlements.