How to troubleshoot upload files error

This wizard step is entirely automated. It can fail due to Jenkins downtime or custom origin domains for example.

Verify files creation

Every tenant who has started the CDN activation process has its own CDN configuration file in its repository. If the file doesn't exist, you can create it.

Customize this boilerplate:

{
  "tenantName": "example.com",
  "desktopBackendAdd": "origin.example.com",
  "desktopBackendPort: 443 or 80 if HTTP,
  "force_ssl": 1 or 0 if HTTP
}

And create a pull request in the site repository with it. The cdn.json codeowners can then review it and help for the next steps.

TIP

Set correctly the values of desktopBackendPort and force_ssl depending on whether the origin domain is accessible with HTTPS or not.

Handle already existing domain

Every domain can be registered only once in Fastly. Marfeel checks for the tenant's domain in Fastly before attempting the registration: if it is already present, Marfeel can't go forward.

The tenant must remove their domain from Fastly to continue the activation steps of MarfeelCDN. If the tenant doesn't know why their domain already exists in Fastly, the Systems team can help.

Marfeel will send a different TXT record instead of the one provided by the CDN Wizard to add to the DNS. This new record will pass on the domain ownership to Marfeel, allowing us to handle the domain in Fastly.

Subdomain management

If Marfeel only handles a subdomain of the tenant, create the cdn.json file manually in the tenant site repository.

Example of a minimum file for a subdomain:

{
  "tenantName": "sub.example.com",
  "desktopBackendAdd": "origin.sub.example.com",
  "desktopBackendPort": 443 # or 80 if HTTP,
  "force_ssl": 1 # or 0 if HTTP,
  "fastly_domains": [
    {
      "name": "sub.example.com"
    }
  ]
}

Create a pull request with the new file: the cdn.json codeowners can help with the next steps.