On this page:
If you would like to export table reports, Gantt charts, Gauge charts, or dashboard pages to PDF or if you would like to send regular emails with dashboards as PDF attachments, then you need to install the headless Google Chrome browser on your Confluence server. Google Chrome on the server will be used by eazyBI to convert eazyBI web pages to PDF files.
Install Microsoft's Core Fonts
To get the best looking PDF export, eazyBI needs mscorefonts package.
Install the mscorefonts package on your server. Here are example how to do it on Ubuntu and RedHat.
The mscorefonts package is available in the main repository:
The mscorefonts package should be installed from it's home page as described there.
Install Google Chrome on the server
google-chrome-stable package on your server. Here are example how to do it on Ubuntu and RedHat.
Install from the Google Chrome repository.
Enable Google YUM repository:
Install the package:
Download and install the Google Chrome for Windows. Please ensure that you have version 62 or later.
If you have your local Confluence Server on macOS then also just download and install the Google Chrome for macOS. Please ensure that you have version 62 or later.
After you have installed Google Chrome please disable and re-enable eazyBI app from Confluence Administration / Manage Apps.
During the startup, eazyBI will detect installed Google Chrome and will start to use it for PDF exports. Please visit any dashboard page and try to export it to PDF.
If you see an error message "Google Chrome is not found on the server." then you could try to specify the path to it manually via advanced settings:
If you have any problems with PDF export after Google Chrome is installed then check:
- System Administration / System Events page and see if you have any errors there.
eazybi-web.logfile from the Troubleshooting page.
Please download eazyBI log files from the Troubleshooting page and send to eazyBI support if you need help with solving PDF export problems.
If you see an error message
Unable to connect [localhost:9250] then it probably means that google-chrome failed to start.
- It could fail to start if you are trying to start the process using user root, try to use a different user.
- It could fail to start if you are using docker, then you can override default security profile with
--security-opt seccomp=unconfinedplease check Docker docs for more information on security profiles.