Laravel 7 Fatal error: Uncaught RuntimeException: A facade root has not been set - deployment

I have looked at several answers suggested to a similar issue but nothing worked in my case.
FYI, this is my first project in Laravel 7, working fine on my Mac.
I have deployed the project on my server following this article.
When running the project on the web, I get the following error :
Fatal error: Uncaught RuntimeException: A facade root has not been set. in /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php:258
Stack trace: #0 /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(425): Illuminate\Support\Facades\Facade::__callStatic('replaceNamespac...', Array) #1 /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(402): Illuminate\Foundation\Exceptions\Handler->registerErrorViewPaths() #2 /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(313): Illuminate\Foundation\Exceptions\Handler->renderHttpException(Object(Symfony\Component\HttpKernel\Exception\HttpException)) #3 /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(210): Illuminate\Foundation\Exceptions\Handler->prepareResponse(Object(Illuminate\Http\Request), Object(Symfony\Component\HttpKernel\Exception\HttpExcepti in /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php on line 258
How can I fix it?

I finally found a solution that worked in my case.
delete the folder vendor
run composer update
run php artisan config:cache
run php artisan config:clear
Home page now displays but the routes do not work...

If the solution from #Paul Godard doesn't work, it could be a psr/log issue as mine.
My composer update added psr/log v2.0.0, which requires php8. However, my application is on php7.4
That gave me the exact error output like in the description
Fatal error: Uncaught RuntimeException: A facade root has not been set. in /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php:258
My solution was to specify in composer.json that I'm using "psr/log": "^1.1.0"
Then run composer update

I got that error when my config folder was deleted by mistake. So after recovering the config folder. My project worked fine. You have to check if any folder is removed on which project is depending. Recover or copy it. It will work fine then.

Related

I have an error when executing ionic serve

