Did F/W Ver. 5.31.108 break Twonky Server?

Many users have recently reported issues after updating their WD My Cloud or My Cloud Home devices to firmware version 5.31.108, particularly regarding the Twonky Server — the built-in media server responsible for streaming content like music, photos, and videos to smart TVs, media players, and other DLNA-compatible devices. While firmware updates are meant to improve system performance, enhance security, and fix bugs, this particular release appears to have introduced complications that effectively broke or disrupted Twonky functionality for many users.

Before the update, Twonky served as a reliable solution for media streaming, automatically indexing files and making them accessible over the local network. However, after installing firmware version 5.31.108, users began to notice that Twonky no longer appeared on their network, failed to index media files, or displayed “Server not found” messages on connected devices. Some even found that the Twonky interface, typically accessible through a browser on port 9000, became unreachable.

The root of the issue appears to be changes in the firmware’s media service framework. WD has been gradually shifting its focus away from third-party and legacy media servers like Twonky in favor of its own cloud-based solutions. Firmware version 5.31.108 seems to have either disabled Twonky by default or limited its access to indexed shares and permissions. For advanced users who rely on Twonky for local streaming — especially in offline environments or home media setups — this has been a major inconvenience.

Some users have tried various troubleshooting steps to restore Twonky functionality. Restarting the device, rebuilding the media database, or toggling the media server settings sometimes brings temporary relief. In certain cases, reverting the firmware to an earlier version (like 5.25 or 5.26) has restored normal operation — though WD generally discourages firmware downgrades and provides no official method to do so. Others have attempted manual reinstallation or enabling Twonky through SSH commands, but these steps require technical expertise and may void warranty support.

If your Twonky Server stopped working after updating to firmware 5.31.108, the best initial step is to check the device’s web dashboard under Settings → Media → DLNA Media Server. If Twonky is disabled, re-enable it and rescan your media shares. You can also try clearing and rebuilding the media database to refresh the indexing process. If the problem persists, you may want to explore alternative media streaming options such as Plex, Emby, or Jellyfin, which can be manually installed and offer broader compatibility.

For now, it’s unclear if WD plans to issue a patch or update to fix Twonky support in future firmware versions. Users who rely heavily on local media streaming should consider delaying firmware updates until compatibility issues are confirmed resolved. In the meantime, maintaining backups of your media library and exploring third-party DLNA servers may help bridge the gap until full functionality returns or WD provides an official solution.

0コメント