PUQ Mautic

Jellyfin WHMCS module

WHMCS module that automates Jellyfin media-server accounts. Sell Jellyfin access as a WHMCS product: each service maps to a Jellyfin user whose library access, playback and transcoding policy, Live TV, SyncPlay, session limits and lockout are driven by the product configuration. Clients manage their account from the WHMCS client area — view credentials, allowed libraries, active devices and sessions, drop devices and unblock the account. Supports PHP 7.4 / 8.1 / 8.2+.

Description

Jellyfin module WHMCS

Order now | Download | Community

Jellyfin WHMCS module

The Jellyfin WHMCS module turns your WHMCS into an automated platform for selling Jellyfin media-server accounts. Each WHMCS service is mapped to a 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.

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 Jellyfin user 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.

Changelog

Jellyfin module WHMCS

Order now | Download | Community

v3.0 — 2026-06-06

Added

Changed

Fixed


v2.1.1

v2.1 — 2025-10-03

v2.0.1 — 2024-12-19

v2.0 — 2024-09-24

v1.5.1 — 2024-08-13

v1.5 — 2023-07-12

v1.4 — 2023-12-21

v1.3 — 2023-12-18

v1.2 — 2023-11-17

v1.1 — 2023-11-09

v1.0 — 2023-11-03

Installation and Configuration Guide

Step-by-step instructions for installing and configuring the Jellyfin WHMCS module: WHMCS deployment, connecting your Jellyfin server, creating the product and configuring the access policy.

Installation and Configuration Guide

WHMCS Module Installation and Update

Jellyfin module WHMCS

Order now | Download | Community

Supported PHP & WHMCS versions

The module supports PHP 7.4, 8.1 and 8.2+ and WHMCS 8.x / 9.x, and is 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 your server's PHP version, not to the WHMCS version. PHP 8.2 and any newer PHP → always use php82. Requires ionCube Loader v13+ (v14/v15 supported).

Download

The module is distributed as a single ZIP archive. A separate build is published for each supported PHP major version — pick the one that matches the PHP runtime used by your WHMCS installation.

All versions and historical builds are available in the index:

Direct "latest" downloads

PHP 8.2

wget https://download.puqcloud.com/WHMCS/servers/PUQ_WHMCS-Jellyfin/php82/PUQ_WHMCS-Jellyfin-latest.zip

PHP 8.1

wget https://download.puqcloud.com/WHMCS/servers/PUQ_WHMCS-Jellyfin/php81/PUQ_WHMCS-Jellyfin-latest.zip

PHP 7.4

wget https://download.puqcloud.com/WHMCS/servers/PUQ_WHMCS-Jellyfin/php74/PUQ_WHMCS-Jellyfin-latest.zip

Not sure which PHP version your WHMCS runs on? Check Utilities > System > PHP Info in the WHMCS admin area.

Installation

Step 1: Unzip the Archive

On your WHMCS server (or locally, before uploading):

unzip PUQ_WHMCS-Jellyfin-latest.zip

The archive extracts into a PUQ_WHMCS-Jellyfin/ directory containing the server module folder puqJellyfin.

Step 2: Copy the Server Module

Copy and replace puqJellyfin from the extracted PUQ_WHMCS-Jellyfin/ directory to your WHMCS installation:

PUQ_WHMCS-Jellyfin/puqJellyfin  →  WHMCS_WEB_DIR/modules/servers/puqJellyfin/

Example:

cp -r PUQ_WHMCS-Jellyfin/puqJellyfin /var/www/html/whmcs/modules/servers/

Step 3: ionCube Loader

Ensure ionCube Loader v13+ is installed and enabled for the PHP version your WHMCS runs on. The module source is encoded with ionCube.

Step 4: License key

Each product that uses this module requires a valid license key in the License key field of the product's Module Settings tab. Invalid or missing licenses are listed on the WHMCS admin homepage.

License key on the Module Settings tab

