> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/introduction/supported-versions-and-environments.md). # Supported Versions and Environments Xibo can be run on a variety of environments, web servers and software versions ## CMS Releases Prior releases are supported for a period of time after the release of a new major version: | Version | Status | Release Updates | Xibo Cloud Hosting | | ------- | ----------- | ------------------ | ------------------ | | **4.5** | **Stable** | **Maintenance** | **Current** | | 4.4 | End of Life | No further updates | Existing Supported | | 4.3 | End of Life | No further updates | Existing Supported | | 4.2 | End of Life | No further updates | Existing Supported | | 4.1 | End of Life | No further updates | Existing Supported | | 4.0 | End of Life | No further updates | Existing Supported | | 3.3 | Supported | Maintenance | Existing Supported | | 3.2 | End of Life | No further updates | Not Supported | | 3.1 | End of Life | No further updates | Not Supported | | 3.0 | End of Life | No further updates | Not Supported | | 2.3 | End of Life | No further updates | Not Supported | | 2.2 | End of Life | No further updates | Not Supported | | 2.1 | End of Life | No further updates | Not Supported | | 2.0 | End of Life | No further updates | Not Supported | | 1.8 | End of Life | No further updates | Not Supported | {% hint style="warning" %} CMS versions earlier than 1.8 are all End of Life with no further updates or support. {% endhint %} {% hint style="success" %} We always recommend installing/upgrading to the **Current** CMS release to take full advantage of latest features, improvements and bug fixes. {% endhint %} {% hint style="danger" %} Customers who choose to self-host their CMS, do so with the knowledge that helpdesk support is not provided. {% endhint %} {% hint style="success" %} Customers who choose to host their CMS with us or add their self-hosted CMS to our Enterprise Plan are subject to Supported Environments, as outlined below to access helpdesk support to open tickets regarding your CMS or Players (provided that they are a supported version). {% endhint %} ## Player Releases Our general recommendation is that your CMS and Players should be of the same major version for best results. For example a version 4 Player with a version 4.x CMS. The current stable Player version is supported and recommended, and support is offered for the most recent previous major Player version too. Anything outside of that is unsupported and you will need to upgrade to a supported version to access support. ### Windows | Major Version | Status | Release Updates | Required OS | Recommended OS | | ------------- | ----------- | ------------------------ | ----------------------------------- | ------------------------------------------- | | 4 | Current | Features and Maintenance | Windows 10 or later | Windows 10 Professional build 1909 or later | | 3 | Supported | Security | Windows 10 or later | Windows 10 Professional build 1909 or later | | 2 | End of Life | No further updates | Windows 7 or later (up to v2 R203 ) | Windows 10 Professional build 1909 or later | | 1 | End of Life | No further updates | | | Not compatible with ARM-based CPUs ### Linux | Major Version | Status | Release Updates | Required OS | Recommended OS | | ------------- | ----------------------- | ------------------------ | ----------------------------------------------------------- | ----------------------------------------------------------- | | 1 | Legacy Community Player | Features and Maintenance | 64 bit Linux supporting the Snapcraft distribution platform | 64 bit Linux supporting the Snapcraft distribution platform | 64 bit AMD/Intel CPU required. Not compatible with 32 bit or ARM based CPUs ### Android | Major Version | Status | Release Updates | Required OS | Recommended OS | | ------------- | ----------- | ------------------------ | ----------- | -------------------- | | 4 | Current | Features and Maintenance | Android 7 | Android 9 or later | | 3 | Supported | Security | Android 6 | Android 7.1 or later | | 2 | End of Life | No further updates | Android 4.4 | Android 7.1 or later | | 1 | End of Life | No further updates | Android 4.4 | Android 7.1 or later | ### webOS | Major Versions | Status | Release Updates | Required OS | | -------------- | ----------- | ------------------------ | ------------------ | | 4 | Current | Features and Maintenance | webOS 3.2 or later | | 3 | Supported | Security | webOS 3.0 or later | | 2 | End of Life | No further updates | webOS 3.0 or later | | 1 | End of Life | No further updates | webOS 3.0 or later | ### Tizen | Major Versions | Status | Release Updates | Required OS | | -------------- | ----------- | ------------------------ | --------------------------------------- | | 4 | Current | Features and Maintenance | Samsung signage monitors SSSP6 or later | | 3 | Supported | Security | Samsung signage monitors SSSP5 or later | | 2 | End of Life | No further updates | Samsung signage monitors SSSP5 or later | | 1 | End of Life | No further updates | Samsung signage monitors SSSP5 or later | ### ChromeOS | Major Versions | Status | Release Updates | | -------------- | ------- | ------------------------ | | 4 | Current | Features and Maintenance | ## Supported Environments The following lists the recommended environment that is required for a self-hosted CMS to be included and supported as part of an Enterprise Plan, or to be covered under a legacy Enterprise Support Contract, or for the Xibo team to offer paid per-incident support via the Helpdesk. Should you choose to install the Xibo CMS outside of this supported configuration, support is not included. ### **Supportable Configuration** * Ubuntu Server 64 bit running on an x86-64 architecture CPU - any current LTS release (20.04, 22.04, 24.04) or the Debian equivalent. * Minimum 4GB RAM. * Minimum 20GB free storage space (SSD/NVMe ideally), plus however much storage you will need to upload your content to the CMS, and to store any logs and proof of play data you might want to collect. * Access to the server running the CMS via SSH/HTTPS or TeamViewer, or TeamViewer access to a workstation with SSH/HTTPS access to the CMS. Access must be possible as the user `root` or as a user with full `sudo` permissions to become `root`. * Server must have access to the Internet to download the provided container images. * Installation with Docker using the docker-compose files we provide for the CMS installation * Optionally (but recommended) an nginx or Apache reverse proxy infront of the CMS handling TLS termination * One each of a cms-web, one cms-db, one cms-xmr container, and with memcached enabled * No modifications to the contents of the provided containers * Any white labelling must be applied by the use of a theme. We reserve the right to temporarily disable the theme to see if a custom theme is the cause of any issues with the CMS * Any custom code must be in the form of a separate custom module or middleware. We reserve the right to temporarily disable any custom code to see if it is the cause of any issues with the CMS. Any custom code falls outside the scope of support. ## Helpdesk Support Helpdesk support is for the installation, configuration and licensing of our Commercial Players (Android, webOS, Tizen and ChromeOS) only, except where Players are connected to a Xibo Cloud Hosted CMS, or a self-hosted CMS covered on the Enterprise Plan, or under a legacy Support Contract. Customers with Perpetual Player licenses may need to purchase upgrades and upgrade their Player version to be able to access Helpdesk support. {% hint style="warning" %} The Linux Player is a Community-contributed Player and whilst you may use it with a Cloud CMS or a CMS hosted on an Enterprise Plan, we regret that we cannot offer support for it at the current time. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.xibosignage.com/introduction/supported-versions-and-environments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.