Amazon Bekleidung Trikot Shirt Ray 52 Xxxl Lewis Baltimore American Jersey 56 Ravens Black Mens Size Football Elite de

Snipe-IT Asset Management Installation Documentation

Welcome to the Snipe-IT documentation hub. You'll find comprehensive guides and documentation to help you install Snipe-IT as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Search results for ""

No results found for "". 
    Youth Allen Youth Jersey Keenan Allen Allen Keenan Jersey Keenan
View All Results
Youth Allen Youth Jersey Keenan Allen Allen Keenan Jersey Keenan Youth Youth Allen Youth Jersey Keenan Allen Allen Keenan Jersey Keenan Youth
keenan allen youth jersey

500 error

If you're seeing the error "Whoops. Something went wrong" with no other output on the screen and a status code of 500, you'll need to turn on debug mode or look at the log file in storage/logs/laravel.log.

In Production?

It's generally not a good idea to enable debugging in a production app. Instead look at the error logs in storage/logs/laravel.log.

There are many reasons why you might trigger a 500 error (misconfigured .env file, etc), but we won't be able to help you unless you can provide us with a stacktrace, either by enabling debug mode, or by looking in your app logs, located at storage/logs/laravel.log.

To enable debug mode:

  • Open your .env file and change APP_DEBUG=false to APP_DEBUG=true
  • From the command line at your Snipe-IT project root, run php artisan config:clear


It is quite literally impossible for us to be able to assist you with a 500 "Whoops" error without additional information. The stack trace tells us where the error is occurring, and what might have triggered it.

When debug is enabled, you'll see a long stack trace on your screen:

In order to be able to see what's happening on your install (what specific errors you're triggering), we need the entire stack trace from that page, or as much of the app error log as is possible.


When opening a Github issue and providing the stack trace, please copy+paste the errors into the Github issue. Do not attach them as files. If you're not familiar with GH Markdown, we'll reformat it for you to make it more readable.

If for some reason you cannot enable debug but you have access to the app logs, the easiest way to provide us with ONLY the relevant information (which will make it easier for us to troubleshoot your issue), is to tail the log file and then trigger the error.

com Washington 2007 Amazon amp; Redskins Ness Nfl Jersey Sean Red Authentic Clothing 3xl Taylor Mitchell

Type the following into a Linux command line prompt at your Snipe-IT project root:

tail -f storage/logs/laravel.log

Then trigger the error again, which would give you output like this:

You can then copy and paste that, or you can tail the error log and output the relevant information into a file:

tail -f storage/logs/laravel.log > snipe-logfile.txt

To tail a log file on IIS, you can use Powershell:

Get-Content C:\inetpub\wwwroot\snipe-it\storage\logs\laravel.log -Wait

If you're not comfortable with Powershell, see the other options available to Windows users at this StackOverflow article.

Then copy and paste the contents of that file into the Github issue. (Remember, don't attach it, paste it in.) Be sure to redact any personal or sensitive data before including it in Github. Information such as database passwords, email passwords, app keys, etc should NEVER be exposed on Github.


Once your issue is resolved, ALWAYS turn APP_DEBUG back to false, and clear your config cache again. Leaving debug mode on in a production environment can expose sensitive information about your filesystem and database. Debug should NEVER be left enabled on systems exposed to the outside world.