The module self-creates its database tables (puq_license, puq_module_versions) on first load — there is no SQL to run manually.

File Structure

After installation, the module files should be located at:

whmcs/
├── modules/
│   └── servers/
│       └── puqJellyfin/            # Server module
│           ├── puqJellyfin.php
│           ├── hooks.php
│           ├── whmcs.json
│           ├── lib/
│           ├── lang/
│           └── templates/

Update Procedure

To update the module to a newer version:

  1. Back up your WHMCS installation (and the existing modules/servers/puqJellyfin/ directory).
  2. Download the latest build that matches your server's PHP version (see Download above).
  3. Upload and overwrite the files in modules/servers/puqJellyfin/.
  4. Open any WHMCS admin page once — the migration runner brings the schema up to date automatically.

Upgrading from v2.x: no reconfiguration is required. The module reads existing product settings from the legacy configoption3configoption8 slots until you save the product once through the new form, at which point they are consolidated into configoption24.

Tip: always back up your WHMCS installation before performing an update.

Installation and Configuration Guide

Add a Jellyfin server in WHMCS

Jellyfin module WHMCS

Order now | Download | Community

Configure the connection to your Jellyfin server under Setup → Products/Services → Servers → Add New Server.

Add a Jellyfin server in WHMCS

Field Value
Hostname / IP Address The Jellyfin server hostname or IP.
Secure (SSL) Enable if Jellyfin is served over HTTPS.
Port Jellyfin port (default 8096, or 443 when SSL is enabled).
Username A Jellyfin administrator username.
Password That administrator's password.
Access Hash A Jellyfin API key (Dashboard → API Keys).
Type / Module PUQ Jellyfin.

In the Server Details section select Module → PUQ Jellyfin and fill in the Username, Password and Access Hash (API key), tick Secure for SSL and set the Port.

Server Details — PUQ Jellyfin module + Test Connection

Use Test Connection to confirm WHMCS can reach Jellyfin and authenticate. The module authenticates with the username/password + API key to obtain an access token, then calls System/Info to verify connectivity.

Assign the server (or a server group containing it) to your Jellyfin product under the product's Module Settings.

Installation and Configuration Guide

Product configuration

Jellyfin module WHMCS

Order now | Download | Community

Create a product of type PUQ Jellyfin (Setup → Products/Services), assign the Jellyfin server on the Module Settings tab, then configure the access policy in the injected configuration panel.

Product configuration

Libraries Configuration

The dynamic list requires the product to be saved with a Server Group that contains a reachable Jellyfin server. Until then the panel shows a hint to select and save a Server Group.

Libraries — dynamic checkbox picker

User Configuration

User Configuration

Allow Playback

Toggle media playback, audio transcoding, video transcoding and video conversion without re-encoding.

Allow Playback

Feature Access

Live TV access, Live TV recording management, and force transcoding of remote media sources.

Feature Access

Links

Client Area

Client Area settings

Settings are stored as a single JSON document in configoption24. After saving, Create/Change actions push the resulting policy to Jellyfin.

Client Area

What the customer sees and can do on the Jellyfin service page in the WHMCS client area.

Client Area

Client area overview

Jellyfin module WHMCS

Order now | Download | Community

The client opens their Jellyfin service from clientarea.php → My Services → (service) → Information. The page loads its data over AJAX and renders a set of cards.

Client area overview

Actions

Account

Info

Libraries & Devices

All actions use AJAX and report the result with a toast notification — the page never reloads.

Admin Area

Managing a Jellyfin service from the WHMCS admin area.

Admin Area

Service page

Jellyfin module WHMCS

Order now | Download | Community

On the WHMCS admin service page (Clients → (client) → Products/Services) the module adds an information tab and the standard module command buttons.

Admin service page

Module commands

Custom buttons

Information tab

All lifecycle actions are license-gated: if the license cache is stale and the license server is unreachable, the action is refused with the license error.