Skip to main content

FAQ & Troubleshooting

Installation Issuesโ€‹

The page is blank after installationโ€‹

A blank white page almost always means a PHP error that is being silently suppressed.

  1. Open the file storage/logs/laravel.log in a file manager (your hosting control panel's File Manager, or FTP). Look at the last few lines โ€” there will be an error message explaining what went wrong.
  2. Common causes:
    • Missing PHP extensions (check the requirements page)
    • Wrong file permissions (see permissions section below)
    • Bad database credentials in the configuration file

500 Internal Server Errorโ€‹

This means the server encountered an error it could not recover from.

  1. Check storage/logs/laravel.log for the actual error message.
  2. Check your web server's error log โ€” in cPanel, this is under Logs โ†’ Error Log.
  3. Most common causes:
    • Wrong database credentials
    • The APP_KEY value is missing or too short in the configuration file
    • A required PHP extension is not enabled

The installer keeps redirecting me back to the startโ€‹

This usually means the installer cannot write to the disk. The installation process creates a file called storage/installed.lock when it finishes. If it cannot create that file, it thinks installation never completed.

Fix: Make sure the storage/ folder and everything inside it is writable. In your hosting file manager, right-click the storage folder and set permissions to 755 or 775.

Database connection failedโ€‹

The error message in the installer will say "Connection refused" or "Access denied".

  • Double-check the database hostname, database name, username, and password. These are all set when you create a database in cPanel.
  • The database hostname for cPanel hosting is almost always localhost.
  • Make sure the database user has full permissions on the database.

Permission errors (cannot write to storage or cache)โ€‹

LeadHub needs to write to certain folders. If you see errors about not being able to write files:

In your hosting file manager, make sure these folders are set to permission 755 (some hosts need 775):

  • storage/
  • storage/logs/
  • storage/framework/
  • storage/app/
  • bootstrap/cache/

Email Issuesโ€‹

Emails are not being sentโ€‹

  1. Go to Settings โ†’ Email and check all fields are filled in correctly.
  2. Click Send Test Email and enter your own email address.
  3. If the test email does not arrive, check the storage/logs/laravel.log file for any SMTP error.
  4. Make sure the cron job is running โ€” emails go through the job queue, which needs the cron job to process. See the Cron Job section below.

Emails are going to spamโ€‹

  • The most common cause is the "From Email" address not matching a domain authorized by your SMTP provider.
  • Add SPF and DKIM records to your domain's DNS settings. Your email provider (SendGrid, Mailgun, etc.) will tell you exactly what to add.
  • Avoid using personal Gmail or free email addresses as your From address for transactional email. Use a professional sending service.

Test email failsโ€‹

  • Check your SMTP credentials โ€” even one wrong character causes failure.
  • For Gmail, you must use an App Password, not your regular password.
  • Port 587 may be blocked on shared hosting. Try port 465 with SSL instead.
  • Ask your hosting provider if outbound SMTP is allowed on the port you are using.

Cron Job Issuesโ€‹

Automations are not running / Reports are not being deliveredโ€‹

LeadHub uses one cron job to process all background work: automations, email sending, report delivery, and scheduled tasks.

The cron job command is:

php /path/to/your/leadhub/cron.php

Replace /path/to/your/leadhub/ with the actual path on your server.

To set this up in cPanel:

  1. Log in to cPanel.
  2. Go to Cron Jobs.
  3. Set the frequency to Every Minute (fill in * for all five fields).
  4. The command: php /home/yourusername/public_html/cron.php
  5. Click Add New Cron Job.

If you are unsure of the path, check with your hosting provider, or look at the full path shown in the cPanel File Manager when you navigate to your site's root folder.

There are no other commands to run. Do not try to run artisan commands from cron โ€” use only cron.php.

How to check if the cron job is runningโ€‹

In cPanel, go to Cron Jobs and look at the cron job you created. If it is listed there, it is scheduled. To verify it is actually executing, you can temporarily add >> /tmp/crontest.log 2>&1 to the end of the command, wait a minute, then check the file for output.

Lead Source Issuesโ€‹

Webhook not receiving leadsโ€‹

  1. Check that the webhook URL you configured in the external service (Facebook, Typeform, etc.) is exactly correct, including the token at the end.
  2. In LeadHub, go to the integration or lead source settings and look for a "Test" or "Ping" button โ€” use it to verify the connection.
  3. Check storage/logs/laravel.log for any incoming webhook errors.
  4. Make sure your server is accessible from the internet (not behind a firewall blocking incoming connections).

IMAP inbox not being polledโ€‹

IMAP polling (checking an email inbox for leads) requires the cron job to be running. See the Cron Job section above. If the cron job is running but IMAP is still not polling:

  1. Check the IMAP connection settings in the integration configuration.
  2. Make sure the php-imap PHP extension is installed on your server.
  3. Check storage/logs/laravel.log for IMAP connection errors.

Performance Issues on Shared Hostingโ€‹

The app is slow or times outโ€‹

Shared hosting has limited resources. A few things you can do:

Increase PHP memory limit: Add this line to the .htaccess file in your site's root folder:

php_value memory_limit 256M

Or ask your hosting provider to increase it in your PHP settings.

Enable caching: Make sure your configuration file has CACHE_DRIVER=file or CACHE_DRIVER=database. These work on shared hosting without extra setup.

Reduce queue batch sizes: If your server is struggling with large imports or bulk operations, process smaller batches.

How to Check Logsโ€‹

The main log file is at:

storage/logs/laravel.log

You can view this in your hosting file manager by navigating to it and clicking to open. Look at the bottom of the file โ€” that is where the most recent errors appear.

The log file can get large over time. You can safely delete it (the app creates a new one automatically).

How to Clear the Cacheโ€‹

If you see stale data or pages that do not reflect recent changes, clearing the cache may help.

Do this through your hosting file manager:

  1. Navigate to bootstrap/cache/
  2. Delete all files inside this folder (but not the folder itself)
  3. Navigate to storage/framework/cache/data/
  4. Delete all files and subfolders inside this folder

The cache rebuilds automatically on the next page load.

Do not delete the folders themselves โ€” only the contents.

How to Re-Run the Installerโ€‹

If you need to go through the installation wizard again (for example, after moving to a new database):

  1. In your hosting file manager, navigate to the storage/ folder.
  2. Delete the file named installed.lock.
  3. Visit your site in a browser โ€” the installer will start automatically.

This does not delete your data. It just lets the installer run again. Your database and files remain intact.

Common Configuration File Mistakesโ€‹

The configuration file (.env) in your site's root folder controls many settings. Common mistakes:

  • Missing APP_KEY โ€” this must be a 32-character random string. If it is missing or wrong, the app will not start.
  • Wrong DB_HOST โ€” for shared hosting, this is almost always localhost. Do not use your domain name.
  • Spaces around = โ€” the format is KEY=value with no spaces. KEY = value does not work.
  • Values with special characters not quoted โ€” if your database password contains # or &, wrap the whole value in double quotes: DB_PASSWORD="my#p@ss&word"

Getting Helpโ€‹

If you cannot solve a problem using this documentation:

  1. Check the log file at storage/logs/laravel.log first. The error message there often tells you exactly what is wrong.
  2. Search the CodeCanyon comments on the LeadHub product page โ€” many common issues have been answered there.
  3. Open a support ticket on CodeCanyon by going to the LeadHub product page and clicking Support. Attach the relevant section of your log file when you do.

When contacting support, always include:

  • Your hosting environment (shared hosting / VPS, which provider)
  • The PHP version your server runs
  • The last few lines of storage/logs/laravel.log