PUQ Mautic

Description

Jellyfin Family module WHMCS

Order now | Download | Community

Jellyfin Family WHMCS module

The Jellyfin Family WHMCS module turns your WHMCS into an automated platform for selling Jellyfin media-server accounts with a family / sub-account system. Each WHMCS service is mapped to a main Jellyfin user whose access is fully driven by the product configuration: which libraries the user can see, what playback and transcoding is allowed, Live TV access, SyncPlay, streaming bitrate limit, maximum active sessions and failed-login lockout.

On top of the main account, the Family edition lets the client create a configurable number of media accounts — additional named Jellyfin sub-users (username-name), each with its own password, enabled state and restricted set of libraries. Clients add, edit and delete their media accounts, and drop their devices, directly from the client area — all over AJAX.

Account provisioning is automatic — on Create the module generates the username and password, creates the Jellyfin user and applies the configured policy. Suspend / Unsuspend / Change package / Terminate keep the main user and every media account in sync with the WHMCS service lifecycle. Clients manage everything from the WHMCS client area.

Client area overview


What's new in v3.0

Version 3.0 is a complete rewrite that brings the module up to the modern PUQ standard:


Main features


System requirements & compatibility

The module supports PHP 7.4, 8.1 and 8.2+, shipped as a separate ionCube build per PHP version. Download the build that matches the PHP version your WHMCS runs on.

WHMCS version PHP version Module build
WHMCS 8.x 7.4 php74
WHMCS 8.x 8.1 php81
WHMCS 8.x 8.2 php82
WHMCS 9.x 8.2 php82

Match the build to the server's PHP version, not to the WHMCS version. PHP 8.2 and any newer PHP → always use php82. Requires ionCube Loader v13+.

A reachable Jellyfin server, version 10.11.10 or newer, with an administrator account and API key is required. The module uses the modern Authorization: MediaBrowser scheme and the current user/password API routes, so it stays compatible with Jellyfin 10.12/10.13 where the legacy authorization headers are removed.


Revision #5
Created 6 May 2024 00:49:34 by Yuliia Noha
Updated 1 July 2026 19:03:31 by Ruslan