When a configuration update fails

A failed configuration update means a change you made — adding a domain, adjusting a capability, or connecting a service — couldn't be applied to your server. Your server keeps running on its previous working configuration. Nothing was taken down and nothing is broken. The new change just wasn't applied yet.

What to do

1. Open the operation and read what it reports. The failed update records where it stopped. That usually tells you whether the problem is with the change itself or something about the server's current state.
2. Check that your server is reachable. Go to your server's page and confirm it shows as online. A server that can't be reached can't receive a configuration update.
3. Review any pending changes. Your server's configuration tab shows what changes are waiting to be applied. If you made several changes recently, consider whether any of them might conflict — for example, a domain that isn't set up in DNS yet, or a service that isn't ready to be connected.
4. Try applying the update again. From your server page, trigger another configuration update. Most failures are transient — a brief connectivity issue or the server being busy during the attempt. A second attempt often succeeds.

If updates keep failing after retrying and your server is otherwise healthy, reach out and we'll look at the operation details with you.