Old plugins are the most common way WordPress sites get hacked, and updates are the most common way they break. FlyNode's updates are built so you can do the first without the second.
Update from the Security tab
Open your app and go to the File Manager tab. Its menu has Plugins, Themes and File Manager. Each plugin and theme is listed with its version, state, author and description, and an Update button at its right when an update is waiting (Update all does them together). WordPress itself and the automatic-update switches are at the top of the Plugins page.
What every update does
- Backup. A copy of the database and of the files that are about to change is saved on the server.
- Maintenance page. Visitors see a maintenance page for a moment.
- Update. WordPress, the plugins and the themes you chose are updated.
- Health check. FlyNode loads your home page and the login page, checks that WordPress starts and that no fatal error is on the page.
- Automatic rollback. If the health check fails, everything is put back from the backup and you are told why. Nothing is left half-updated.
FlyNode keeps the three newest update backups of each site on the server, so a bad update can be undone quickly. The site is also backed up every night: see Back Up and Restore WordPress.
Automatic nightly updates
Switch on Update automatically every night and FlyNode runs the same process around 3:30 am server time. You choose whether it covers WordPress core, plugins and themes. Core only gets security and maintenance releases, never a new major version. You receive a message with the result: updated, rolled back because the site stopped working, or could not run.
Update on staging first
For a site that matters, update the staging copy first, look at it, and then use Push to Production (or update the live site). The Security tab on a staging copy shows the Updates card for exactly this.
The automatic rollback protects you from an update that breaks the site's start-up. It cannot know that a button on page 12 moved. Look at the pages that matter after a big update.
Still stuck?
Open a support ticket from your dashboard and include the container name.