The requirements for the OneSignal addon module are PHP 5.6 or higher, WHMCS 7.x, OpenSSL with TLS 1.1+ support, Ioncube Loader v10.1.x or higher, and cURL with TLS 1.1+ support. You also need a OneSignal account with an application created using the API key and App ID, configured for Chrome, Firefox, Edge and Safari. The module has only been tested in these scenarios by our developers and may or may not work under different conditions. Your system must already meet WHMCS base requirements.

These prerequisites ensure that the encoded module loads correctly, API calls are secure, and push notifications can be delivered to a wide range of user browsers. Failing to meet the TLS or loader requirements is a common cause of blank screens or connection errors when using the addon. The browser list defines the audience that can successfully subscribe to notifications through your WHMCS client area.

#Detailed System Requirements

You should have a clear understanding of using WHMCS including uploading, installing and configuring addons and gateways. Without this background, correctly integrating the OneSignal module with your client notifications and admin area may prove challenging. The module is not a simple drop-in; it requires accurate placement of files and precise entry of credentials.

PHP must be 5.6 or higher. This ensures access to updated security functions and compatibility with the module's code. WHMCS must be on the 7.x series; we do not support alpha, beta or release candidate builds due to their unstable nature. OpenSSL or any equivalent SSL library must include TLS 1.1 or higher support for secure outbound connections to external APIs. The Ioncube Loader v10.1.x or higher is required to execute the encoded PHP files at runtime. Older loaders produce fatal errors on include statements.

bash 
php -v

Check your PHP version and loaded modules with the command above or a phpinfo() page. Update the Ioncube Loader through your control panel or server package manager if the version is below 10.1. TLS 1.1+ prevents handshake failures when the module contacts OneSignal endpoints.

#PHP Extension Requirements

The cURL extension with TLS 1.1+ support is essential. It handles all interactions with the OneSignal API endpoints for subscription management, notification creation, and status tracking. Confirm support by inspecting the SSL backend and protocol list in the version output. Servers limited to TLS 1.0 will fail when the module attempts to POST JSON payloads.

bash 
curl -V

#OneSignal Service Requirements

A OneSignal account is necessary. If you do not have one, you may signup here. Within the OneSignal dashboard create a new application. This generates the REST API key and App ID required by the module. These values are stored in the addon settings inside the WHMCS admin interface and are used to authenticate every request.

The OneSignal application must be configured for Chrome, Firefox, Edge and Safari support. Complete their web push setup checklist, including domain verification, icon uploads, and insertion of the initialization script into your WHMCS template files. Incorrect SDK placement is a frequent source of silent failures where the subscription bell never appears for visitors.

#Browser Requirements

Push notifications will only work for users on these browser versions and platforms:

  • Chrome 42+ on Windows, Linux, macOS and Android Firefox 44+ on Windows, Linux and macOS Firefox 48+ on Android Safari 7.1+ on macOS (iOS not supported) Edge 42.17134.1.0+ (Windows 10 - April 2018 Update) Opera 37+ on Windows, Linux, macOS and Android Yandex 15.12+ on Windows, Linux, macOS and Android Samsung Internet Browser on Android 4.0+

#Requirements Test Script

We offer a PHP script that will quickly and easily check your PHP and WHMCS installation for any missing requirements. The tool can be downloaded here - https://billing.aspnix.com/dl.php?type=d&id=138. Place the file in your WHMCS root, access it directly in a browser, and examine the output for pass/fail status on each dependency. The script inspects version numbers, extension availability, and TLS capabilities without modifying any files.

After the test script reports full compliance, install the addon and enter your OneSignal credentials. Send a test notification to confirm delivery. If TLS or cURL issues appear, update the server libraries before retrying; these account for the majority of runtime failures with external notification services.