OsTicket

One-Click Installation

OsTicket Initialization:

Overview:

This guide will walk you through initializing OSTicket on your AWS instance in just one click. The setup process is streamlined using our custom script, designed for ease of use and efficiency. Before starting the script, ensure the minimum requirement is met.

Pro Tip: We recommend associating an AWS Elastic IP with your instance before running the setup. This prevents your IP address from changing when the instance is stopped and restarted.

Step 1: Access Your AWS Instance

1. Launch Your AWS EC2 Instance:

  • Choose your desired AWS EC2 instance type. (Recommended: t3a.small / t3.small)
  • Once the instance is running, connect to it via SSH.

2. Connect to the Instance:

  • Open your terminal (Mac/Linux) or use an SSH client (e.g., PuTTY for Windows).
  • Run the following SSH command:
ssh ec2-user@<your-aws-public-ip>
  • When prompted for the login, enter:
[ec2-user@…]$ sudo -i

3. Run the Initialization Script:

  • To initiate the installation, run the following command:
[root@…]$ dnf -y update
[root@…]$ /usr/local/bin/egl_init.sh.x
  • Note: This script automates the entire installation process. While it runs, ensure your terminal remains active, and do not close the session. The script may take up to 10-20 seconds to complete. The script will random generate new credentials for all the necessity.

 

Step 2: Instance Set Up and Installation 

1. Completion Confirmation:

  • Once the installation is finished, you will see a summary on the screen that includes all credentials.

 

2. Access the Web Interface:

  • Open your web browser and navigate to http://<your-public-ip> :
http://<your-public-ip>
  • You will be greeted by the welcome screen.

 

Step 3: Finalizing Installation  

1. Prerequisites

  • Click Contine to proceed if all system checks are ticked. If not, contact our support immediately.
(Click to enlarge)

2. System Settings:

  • Get the database credentials from the summary of initialization script earlier and fill up the database settings, as below.

Table Prefix: ost_ (your preference) 

Hostname: localhost

Database: osticketdb

Username: (the values provided per the output of egl_init.sh.x)

Password: (the values provided per the output of egl_init.sh.x)

  • You may fill up all other fields accordingly per your preference or business need.
  • Once completed, press ‘Install Now‘.

3. Installation Complete:

  • Once the setup is complete, you will see the final “Congratulations” screen.

 

  • Navigate to http://<your-public-ip>/scp/login.php and login with the Administrator credentials you entered in the “Admin User” section earlier.
http://<your-public-ip>/scp/login.php

 

Step 4: Post Installation

1. The “setup” folder is removed for you

osTicket recommends deleting the setup directory once installation is finished. You do not need to do this. It is done for you automatically just after you complete the setup wizard, along with tightening the permissions on the configuration file.

  • Straight after finishing the wizard, osTicket may still show the message “Please take a minute to delete setup directory (../setup/) for security reasons.” at the top of the admin panel. Close your browser and log in again and the message will be gone.
  • No action is required from you, and there is nothing to delete over SSH. The application files live inside a container, not on the instance filesystem, so the older instructions to run rm -rf or mv against /var/www/osticket/setup do not apply to this build.

Next Step: Use Your Own Domain with a Free SSL Certificate

  • Your osTicket instance is served over plain HTTP at its IP address. To use your own domain name with a free SSL certificate, see Associating Your Domain.
  • It takes one command. The certificate is requested automatically, renews itself, and HTTP requests are redirected to HTTPS.

Important Notes:

  • Outbound mail must be configured inside osTicket. This image does not include a local mail server, so osTicket sends through an SMTP server that you provide. Set this under Admin Panel > Emails using your own domain’s SMTP details. AWS blocks outbound port 25 by default, so use port 587 or 465 with your mail provider, and you may also need to ask AWS to lift the restriction on outbound email traffic.
CONTENTS