Why a CDN failed to deploy to my domain?
When activating a 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 these CDN providers. But when an error occurs on any of these CDNs end, the integration process might be put on hold or even stuck until fixed.
When this happens, mlytics will automatically retry the setup process. If you’re still seeing this after 24 hours, please contact us.
The domain already exists under another CDN providers
Though not many, some CDN providers limit users from adding the same domain via their service via different portals or channels. When a domain already exists under these CDN providers, they might stop mlytics from integrating that domain to the 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. If this is the case, we won't be able to install Cloudflare for your domain because it already exists on Cloudflare, even if you're not using their CDN service.
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