[GH-ISSUE #343] Arch and Nginx error after installation "ErrorException in Application.php line 50" #248

Closed
opened 2026-02-26 02:32:34 +03:00 by kerem · 4 comments
Owner

Originally created by @BugMaze on GitHub (May 27, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/343

Hi . I'm trying to install koel on Arch and nginx/php-fpm . Everything installs fine and npm, compose and gulp all excute perfectly . I sat up a Mariadb correctly and filled up the .env with the required info .
However pointing my browser to https:/MY_DOMAIN/koel returns these errors :
http://i.imgur.com/vjPzIDT.gif
http://i.imgur.com/qt1bEVi.gif

My nginx server block for koel :
http://i.imgur.com/xzSq8fC.gif

Nginx and php are working and serving my blog just fine . Any help would be really appreciated . Thanks .

Originally created by @BugMaze on GitHub (May 27, 2016). Original GitHub issue: https://github.com/koel/koel/issues/343 Hi . I'm trying to install koel on Arch and nginx/php-fpm . Everything installs fine and npm, compose and gulp all excute perfectly . I sat up a Mariadb correctly and filled up the .env with the required info . However pointing my browser to https:/MY_DOMAIN/koel returns these errors : http://i.imgur.com/vjPzIDT.gif http://i.imgur.com/qt1bEVi.gif My nginx server block for koel : http://i.imgur.com/xzSq8fC.gif Nginx and php are working and serving my blog just fine . Any help would be really appreciated . Thanks .
kerem closed this issue 2026-02-26 02:32:34 +03:00
Author
Owner

@0xcaff commented on GitHub (May 27, 2016):

It looks like laravel-elixir didn't run. cd to the directory you installed koel to and try running npm install. koel:init doesn't fail when npm does (see #336).

<!-- gh-comment-id:222204348 --> @0xcaff commented on GitHub (May 27, 2016): It looks like `laravel-elixir` didn't run. `cd` to the directory you installed koel to and try running `npm install`. `koel:init` doesn't fail when `npm` does (see #336).
Author
Owner

@BugMaze commented on GitHub (May 27, 2016):

Thanks for the reply, npm runs fine and installs lots of stuff , running it again prints these :

npm WARN lifecycle koel@~postinstall: cannot run in wd %s %s (wd=%s) koel@ cross-env NODE_ENV=production && gulp --production /srv/http/koel
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12

However it doesn't solve the issue .

<!-- gh-comment-id:222211742 --> @BugMaze commented on GitHub (May 27, 2016): Thanks for the reply, npm runs fine and installs lots of stuff , running it again prints these : ``` npm WARN lifecycle koel@~postinstall: cannot run in wd %s %s (wd=%s) koel@ cross-env NODE_ENV=production && gulp --production /srv/http/koel npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12 ``` However it doesn't solve the issue .
Author
Owner

@BernardGoldberger commented on GitHub (May 27, 2016):

What version of Koel are you running?

You can ignore the following lines as fsevents is a OS X specific package

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12

I believe your issue is similar to https://github.com/phanan/koel/issues/45, have a look.

<!-- gh-comment-id:222215963 --> @BernardGoldberger commented on GitHub (May 27, 2016): What version of Koel are you running? You can ignore the following lines as `fsevents` is a OS X specific package ``` npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12 ``` I believe your issue is similar to https://github.com/phanan/koel/issues/45, have a look.
Author
Owner

@BugMaze commented on GitHub (May 27, 2016):

@bdgold :
Thanks ! That fixed it , I was running the server as root and "npm install --unsafe-perm" fixed it .

<!-- gh-comment-id:222240856 --> @BugMaze commented on GitHub (May 27, 2016): @bdgold : Thanks ! That fixed it , I was running the server as root and "npm install --unsafe-perm" fixed it .
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/koel-koel#248
No description provided.