CDN.com.tr Help

Apply Changes and watch Operations

Use Apply Changes and Operations to understand when saved origin, hostname, DNS, SSL, cache, or platform changes are actually deployed to traffic.

Back to Help Center Back to section

Getting started

Apply Changes and watch Operations

Use Apply Changes and Operations to understand when saved origin, hostname, DNS, SSL, cache, or platform changes are actually deployed to traffic.

Which guide does the Apply result point to?

Return to the guide for the area named by the operation result.

Origin/Host header

Check existing website settings

Wrong backend responses usually relate to origin Host header, DNS target, or path settings.

Pull CDN All delivery methods
Open existing site guide
Wrong choice

Re-evaluate source and delivery method

If the issue is a wrong source type or delivery model, return to the decision guide.

Pull / Push / Hosting Default / CNAME / Full DNS
Open choice guide

Panel path

  1. Management Panel
  2. CDN Accounts
  3. Related settings screen
  4. Apply Changes
  5. Activity > Operations
  6. Public verification

Prerequisites

  • The setting is saved.
  • The account is active and required package is assigned.
  • CDN method type and delivery transfer type are complete.
  • Manual server deploys or DB changes are not the customer flow.

Decision model

When is Apply Changes needed?

Traffic-affecting settings may need deploy after they are saved.

  • Origin or Host header changed.
  • Delivery hostname, DNS, SSL, or cache/security setting changed.
  • Platform source or public host binding changed.

What does Operations tell you?

Background work must be visible through customer-safe status and messages.

  • Success: proceed to public verification.
  • Failed: inspect the redacted error message.
  • Running/queued: wait or share operation ID with support.

Step-by-step guide

1

Find the account with pending changes

CDN Accounts or the related product screen exposes Apply Changes when deploy is required.

  • Confirm the right account is selected.
  • Inactive or incomplete method/delivery accounts may hide apply.
  • Note which setting was changed.

Expected result: Apply Changes appears only as a customer action for completed accounts that need deploy.

cdnctl equivalent 
cdnctl accounts describe --account "$ACCOUNT_UUID"
cdnctl accounts diff --account "$ACCOUNT_UUID"
2

Check that the setting is deploy-ready

Missing origin, Host header, hostname, DNS, or SSL data can make public results wrong even if deploy succeeds.

  • Check origin and Host header.
  • Check hostname and DNS state.
  • Check certificate readiness for HTTPS domains.

Expected result: Pre-apply gaps are visible in customer-facing surfaces.

cdnctl equivalent 
cdnctl pull origin describe --account "$ACCOUNT_UUID"
cdnctl hostnames list --account "$ACCOUNT_UUID"
cdnctl certificates list --account "$ACCOUNT_UUID"
3

Run Apply Changes

The button or warning queues the background deploy job.

  • Click Apply Changes.
  • Read the toast or success/warning response.
  • If DNS or certificate gaps are reported, return to the relevant guide.

Expected result: A deploy operation is created or a customer-safe warning is returned.

cdnctl equivalent 
cdnctl cdn accounts apply --account "$ACCOUNT_UUID"
4

Watch the result in Operations

Activity > Operations shows customer-visible deploy, transfer, certificate, and platform job status.

  • Open Operations.
  • Match the latest operation to account and time.
  • If it failed, use the message and supported retry or cancel action.

Expected result: Operation status tells whether public verification can start.

cdnctl equivalent 
cdnctl operations list --account "$ACCOUNT_UUID" --latest
cdnctl operations watch --account "$ACCOUNT_UUID" --operation <operation_id>
5

Verify public behavior

After deploy success, test the CDN endpoint or custom domain from a clean session.

  • Open the public URL in browser or curl.
  • If the wrong backend responds, return to Host header, DNS target, and origin path checks.
  • If stale content appears, use the purge guide.

Expected result: The public response matches the expected origin, storage, or platform output.

cdnctl equivalent 
curl -I https://www.example.com/
cdnctl cache purge --account "$ACCOUNT_UUID" --path /changed-path

Verification

  • Apply Changes button or warning appears on the correct account.
  • Operations shows the deploy result.
  • Failure messages remain customer-safe.
  • The public URL is verified after success.
  • Manual DB, hand-written nginx config, or SSH deploys are not part of the customer guide.

Use cases

A customer saved a setting but public traffic still behaves the old way, so they need to see whether the change was deployed and which operation result was produced.

Quick workflow

  1. Save the panel change.
  2. Run Apply Changes when the warning or button appears.
  3. Open Operations.
  4. Read success or failure.
  5. Verify with the public URL or related API.
  6. If it fails, use customer-facing retry or support paths.

Checks

  • Account method and delivery type must be complete before Apply Changes.
  • Operations ownership and redaction tests must remain in place.
  • Public verification happens after a successful operation.
  • Manual operations belong to internal runbooks, not user docs.