This post is in response to a request we received via a comment from our youtube.com/HendGrow channel on a guide on RT installation.
NOTE: This guide and the included script will only work if you have followed our guide on installing an RT5 base with our script. (Scrtip is editable and can be found within guide [45] REQUEST TRACKER – ONE SCRIPT INSTALL!
Refresh your browser, you should now see an RTIR tab as shown in the below image.
—End—
There is still a lot to do, like configuring the domain to use, SSL, RT email gateway, task scheduler, full-text search, general system security etc etc….
If you would rather have the Virtual machine in OVA format we used in this guide? Reach out details on our contact page.
This guide does not cover server/application hardening, or security as it is a broad topic dependent on many variables and not the aim of this guide. That’s potentially for a future guide should there be demand.
Consider subscribing & following us if you find this content helps! It enables this type of content to reach others who might also find it useful & valuable. Also, feel free to leave a comment or message directly if you have questions:
Due to the popularity, good feedback, and support requests we received for our original request tracker guide, we decided to respond to a request to look at how to automate this installation a bit more than the previous guide. So, we created an install script that installs Request Tracker 5.0.7 from a base Ubuntu server to the point of the web UI login. An overview diagram is below.
Below is the Bash installation script to install Request Tracker (RT) 5.0.7 on an Ubuntu 24.04.2 LTS base server. (Should work on any Debian-based system 😉). This script assumes a fresh system, installs the necessary dependencies, downloads RT 5, configures it with MariaDB as the database, and sets up Apache as the web server. It’s designed to be run as root (using sudo) and includes basic error handling.
Please note:
This script is tailored for a typical setup and may need adjustments based on your specific environment.
It uses the latest stable version of RT 5 (5.0.7) available as of March 2025
You should first review and test this script in a non-production environment.
During the installation, you will receive prompts that require a response. Below, I have captured the responses we used for the prompts during the creation of this walk-through guide.
1st prompt: Would you like to configure as much as possible automatically? [yes] –> Response = yes
Note: Don’t be concerned about seeing the MISSING messages. the script will rectify this at a later stage.
2nd prompt: Continue anyways? [y] –> Response = y
3rd prompt: Check for a new version of the Public Suffix List? [N] –> Response = N
4th prompt: Do you want to run external tests? These tests *will* *fail* if you do not have network connectivity. [n] –> Response = n
5th prompt: These test will detect if there are network problems and fail soft, so please disable them only if you definitely dont’t want to have any network traffic to external sites. [Y/n] –> Response = Y
6th prompt: Do you want to build the XS Stash module? [y] –> Response = y
7th prompt: Do you want to use the XS Stash by default? [y] –> Response = y
8th prompt: Password: –> Just press the return/enter key.
Open your browser and enter the IP Address of your server. In our example it is
192.168.2.125
Login with Username = root & Password = password
How to remove the “Possible cross-site request forgery” message RT 5.0.7 will show when making changes via the Web UI.
Possible Cross-site request forgery message RT5
Edit the RT_SiteConfig.pm and add your server’s IP Address. this will remove the “Possible cross-site request forgery” message.
Steps below:
sudo vi /opt/rt5/etc/RT_SiteConfig.pm
Set( $WebDomain, 'your-servers-ip' );
or
Set( $WebDomain, 'your-domain' );
Restart Apache
sudo systemctl restart apache2
—End—
If you would rather have the Virtual machine in OVA format we used in this guide? Reach out details on our contact page.
If you got to this stage of the guide, congratulations you now have a basic installed and working instance of Request Tracker 5.0.7! There is still a lot to do, like configuring the domain to use and linking it, SSL, RT email gateway, task scheduler, full-text search, general system security etc etc.
This guide does not cover server/application hardening, or security as it is a broad topic dependent on many variables and not the aim of this guide. That’s potentially for a future guide should there be demand.
Consider subscribing & following us if you find this content helps! It enables this type of content to reach others who might also find it useful & valuable. Also, feel free to leave a comment or message directly if you have questions:
