Technical Anshu
Tutorials Blog
Faveo Installation

Install Faveo Helpdesk on Your Own Server Step by Step

Faveo is free, but it is a real server application - a Laravel and PHP program that needs a web server, PHP extensions and a MySQL database. This guide walks the install in the right order and is honest about the effort involved.

By Technical AnshuLinux ServerPHP and MySQLStep by step
Watch the full video - Faveo Helpdesk download, installation and complete setup, step by step

Many people download Faveo, click around for ten minutes and give up at the first error. The errors are almost never Faveo's fault - they are a missing PHP extension, a wrong database password or a folder the web server cannot write to. Install the stack properly first and the Faveo installer itself takes only a few minutes. Here is the honest, complete route.

Faveo Installer - Server Requirement Check (illustration)
☑ PHP version and web server detected PASS
☑ OpenSSL, PDO, Mbstring, Tokenizer extensions PASS
☑ MySQL database connection PASS
☑ Storage and cache folders writable CHECK
☑ Scheduled task for email fetching MISSING
Illustration of the installer check list. The last line is the one most people skip - without the scheduled task, no email ever becomes a ticket.
1

The Stack in Plain Words

Faveo Helpdesk is built on the Laravel framework, which means it runs like most modern PHP software:

  1. Web server - Apache or Nginx serves the pages.
  2. PHP - a current PHP version with the extensions the official manual lists, including OpenSSL, PDO, Mbstring and Tokenizer.
  3. MySQL database - every ticket, user and setting lives here. This is the data you must protect.
  4. A scheduler - a small background job (cron on Linux) that runs every minute and triggers email fetching, SLA checks and auto-close rules.

Faveo's own documentation gives install guides for common Linux distributions with both Apache and Nginx, including adding a free Let's Encrypt SSL certificate. Follow the guide for your exact operating system instead of mixing steps from three blogs.

2

Pick the Machine - and Be Honest About the Effort

For a small office, the machine can be modest: a small cloud VPS or a spare office PC with a couple of gigabytes of RAM runs a small team's helpdesk comfortably. Two conditions matter more than power. The machine must stay on - a helpdesk on a PC that sleeps at night misses email and SLA alerts. And it should be a machine you are willing to patch and back up, because it will hold your company's support history.

The honest effort report: an experienced Linux admin finishes in under an hour. If this is your first PHP application, keep half a day - not because Faveo is hard, but because server basics like DNS, file permissions and database users take the time they take. That half day is the real price of the word free, and it is still far cheaper than a per-agent subscription.

3

Prepare the Database and the Files

Before touching the installer, prepare three things:

  1. Create the database in MySQL and a database user with full privileges on that database only. Write down the database name, username, password and host exactly.
  2. Upload the Faveo files to the web folder and point your domain or subdomain at the application. The official guides use a subdomain such as support.yourcompany.com.
  3. Make the storage and cache folders writable by the web server user. The installer checks this - a read-only folder is the most common first failure.

One security habit from the start: the database user for Faveo should not be the MySQL root account. A dedicated user that can only touch the Faveo database limits the damage if anything ever goes wrong.

4

Run the Web Installer

Open the subdomain in a browser and the installer starts with the requirements check. Every line must pass. A missing PHP extension is fixed on the server (install the extension package and restart the web server), never by skipping the step.

Then enter the database details you prepared. The installer creates all the tables itself - you never import SQL by hand. After that you create the administrator account and log in. Set the timezone and company details right away; ticket timestamps and SLA clocks are wrong until you do.

Last, the step that decides whether the system lives or sleeps: add the scheduled task. Laravel applications run all their background jobs from one scheduler entry, which on Linux looks like this in the server crontab:

  1. * * * * * php /var/www/faveo/artisan schedule:run

The exact path is your install folder. With this running, Faveo fetches email, watches SLA deadlines and auto-closes old resolved tickets by itself. Without it, everything waits for someone to open a page.

5

First Checks After the Install

Before inviting a single user, run this short acceptance list:

  1. HTTPS works. Add the free Let's Encrypt certificate from the official guide - logins and passwords must never travel on plain HTTP.
  2. Admin login works from a different computer on the network, not only from the server itself.
  3. Send a test email to the support mailbox and watch a ticket appear within one fetch cycle.
  4. Take a backup now - database dump plus the application folder - while the install is fresh and known-good. This is your return point if later experiments go wrong.

If all four pass, the installation is done and you can move to structure: departments, agents and roles, which the next guide in this series covers.

🖥️ The one step people skip: the scheduled task. Faveo does not fetch email or check SLA timers when someone merely installs it - those jobs run from the server scheduler. Installs that look dead are usually just missing this one line. Set it, then send a test email and watch the ticket arrive before you do anything else.

Watch the Complete Video Guide

The video installs Faveo Helpdesk on screen from download to first login - watch it alongside this guide and your install will follow the same path.

Watch Full Video
Common Questions (FAQ)

Can I install Faveo on a Windows server?

Faveo is a PHP and Laravel application and the official documentation is written around Linux servers with Apache or Nginx - that is the smooth, supported-feeling path. A small Linux VPS costs very little and avoids fighting Windows-specific PHP quirks, so for almost every small office the Linux route is the honest recommendation.

Can I use cheap shared hosting instead of a VPS?

Sometimes, but it is the risky option. Faveo needs the right PHP extensions, a MySQL database and, critically, a scheduled task that runs every minute - many shared hosts restrict exactly those things. If the host cannot give you all three, the helpdesk will install but email fetching will silently fail. A basic VPS is the reliable minimum.

How long does the installation really take?

The Faveo installer itself is a few minutes once the server is ready. The real time is in preparing the server - PHP, extensions, database, domain and SSL. An experienced admin needs under an hour in total; a first-timer should keep half a day and a cup of patience. Either way it is a one-time cost.

This guide is based on the Technical Anshu video on the Faveo Helpdesk ticket system. Stuck on a step? Ask in the video comments - you will get an answer there.