This page lists common errors and the steps needed to troubleshoot them.

Enable debugging

In the .env file there is a configuration option


set this value to true to see debugging information. Any errors should be logged in storage/logs

Permissions issues

Attendize requires write access to files within the document root. This can be the cause of quite a few issues. Make sure the following directories are writable by the web server user.

  • storage/app/
  • storage/framework/
  • storage/logs/
  • storage/cache/
  • public/user_content/
  • bootstrap/cache/
  • .env

Trouble generating PDF tickets / Checkout failing

  1. Attendize needs to be configured to send email using SMTP. If it can’t send email it will log the exception in storage/logs if APP_DEBUG=true is set in the .env file. The SMTP settings can be found in the .env file.

  2. Attendize uses Wkhtml2PDF to generate tickets. If you are getting errors while generating PDFs make sure all the driver files in vendor\nitmedia\wkhtml2pdf\src\Nitmedia\Wkhtml2pdf\lib are executable. . Also make sure this folder is owned by your webserver user. If you used composer as root to install the dependencies for the project ownership of this directory can be wrong which can cause generation of tickets to fail.

Also make sure the setting for WKHTML2PDF_BIN_FILE is correct in the .env file. The acceptable options are:

  • wkhtmltopdf-0.12.1-OS-X.i386 - Mac OS X 10.8+ (Carbon), 32-bit
  • wkhtmltopdf-amd64 - Linux (Debian Wheezy), 64-bit, for recent distributions (i.e. glibc 2.13 or later)
  • wkhtmltopdf-i386 - Linux (Debian Wheezy), 32-bit, for recent distributions (i.e. glibc 2.13 or later)

Installer not showing up?

Try navigating to If that works and doesn’t, it means your server configuration needs to be updated.

Make sure the mod_rewrite module is enabled and the .htaccess file is being recognised.

On Nginx, use the following directive in your site configuration: location / { try_files $uri $uri/ /index.php?$query_string; }