Why does a CDN failed to deploy on my domain?
When activating a Multi CDN for your domain, the system will attempt to set up the CDN with your domain. This process is done via API between Mlytics and the CDN providers. But when an error occurs from the CDNs end, the integration process might be put on hold until fixed.
This kind of error can be seen from the ‘Installed Power-Ups’ section and is signified by a ‘Failed’ status.
When this happens, Mlytics will automatically retry the setup process. And if you’re still seeing this after 24 hours, please contact us.
Below are 2 possible reasons for having a CDN error.
Some CDN providers put restrictions on domains that are installed on their platform
Though not many, some CDN providers limit their users from adding the same domain used via their service to be used in other portals or channels. When a domain already exists under these CDN providers, they might restrict Mlytics from integrating that domain to use their own CDN.
Cloudflare is one of the most common CDN that has this issue. As one of the widely used DNS providers on the market, there's a very good chance that you're already using Cloudflare as your main DNS provider or CDN provider.
To learn how to fix this, please check out this article.
Cloudflare CDN is available in Developer, Business, and Enterprise Plans.
Domain rejected by CDN providers
When installing any Chinese CDNs such as Alibaba Cloud or Wangsu to your Mlytics Multi CDN lineup, these CDN providers will automatically audit the added domain to verify its validity.
If the added domain is suspected to contain any illegal content, Chinese CDN providers will reject the domain, causing CDN installation failure on Mlytics.
The following categories are considered illegal to Chinese CDN providers based on government regulations:
- Private gaming server