For whom: Panel Administrator, SRE. Required rights: CDN management and Flow.
Diagnostic procedure
1
Provider account
Open the account card and click Check the keys. Expected status is
valid. permission_limited will list the missing roles, invalid means the keys are not authenticated.2
Operation.
Open the CDN section and find the last operation of the desired resource. Check its step and error code.
3
Resource and block
Open Flow → Holst and select the CDN block. Verify the domain, account and current status.
4
Origin
Make sure that the input node has a domain and responds over HTTPS with a valid certificate – without this provisioning will not begin.
5
DNS zone
Check that the zone covering the node domain exists with the provider and the account has access to it (
dns.editor).Model scenarios
The operation is stuck on the DNS step
Symptoms: the state ofDNS_PENDING or PROPAGATING does not change for a long time; codes DNS_RECORD_CONFLICT, DNS_PROPAGATION_TIMEOUT.
- Verify that the account has access to the node domain DNS zone – the
CDN_DOMAIN_SETUP_FAILEDcode means that no zones are visible or none cover the domain. - With
DNS_RECORD_CONFLICT, find records in the zone that conflict with the delivery domain (cdn.node.example.com) or with the challenge certificate entries, and remove them. - With
DNS_PROPAGATION_TIMEOUT, check the delegation of the zone and repeat the application of Flow later - re-application is safe (surgeries are idempotent).
Operation stuck at TLS step
Symptoms: conditionCERTIFICATE_PENDING; codes CERTIFICATE_VALIDATION_PENDING, CERTIFICATE_ISSUE_FAILED.
- Check the role of
certificate-manager.editorin the service account. - Certificate issuance is confirmed via DNS – if the challenge record is not published, see the DNS script above.
CERTIFICATE_VALIDATION_PENDINGmeans that the certificate is not issued out of the waiting window: repeat the application - the operation will continue from the current place.
DNS Recording Conflict
CodeDNS_RECORD_CONFLICT. There is already a record in the zone that prevents the delivery domain CNAME or challenge record from being published. Delete or rename the conflicting entry in the DNS provider console and repeat the application. Don’t create entries for cdn.<домен-ноды> manually, this is controlled by the panel.
Account invalid / expired / permission_limited
invalid- keys do not pass authentication: check that the full authorized key (JSON in its entirety) and the correct Folder ID are inserted; replace the keys through account editing - the panel will recheck them automatically.expired- The validity of credentials has expired: release new keys from the provider and update your account.permission_limited- lack of roles: the panel lists the missing ones (for Yandex Cloud -cdn.editor,certificate-manager.editor,dns.editor). Give the roles to the service account and click Check the keys. For VK Cloud, Selectel and Beget, this status is expected: the provider is not yet qualified for automation.
Rollback_Partial: What to do with your hands
The rollback restores the DNS from the images, removes the ISP’s created artifacts (CDN resource, origin group, certificate) and releases the delivery domain. If part of the steps fails, the rollback response lists the unfinished items, and the operation is marked as requiring attention.- Read the list of unfinished items in the kickback response/operation status.
- In the console provider manually remove the remaining artifacts: CDN-resource, origin-group, certificate.
- In the DNS zone, check the delivery domain records and challenge records – bring them to the “pre-operation” state.
- After manual cleaning, the reuse of Flow will begin the provisioning again from a clean state.
Qualification of the provider is not passed
CodeNEEDS_QUALIFICATION, block status blocked.
- Candidate Provider (VK Cloud, Selectel, Beget) or Timeweb: automatic provisioning is not yet available for them - use Yandex Cloud for automation or manual mode (configure in the provider’s console yourself).
- Functional tests failed (e.g.
CACHE_BYPASS_UNPROVEN): eliminate the cause and re-apply Flow - the samples will be performed again, and if successful, the resource will go toreadywithout re-creating.
Flow usage drops due to CDN
Fail-closed: the configuration is not applied until the CDN is ready. See the error code in the status of the CDN block and operation; frequent causes.ORIGIN_TLS_FAILED (There is no valid HTTPS on the node) CDN_AUTOMATION_NOT_AVAILABLE (no account ready), CDN_BLOCK_ENTRY_NODE_REQUIRED (the block is not connected to one node) Check also the graph diagram: Routing.
When to call for support
UNKNOWN_MUTATION_RESULT– Domain lease status is unsynchronized and requires reconciliation; do not try to repair by re-creating blocks.ROLLBACK_PARTIAL, which cannot be closed by manual cleaning.- Repetitive
PROVIDER_SCHEMA_MISMATCHorPROVIDER_OPERATION_TIMEOUTwhen the service provider is running. - Any situation where the operation is “hung” in an intermediate state and does not respond to either reuse or rollback.
Verification
The problem is solved when the operation reached
READY, the CDN block in Flow shows ready with the delivery domain, and the account status is valid.Rollback
If you can’t restore the food supply:- ready-made CDN uninstall by deleting the CDN block from Flow with subsequent application - direct rollback of the
READYoperation is prohibited (HTTP 409); - Resources and operations .
