In the third week of October, the people who keep the world's web servers quietly turned their attention to two serious flaws in PHP, the language beneath a large share of the internet, and a great many musicians found themselves within reach of the repair. The story is less about code than about how much of an artist's life now rests on infrastructure they never see. A band website or merch store may depend on a server maintained by someone else, just as a modern studio depends on licence servers, drivers and cloud libraries that can change without warning. Mixdown Magazine uses this moment t
Licence Servers, Updates and the Cloud: How Musicians Can Stay in Control of Their Studio
A mate who set it up a few years ago and hasn't logged in since.
Mark
Why is a magazine for musicians writing about PHP?
Mimi
Because the band site, the merch store and the label page are often WordPress, and WordPress runs on PHP. Two critical flaws were patched on 21 October, so those sites need the update.
Mark
Can't they just update WordPress?
Mimi
Not for this. The fix goes on the server, so it's down to the host or whoever manages it.
Luke
Worth noting the piece doesn't say any musician's site has been attacked. It reports the flaws and patches, and frames this as housekeeping.
Mark
And the studio examples? Are they connected to PHP?
Mimi
Only by theme. Licence servers, OS updates and cloud platforms are all places where something outside your control can interrupt your work.
Luke
The Google licence outage in 2019 and the Myspace loss are cited as examples. The Myspace figure of 50 million songs is described as an estimate, so I'd hold it loosely.
Mark
What's the one habit that covers most of it?
Mimi
Print your stems, and back up in two places, one offline. Then a plugin or platform disappearing doesn't take the session with it.
Luke
And the unknown is the website. The article says the honest answer for many artists is a mate who set it up and hasn't logged in since. Nobody can tell you from outside whether your server is patched; you have to ask.
O Pulso
- Two critical PHP flaws were patched on 21 October, and administrators across the web are racing to apply the fix.
- WordPress sites look safe from the dashboard, yet the real repair happens on the server, which many musicians never touch.
- Band sites, merch stores and label pages sit in the blast radius, since PHP underpins roughly 70 per cent of identifiable websites.
- The immediate route forward is simple: confirm with the host that PHP is patched, update plugins and themes, and back up the site.
- Beyond the web, studios face their own quiet risks as licences, drivers and cloud presets change faster than artists can track.
In the third week of October, the people who keep the world's web servers quietly turned their attention to two serious flaws in PHP, the language beneath a large share of the internet, and a great many musicians found themselves within reach of the repair. The story is less about code than about how much of an artist's life now rests on infrastructure they never see. A band website or merch store may depend on a server maintained by someone else, just as a modern studio depends on licence servers, drivers and cloud libraries that can change without warning. Mixdown Magazine uses this moment to remind its readers that the old studio could be understood by opening its box, while the new one must be understood by knowing who holds the keys.
Two critical flaws in PHP were patched on 21 October, and web administrators spent the week applying the fixes. PHP powers roughly 70 per cent of websites whose server language can be identified, and every WordPress site runs on it. That puts band websites, merch stores, label pages and music retailers squarely in the frame.
The crucial detail is where the fix lives. The update goes onto the server itself, not through WordPress. A musician who keeps plugins current in the dashboard may still be exposed if the server beneath runs an unpatched PHP.
Mixdown uses the moment to look at the wider dependencies of the modern studio. Twenty years ago a studio was largely physical, and if it was switched on it worked. Today plugins phone home to licence servers, interfaces need drivers that keep pace with each operating system, and synths lean on editor apps and cloud presets. Usually this runs smoothly, but precedents are instructive. A 2019 Google network disruption briefly locked some users out of their cloud-licensed plugins, and Apple's removal of 32-bit support left older software unable to open. Myspace, meanwhile, lost an estimated 50 million songs in a server migration, a reminder that a platform is not an archive.
The advice is practical rather than alarmed. Bounce important sessions to audio, keep offline installers and licence files, hold off on system updates mid-project, and keep masters in at least two places, one offline. Know who hosts your website, and consider a managed platform if the answer is nobody.
For this week, the task is short. Ask your host to confirm PHP is patched, update plugins and themes, and make a fresh backup. Mixdown estimates it takes about ten minutes for most people.
Patches for two critical flaws in PHP were released on 21 October, and web administrators around the world spent the week applying them. PHP is the programming language behind roughly 70 per cent of websites whose server language can be identified, and every WordPress site runs on it. That puts a lot of musicians in the frame: band websites, merch stores, label pages and music retailers.
The detail that matters most for them is where the fix goes. The update is applied to the server itself, not through WordPress. A musician who keeps their plugins and themes current in the WordPress dashboard has still not done the job if the server underneath is running an unpatched version of PHP.
Mixdown Magazine uses the moment to look at a wider set of dependencies in the modern studio. Twenty years ago a studio was mostly physical: a desk, a tape machine or an early DAW, a rack of outboard, instruments in the room. If it was plugged in and switched on, it worked, and a tech could open it up if it broke. Today's setups are more capable and more affordable, but plugins check in with licence servers, DAWs need authorising, and interfaces need drivers that keep pace with each new operating system. Synths, modellers and pedals increasingly rely on editor apps, firmware updates and cloud preset libraries. Finished music ends up on platforms the artist doesn't own.
The magazine is clear that this mostly works smoothly. But there are precedents for it going wrong. In June 2019, network congestion at Google disrupted some cloud-based plugin licences for a few hours, and some users couldn't open sessions until service returned. They had done nothing wrong. Licensing models also shift between subscriptions and perpetual licences, so it helps to know what kind of licence each plugin uses and what happens if you stop paying. Steinberg, for instance, has been moving Cubase and Nuendo users off the USB-eLicenser dongle to a system with no hardware key, which matters to anyone opening an old project in an old version.
Operating systems bring their own friction. When Apple released macOS Catalina in 2019, it ended support for 32-bit software, and older plugins and apps that hadn't been updated stopped opening. A year later, Apple's move to its own silicon chips had producers checking compatibility charts before upgrading while developers worked through updates. Even a perfectly healthy audio interface may need new drivers for the latest macOS or Windows, which is why plenty of engineers keep a spare computer for older gear. Editor apps for modellers and synths work best when kept current, so the magazine suggests backing up firmware and editor installers.
The same applies to finished work. In 2019, Myspace revealed that a server migration had lost music uploaded between 2003 and 2015, an estimated 50 million songs, and many bands of that era had used it as their main online home. The lesson drawn is to keep your own copies and give fans more than one place to find you. Closer to home, anyone running a WordPress band site, or streaming their own catalogue or sample library from a self-hosted media server, should know who looks after the server. Many popular open-source options, such as Koel, are also built on PHP. For many artists, the article notes, the honest answer is a mate who set it up years ago and hasn't logged in since.
The advice is practical rather than alarmed. Print stems by bouncing each track of important sessions to audio with effects, so they open in any DAW regardless of installed plugins. Keep offline installers and licence files, and know which plugins need the internet to authorise. Hold off on operating system updates until a project is finished, and check DAW, plugin and driver compatibility first. Keep masters and session files in at least two places, one of them offline. Find out who hosts and updates your website, and consider a managed platform if the answer is nobody. And make sure a live rig works with wifi off, with backup presets stored on the device.
For this week, the to-do list is short. If your band site, merch store or label page runs on WordPress, ask your host or whoever manages the server to confirm PHP has been updated to a patched version. Update plugins and themes, and make sure you have a recent backup of the site. Mixdown puts it at about ten minutes for most people.
Citações Notáveis
If your band site, merch store or label page runs on WordPress, check with your host that PHP has been updated to a patched version.— Mixdown Magazine
Quer a matéria completa?
Leia o original em Mixdown Magazine ↗
Technology