Divi fix
Divi Update Failed? Fixing the Username and API Key Error
Divi updates do not come from WordPress.org. They come from Elegant Themes, and only after the site proves it belongs to an active account with a username and an API key. When either is wrong, expired or someone else's, the update fails and the notice tells you less than it should.
- Dashboard > Updates > Themes
- Divi: a new version is available
- Updating Theme Divi (1/1)
- An error occurred while updating Divi: Download failed.
- You must first authenticate your Elegant Themes subscription
- Theme Options > Updates: API key not accepted
What you are seeing
- The Updates screen says to authenticate your Elegant Themes subscription
- Divi shows an update available and the update fails every time
- No Divi update has been offered in a long while, though plugins update fine
- The Username and API Key fields hold details you do not recognize
- A notice says the Elegant Themes subscription has expired
Why it happens on Divi
Most common first.
- 1
The key belongs to an account that has moved on
Agencies and freelancers often enter their own Elegant Themes credentials on client sites. When they revoke the key, close the account or stop renewing, your site loses its right to updates without anything visibly changing. The key is usually in the inbox of someone who no longer answers email.
- 2
The username field holds the wrong thing
The Updates tab wants the Elegant Themes account username, exactly as the members area shows it, alongside the key. An email address typed out of habit, a misspelling or a key pasted with a stray space at the end can each fail the check, and the notice does not say which half was wrong.
- 3
A yearly membership that lapsed
Elegant Themes sells yearly and lifetime memberships. When a yearly one expires, the installed copy of Divi keeps running and stops receiving updates. The API key itself has not changed; the account behind it no longer qualifies.
- 4
The server cannot reach Elegant Themes
The check is an outbound request from your server. A firewall rule, a security plugin that blocks external requests or a host with restricted outbound connections can stop it, and correct credentials then fail the same way wrong ones do.
- 5
Authentication passes and the install still fails
Sometimes the key is fine and the update dies later: the download times out, the disk is full or file permissions refuse the new files. That is a WordPress update failure wearing a Divi label, and it gets fixed at the host.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Back up first, and resist the Update button
Fixing the key may unlock an update that spans years of releases. Take a full backup of files and database before you authenticate anything, and plan to run the update on a staging copy before the live site sees it.
- 2
Read what is saved in the Updates tab
Go to Divi, Theme Options, Updates and note the username. If you do not recognize it, the site is running on someone else's account, and the real fix is getting credentials that belong to your business.
- 3
Generate a fresh key in the members area
Sign in at elegantthemes.com, open the account area and find the page for your username and API keys. Create a new key and label it with the site's name. Copy the username from that same page so it matches character for character.
- 4
Save both and ask WordPress to check again
Paste the username and key into the Updates tab and save. Then open Dashboard, Updates and use Check Again. The authentication notice should clear and the Divi update should be listed normally.
- 5
If the notice stays, test the connection
Open Divi, Support Center and review the system status for warnings. On staging, pause any security plugin's firewall and retry. If that changes nothing, ask the host whether outbound requests to elegantthemes.com are being blocked.
- 6
Update on staging, or upload the zip by hand
Run the update on the staging copy and check the pages that earn money. If the automatic update still fails, download the current Divi zip from the members area and upload it under Appearance, Themes, Add New, Upload Theme; WordPress will offer to replace the installed version. Should the new release misbehave, the Updates tab includes a Version Rollback.
Keep it from coming back
- Hold the Elegant Themes membership in an account your business owns, and issue outside developers a labeled key you can revoke
- Use one key per site so retiring one never breaks another
- Put the renewal date of a yearly membership on a calendar someone reads
- Update Divi every month or two on staging, so no single update spans years
The permanent fix
A faster Next.js build, with a CMS made for your business
A site whose updates depend on a membership, a key and the goodwill of a former agency has three points of failure before any code runs. A Next.js build has no theme to license and no update channel to authenticate; the code sits in a repository you own, the custom CMS is yours too, and both change when you decide. If the key problem surfaced because nobody has maintained the site in years, weigh the catch-up work against starting clean.
| On Divi today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your Divi site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
In the Elegant Themes members area, under your account, on the page that lists your username and API keys. You can create several keys and label each one. In WordPress they go in Divi, Theme Options, Updates, and the same pair covers other Elegant Themes products installed on the site.
You can update by hand: download the latest zip from the members area and upload it through Appearance, Themes. That still takes an active membership to get the file. Copies of Divi from anywhere else are not worth the risk, because you cannot know what was added to them.
Not necessarily. Many developers run client sites on their own membership, which works until the relationship ends. What matters is control: either hold the membership yourself, or have a written understanding and a key issued just for your site.
It is safe to attempt on a staging copy with a backup behind it. The risks are custom code edited into the parent theme, which an update overwrites, and third-party extensions written for the old version. Look for a child theme first; our page on themes that break after an update covers the recovery.
Keep reading
- ServiceWebsite Hosting & Maintenance PlansThe watching after launch: managed hosting, tested updates, backups that restore, security and uptime monitoring, and small edits done within a day, month to month.
- ServiceFixing WordPress PluginsOne bad plugin can take your whole site down. We fix plugin conflicts, fatal errors, and security holes fast — and build custom plugins when the off-the-shelf ones fall short.