Skip to content

Apply a profile to sites

A profile is applied to a site once. Later edits to the profile reach the site only when you apply it again. The Profiles & limits page shows how many sites are on each profile, and the profile’s edit page can re-apply it to all of them in one background job.

  • Create the profile first. See Create and edit a profile.
  • To apply to an existing site you need manage access to that site and the Manage hosting profiles capability. Owners and Administrators have both.
  • Know what gets overwritten. Applying sets these on the site:
    • PHP memory, execution time, workers, recycle count and database connections.
    • The disk quota and the over-quota action, when the profile has a disk limit. A profile with both disk fields blank leaves the site’s existing quota alone and sets only the over-quota action.
    • The backup cadence and the retention values.
    • The expiry policy (grace days and warning days). The site’s expiry date is not changed.
    • The price snapshot and billing clock, unless a price was set on the site itself.
    • The Slack webhook and alert emails, copied onto the site’s uptime monitor.
    • The WordPress plugins and themes listed in the profile.
  1. Open Hostings, click Add a website and fill in the form.
  2. Open Advanced options. Under Profile, choose a card. None keeps the defaults.
  3. Finish the form. Picking a profile pre-selects the PHP version and database engine from its New-site defaults, and the profile is applied after the site is created. The profile’s WordPress plugins and themes are installed with a progress card.
  1. Open Hostings, click the site, then the Settings & limits tab.
  2. Scroll to Apply a profile. Pick the Profile. The box under the list reads “Will set:” and names the values, ending with “Overwrites the current values.”
  3. Click Apply profile and confirm Apply profile. The page opens the job’s progress card on the WordPress tab.

The card Price on the same tab shows set here when the price belongs to the site. A site-level price is kept when you apply a profile, and the confirmation says “The price set on this hosting stays.”

To copy only the Slack webhook and emails, click Import only Slack + e-mails instead. It leaves limits, expiry and price alone. The button is disabled for a profile that has neither.

Re-apply an edited profile to every site on it

Section titled “Re-apply an edited profile to every site on it”
  1. Open Profiles & limits, then the profile.
  2. Under Websites on this profile, read the list. The note says “Saving below changes the profile only.” The sites keep what they were applied with.
  3. Click Re-apply to N websites and confirm Re-apply to N. The page opens the job at Background jobs.
  4. Watch the job. It works through the sites one by one and names each domain.
  1. Open Profiles & limits, then the profile, then the Delete group at the bottom.
  2. Click Delete profile and confirm Delete profile. The list shows “Profile deleted”.

Only the profile is removed. Sites on it keep the limits, expiry policy and price they were applied with. If the profile had a Slack webhook, the per-profile Slack channel for billing and expiry notices is lost and those notices fall back to email. This cannot be undone. Duplicate the profile first if you may need it again.

  • On the site’s Settings & limits tab, the Apply a profile card shows the profile name as a badge, and Disk quota shows from <profile>.
  • A finished job reads “Profile fully applied.” for one site, or “Re-applied to all N site(s).” for a re-apply.
  • On the profile’s list row, the Sites column counts the sites on it.
  • “Re-applied to X/Y; N failed:” followed by a list: the job names each domain that failed with the reason. Fix the cause and run Re-apply again. It only repeats the apply.
  • “node(s) … could not be reached — their sites were not re-applied; run this again once they are back”: a worker did not answer. Check it on Nodes, then re-apply.
  • “No hostings are on this profile yet — nothing to re-apply.”: no site has had this profile applied.
  • “No reachable hostings are on this profile — node(s) … could not be asked.”: every node with sites on this profile was unreachable.
  • A site shows a quota error after applying: the kernel rejected the disk cap. See Set a disk quota.
  • A plugin or theme did not install: the WordPress install is best effort and does not undo the limits. Read the site’s WordPress tab and the job log.