The “Whoops, looks like something went wrong” error can appear whenever a user navigates to a web resource powered by a free open source web framework called Laravel. The reason for the error is that the owner of the site – or the web developer who worked on it on request – did not configure it correctly. In this article we will take a closer look at the error “Whoops, looks like something went wrong”.
Causes of the error “Whoops, looks like something went wrong”
Let’s take a look at the possible reasons why this error could occur. In fact, it can manifest itself due to many factors, however, there are several quite characteristic and most common reasons for it.
- Composer did not create an env file.
- the site is based on an outdated version of the “Laravel” tools;
- error No supported encrypter found.
As you can understand from the above reasons, the error “Whoops, looks like something went wrong” is definitely not the fault of the user who went to this resource. The problem lies in the incorrect configuration of the site – the fault lies with its owner / web developer.
Solution to the error “Whoops, looks like something went wrong”
Let’s now see how you can resolve the “Whoops, looks like something went wrong” error if you are the resource owner / developer.
- Editing the env file. First, you need to try editing the APP_DEBUG = false line inside the ENV file. Change the value in this line to true, then save the change and try again to go to the page. Many web developers claim that this is how you can easily get rid of the “Whoops, looks like something went wrong” error if it starts bothering you.
- Assuming you are using the Printer Installer server, navigate to C: Program Files (x86) PHP (PHP version) and open the php.ini configuration file. In this file, you need to find the line display_errors and change its value to on. This will open access to additional information on error, which can be provided to the technical support of the web resource if you are not its developer.
- You need to make sure that there are not one, but two types of ENV file in the settings directory. One of them is a file with the extension .env, and the other .env example, which contains the key from the site. Once you have verified that these files are present, enter the command cp .env.example .env php artisan key: generate. After entering the command, the error “Whoops, looks like something went wrong” should be eliminated.
- Among other things, this error can be caused by an outdated version of Composer. To update it, you just need to enter the command composer self-update, with which it will be updated.
- There is one more thing you can try to fix this error: go to the app / config / directory and open the app.php file; go down to line number 81 and see if there is a key consisting of 32 characters; if not, create it.
Ok, but what if you are not the owner of the site or its web developer? What to do in this case? Well, in a situation like this, there isn’t much you can do. The only solution in this case is to contact the administration of the web resource and point out the error “Whoops, looks like something went wrong”.