Troubleshooting

Below are some troubleshooting tips for problems that we have encountered and resolved:

Blank page or HTTP 500 server error.

Check the laravel log file (storage/logs/laravel.log) file for hints. If nothing new was added to the file that is a good hint in
itself. Next, check the Web server error log (/var/log/httpd/error.log) if you see a message such as this one:

PHP Fatal error: Uncaught exception 'UnexpectedValueException' with message 'The stream or
file "/.../.../storage/logs/laravel.log" could not be opened: failed to open stream: Permission
denied' in /.../.../vendor/monolog/monolog/src/Monolog/Handler/StreamHandler.php:97

Check the file permission on the laravel log file (storage/logs/laravel.log) it could be that the process
running your Web server does not have write permission to it.

Node.js

Old version

As pointed out by thassan in Issue 6,
if your distribution or OS ships with an older version of Node.js the name of the executable may be 'nodejs'. In recent versions, the name has
been changed to 'node'. This will cause some Node.js packages to fail during the installation as they expect to find the 'node' executable.
To resolve this issue you can either create a symbolic link from the 'nodejs' executable to 'node', or you may want to consider installing
a more recent version of Node.js.
To create a symbolic link issue the command:

sudo ln -s /usr/bin/nodejs /usr/bin/node

ENOENT error

If the installation of Node.js packages fails with a 'ENOENT' error, you may need to create an empty file at the root of the project as
explained on Stack Overflow.
To create the empty file run:

touch .npmignore

Hangs

If the installation of Node.js packages appears to hang, it may be due to a race condition that does not manifest itself when invoked
with the -ddd after having deleted the node_modules directory at the root of the project:

rm -rf node_modules
npm install -ddd

Composer fails with a memory allocation error

Due to the size of the dependency map generated by the composer.json file, the composer command may fail with a memory allocation error such as this one:

Get in touch

Don't hesitate to get in touch if you have any question or suggestions. The best way to reach out to the community is directly on GitHub by creating an issue, but, if you prefer, you can also email us directly.