You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Use the following methods to find and save the Fastly service ID and API token for your environment:
To view your Fastly credentials:
* IaaS-mounted shared directory—On Pro projects, use SSH to connect to your server and get the Fastly credentials from the /mnt/shared/fastly_tokens.txt file.
When Cloud Pro customers submit tickets relating to Fastly not working correctly, their issue often arises simply due to them having configured the wrong Fastly credentials in the affected environment.
Possible solutions:
Add an alert for Pro customers under that segment that they should make sure to check the /mnt/shared/fastly_tokens.txt file in the correct environment for the Fastly credentials when configuring Fastly because Staging and Production have separate credentials/Service IDs.
The text was updated successfully, but these errors were encountered:
General issue
Description:
https://devdocs.magento.com/cloud/cdn/configure-fastly.html#cloud-fastly-creds
When Cloud Pro customers submit tickets relating to Fastly not working correctly, their issue often arises simply due to them having configured the wrong Fastly credentials in the affected environment.
Possible solutions:
Add an alert for Pro customers under that segment that they should make sure to check the /mnt/shared/fastly_tokens.txt file in the correct environment for the Fastly credentials when configuring Fastly because Staging and Production have separate credentials/Service IDs.
The text was updated successfully, but these errors were encountered: