Jira Data Center Health Check: Fonts

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

This health check verifies that Jira has access to the system fonts it relies on. Missing fonts might result in errors when generating reports, or text displaying as unclear or garbled.

We’ve introduced this health check because some Java distributions don’t include any font configuration packages, which results in these problems. AdoptOpenJDK for example, does not include a font configuration package.

If you’re here, it probably means you’ll need to install this package.

Results

Icon

Result

What this means

Green Checkmark

System fonts are available, and no issues have been detected.

No action is required.

Red Circle with Exclamation Mark

Some fonts are missing.

The Java distribution you're using is missing font configuration packages. You can fix this problem by installing fontconfig, as described below.

Diagnosis

When reviewing the atlassian-jira.log files, users may see the following error message indicating that system fonts are missing:

1 2022-08-18 09:13:22,254-0400 Caesium-1-4 WARN ServiceRunner [c.a.t.healthcheck.concurrent.SupportHealthCheckProcess] Health check 'Fonts' failed with severity 'warning': 'System fonts are not available. Please make sure correct font packages are installed.'

In addition, users may also see that the Health Check fail for the Fonts feature in the healthcheckResults.txt file with the following error:

1 2 3 4 5 Name: Fonts NodeId: null Is healthy: false Failure reason: System fonts are not available. Please make sure correct font packages are installed. Severity: WARNINGAdditional links: []

Solution

Install fontconfig (or an equivalent), and restart Jira.

Use our script to install

The script is available in Jira 8.2 or later. If you're on an earlier version, use the commands described further below.

If you're using Ubuntu, CentOS, RedHat Enterprise (RHEL), Debian, or Fedora, we've created a script to install the required package for you.

To install the font package:

  1. Change to the /bin directory of your Jira installation

  2. Run the install_fontconfig.sh script.

    1 $ sudo ./install_fontconfig.sh
  3. Restart Jira.

Install it yourself

Here are the commands to install the font dependency in several common Linux distributions and package managers, including Windows.

Ubuntu

To install the fontconfig package on Ubuntu 18:

1 sudo apt install -y fontconfig

CentOS

To install the fontconfig package on CentOS 8 and above:

1 sudo yum -y install fontconfig

CentOS 6/7

CentOS 6/7 does not work with fontconfig. You can install dejavu-sans-fonts as an alternative:

1 sudo yum install -y dejavu-sans-fonts

RHEL

To install fontconfig on RedHat Enterprise Linux 7.5:

1 sudo yum install fontconfig

Debian

To install the fontconfig package on Debian 9.5:

1 apt-get update && apt-get install -y fontconfig

Fedora

To install the fontconfig package on Fedora 28:

1 dnf install -y fontconfig

Windows

The issue may be caused by the dejavu-sans-fonts missing from the Windows server where Jira is installed.To install missing fonts for Windows:

The solution can be solved by performing the following steps in the Fix font healthcheck on Windows serverCommunity Article:

  1. Download the latest version of the font package from https://dejavu-fonts.github.io

  2. Unzip the zip package

  3. Open the tff directory

  4. Open each font and click install

    You can also select all files and right click. Select install in the context menu. It will install the 22 items.

  5. Restart Jira

Related articles

Updated on April 15, 2025

Still need help?

The Atlassian Community is here for you.