Error when validating the Fastly credentials
- Topics:
- Configuration
CREATED FOR:
- Developer
This article explains how to resolve Token expired errors encountered when validating Fastly credentials.
The steps outlined in this article also apply if you need to rotate (cycle) your Fastly API Token for security reasons. In these cases, you should submit an Adobe Commerce Support ticket to request a new Fastly API token.
Issue
- You get an error when validating the Fastly credentials.
- You suspect that your Fastly token may have been compromised, for example, if it was inadvertently shared in a support ticket or posted on a public forum.
Affected products and versions
- Adobe Commerce (all deployment methods): All versions
- Extension or technology (Fastly, New Relic, etc.) version Fastly
Solution
-
Make sure you have the correct Fastly service ID and API token and try to validate again. For detailed instruction, refer to Test the Fastly credentials in our developer documentation.
-
If the verification of the credentials fails, run the following curl command to confirm the status of the service:
curl -H "Fastly-Key: <API key>" https://api.fastly.com/service/<service ID>/version/active -
If the above command returns an error similar to:
{"msg":"Token $TOKEN expired at 2021-09-28T02:03:37Z"}, submit a support ticket to request a new API token. After receiving your new token, update the configuration in your environment.To learn how to submit a support ticket, refer to Adobe Commerce Help Center User Guide > SUPPORT TICKETS in our support knowledge base.
NOTENever share any passwords or valid/active API tokens directly in the ticket as we will have to revoke the current token and generate a new one for security reasons.Adobe Commerce Support has access to the tokens, so you shouldn’t need to include this information in the ticket. -
If the command doesn’t return the error, make sure that you are running the newest version of the Fastly extension. If you are on an older version prior to 1.2.203, you must first click on Save Config before you can test the credentials.