When I execute ionic serve, it shows the following errors:
Refused to load the image 'http://localhost:8100/favicon.ico' because
it violates the following Content Security Policy directive:
"default-src 'none'". Note that 'img-src' was not explicitly set, so
'default-src' is used as a fallback.
Failed to load resource: the server responded with a
status of 404 (Not Found)
How can I solve this?
I had the same error message.
Looking through the logs printed when doing
ionic serve
showed me a bunch of errors, all similar to this
[ng] ERROR in ./src/global.scss (./node_modules/#angular-devkit/build-angular/src/angular-cli-files/plugins/raw-css-loader.js!./node_modules/postcss-loader/src??embedded!./node_modules/sass-loader/lib/loader.js??ref--14-3!./src/global.scss)
[ng] Module build failed (from ./node_modules/sass-loader/lib/loader.js):
[ng] Error: Cannot find module 'node-sass'
[ng] Require stack:
This lead me to get the application up and running again by
npm install node-sass --save
The compilation process is sometimes spitting out rather confusing error messages from time to time, but with a little digging one can start guessing where to start poking
I had the same issue. I was able to solve it. I fixed the routing file, I had a route that couldn't load because another route was higher order.
Ionic include default favicon icon into index.html file.
<link rel="icon" type="image/png" href="assets/icon/favicon.png" />
You can put your favicon icon into "assets/icon" and replace href above.
I had this error and it was because I had included an import I wasn't actually using. In my example, I had accidently imported Console when using console.log.
I was getting error TS2307: Cannot find module 'console'. in the VS Code terminal, but my error in Chrome was "Refused to load the image 'http://localhost:8100/favicon.ico' because it violates the following Content Security Policy directive: "default-src 'none'". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.
Failed to load resource: the server responded with a status of 404 (Not Found)"
So be aware that this error is not necessarily to do with the favicon.
I had same issue but solved using below solution.
<link rel="icon" type="image/x-icon" href="assets/icon/favicon.ico" />
I used .ico file instead of .png file and thats works for me. try once.
I get same error multiple times,this error throw when u missed any small issue like wrong image path or forget to write import statement of any module/service/component.these error will shown in terminal when u running your project.After fixing these run your project
I had the exact same problem.
I advise you to take a look at your Terminal in VSCode (or the standard terminal if you launched it by there) and look for an ERROR message.
Most likely the problem isn't the favicon.ico blabla stuff but another element of your app, something in a .ts doc for example. Via Terminal you can seek for it in a better way than Chrome, that shows you this unrelated message.
I too faced same error .In my case i have done mistake in importing file
import { IUser } from 'src/app/shared/interfaces/IUser
Changed path like below is fixed error.
import { IUser } from './shared/interfaces/IUser
Cross check your import file. it might helps
I got the same error when I downloaded a new branch of the project, I just run npm install of the lastest components
I solved by created copy favicon.png from assets/icon/favicon.png to root project folder and rename it to favicon.ico , and also put it on assets/icon/favicon.ico
and also check this answer .
https://stackoverflow.com/a/63749758/8370334
Same issue here with ionic v5 and angular v10.
You may have this error when you create some error in the variables.scss file.
I was using adding a list of global variable that will be used across the app but I forgot to add a ,.
It didn't create an error while compiling...
The code was :
$color-settings: (
'primary': (
'base': #297bfd,
) // <-- Comma is missing here
'secondary': (
'base': #297bfd,
)
}
It will display the same error, I think, it breaks somehow the way ionic compile the scss.
I had the same issue after an upgrade. I solved the problem doing:
npm rebuild node-sass
Try to change the browser, I fixed this clicking on the url resource which opened firefox and then I've been able to test the app normally on Firefox

How To Fix This Error [Error: Failed to find '#ionic/angular/css/display.css']

When i run the operation ionic serve it fails to compile and gives an error code that says:
ERROR in ./src/global.scss (./node_modules/#angular-devkit/build-
angular/src/angular-cli-files/plugins/raw-css-
loader.js!./node_modules/postcss-loader/src??embedded!./node_modules/
sass-loader/lib/loader.js??ref--14-3!./src/global.scss)
Module build failed (from ./node_modules/postcss-loader/src/index.js):
Error: Failed to find '#ionic/angular/css/display.css'
in [
C:project/src
]
at resolveModule.catch.catch (project\node_modules\postcss-
import\lib\resolve-id.js:35:13)
This is a piece of code i tried to integrate into my own project which opens the camera to take a picture and you can either upload the picture or delete it. I tried searching for "#ionic/angular/css/display.css" on the internet but couldn't find a solution. I started ionic just recently so i don't understand much about it.
If anyone wants to see the code It is here The original i took it from had the code at home.page.ts but i needed it at tab1.page.ts so the error may be born from this. Also global.scss
The method i used to solve the problem is importing "#ionic/angular/css/display.css". I did it manually taking it from a project where it exists and copying it to the Project which gives the error.

sails­postgresql Error while using sails lift command?

While running $ sails lift command , I am getting this error.
info: Starting app...
error: Trying to use unknown adapter, "sails­postgresql", in model `adminintro`.
error: Are you sure that adapter is installed in this Sails app?
error: If you wrote a custom adapter with identity="sails­postgresql", it should be in this app's adapters directory.
error: Otherwise, if you're trying to use an adapter named `sails­postgresql`, please run `npm install sails-sails­postgresql#0.10.x`
Please help me out guys ...
Got the answer ... It was unicode mistake . I have copy n pasted the code for local.js from one of my coworker's pdf file. So when I pasted that code in my local.js "-" was replaced with some unicode http://www.fileformat.info/info/unicode/char/00AD/index.htm .. and that was causing this issue..

Error when running yeoman init

I'm getting the following error when I run `yeoman init angularù, although the angular part shouldn't matter, since I got the same error:
create test/lib/angular-mocks.js
<WARN> Unable to create directory "/Users/myuserfolder/test/lib" (Error code: ENOTDIR). Use --force to continue. </WARN>
it seems to be trying to create a file in my home folder, which is weird, becuse I cd'd into a folder designated for my project. What could be going on here?
That is a known bug caused by you having a Gruntfile in your home directory.

Zend_Tool CLI issues, throwing fatal errors

Before installing PHPUnit on my Ubuntu machine, I thought I had zf.sh all set up correctly. I was able to create a new project without any issues. Now, since installing PHPUnit, everything is not working right.
When I try to create a test project, I get this:
Fatal error: Cannot redeclare class PHPUnit_Framework_TestSuite_DataProvider in /usr/share/php/PHPUnit/Framework/TestSuite/DataProvider.php on line 64
Call Stack:
0.0011 110200 1. {main}() /opt/ZendFramework/ZendFramework-1.9.3PL1-minimal/bin/zf.php:0
0.0011 110320 2. zf_main() /opt/ZendFramework/ZendFramework-1.9.3PL1-minimal/bin/zf.php:23
0.0113 685448 3. zf_run() /opt/ZendFramework/ZendFramework-1.9.3PL1-minimal/bin/zf.php:36
0.0113 685568 4. Zend_Tool_Framework_Client_Console::main() /opt/ZendFramework/ZendFramework-1.9.3PL1-minimal/bin/zf.php:214
0.0114 686044 5. Zend_Tool_Framework_Client_Abstract->dispatch() /opt/ZendFramework/ZendFramework-1.9.3PL1-minimal/library/Zend/Tool/Framework/Client/Console.php:96
0.0114 686164 6. Zend_Tool_Framework_Client_Abstract->initialize() /opt/ZendFramework/ZendFramework-1.9.3PL1-minimal/library/Zend/Tool/Framework/Client/Abstract.php:209
0.0152 866128 7. Zend_Tool_Framework_Loader_Abstract->load() /opt/ZendFramework/ZendFramework-1.9.3PL1-minimal/library/Zend/Tool/Framework/Client/Abstract.php:118
0.4374 2729116 8. include_once('/usr/share/php/PHPUnit/Framework/TestSuite/DataProvider.php') /opt/ZendFramework/ZendFramework-1.9.3PL1-minimal/library/Zend/Tool/Framework/Loader/Abstract.php:90
What do I need to do to get it working again?
Update: I think I understand the reason why this is happening. In PHPUnit 3.4.0 there is a class with the same name as the Zend Framework 1.9.3. Apparently it is a known issue. But how can I get around this so I can use Zend_Tool again?? Can I downgrade PHPUnit? Will that fix the problem?
Update: This tutorial mentions something about installing a diff patch.
I found a temporary workaround:
Edit PHPUnit/Framework.php, near line 70:
require 'PHPUnit/Framework/TestSuite/DataProvider.php';
Change to:
require_once 'PHPUnit/Framework/TestSuite/DataProvider.php';
This is probably not the long-term fix, but it resolves the immediate symptom.
Update 2009-11-20: I just saw a commit to the ZF 1.9 branch that claims to resolve this issue. Presumably the fix will be in the next point-release (1.9.6) and in subsequent minor releases (1.10.0 and later).
Another solution, which doesn't require to change any 3th party code, is copying the PHPUnit folder to a location outside the include_path and create a symlink to the new location instead.
For details on this issue have a look here: Zend_Tool troubles PHPUnit