Common causes of errors (500/404 errors)
The first place to look if you're seeing 500 errors is the Apache (or Nginx) error log. You should see the reason for the error logged there. Below are some common problems that might cause a 500 error, or a 404 error.
A common problem when uploading the Bugify files to your server via FTP from a Windows machine is the .htaccess file gets left out. This often results in a 500 error being logged to the Apache error log.
Please ensure the
./public/.htaccess file is copied
over to your server.
Bugify uses a .htaccess file to define the rewrite rules for the
site. If the Apache virtual host config for the site is set to
AllowOverride None the .htaccess file will be ignored.
Please change the setting to
Please also ensure that
installed/enabled on your server. It is usually enabled, but if
you're having trouble, trying checking
see if it's listed there.
If you're running Bugify on its own domain (recommended), most
of the files are kept outside the web root so they aren't publicly
accessible. If you're seeing errors in the error log similar to
open_basedir restriction in effect, your server might
be set to restrict your website from accessing any files that
aren't in the publicly accessible folder. In this case, you will
need to change the
open_basedir path to allow Bugify
to use its files that are stored outside the web root. For example,
if your site is stored at
open_basedir path might need to be changed to
This is not a very common problem so make sure you check your error logs before making any changes to
Some server setups require you to add the following to your
After unzipping the Bugify files on a Mac, you generally need to
change the file permissions and ownership using the following
commands. Note that in the commands below
refers to the folder created when unzipping - so beneath that
folder would be the
chown -R _www bugify chmod -R 755 bugify