-
-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] EACCES: permission denied, mkdir '/etc/.pm2/logs' #367
Comments
You may want to run it as root or see this fix: Unitech/pm2#487 |
I got the same issue and I solved it by specifying the forge directory to an actual site directory. |
Hi Christoph, thanks for your update. I got a question about that: What do you mean with "specifying the forge director to an actual site directory"? The "forge directory" should be So did you set the working directory in Laravel Forge to |
I run soketi on the same server as my project, so maybe this doesn't work for you but since soketi is global it can run from all the directories, but it seems that somehow subdirectories from 'sites' have different permissions. so for example I have a site: 'example.com', i run this command only for the directory '/home/forge/example.com' . That fixed it for me, but changing it to the 'root' user instead of forge also works! |
Try this
|
Running as root is BAD security practice. This issue is not a soketi problem, more a pm2 problem. I use supervisord to monitor and control the soketi processes. To fix the issue with supervisord, you should add the following to you supervisord config:
In this case I created a user called "soketi" with nologin and with a home directory. Edit: Correct me if I am wrong, but you should be able to add the envoirment path in front of the command like:
|
Gonna close this up. @Diz-X's solution is working to me too. |
Thanks @Diz-X's, I finally solved my problem. Note for others: if you do not get rid of this errors Soketi can work unstable. From time-to-time my events haven't been received by frontend thought it was sent from backend. I didn't understand why it happening until fixed this issues |
Hello,
I got a little problem using soketi on Laravel Forge.
I followed this article (https://blog.laravel.com/deploying-soketi-to-laravel-forge) to configure a daemon that makes sure that soketi is always up and running.
This is the resulting daemon:
And this is the generated supervisord-config:
Now I am getting this error on startup:
Any help or hint is highly appreciated :-)
The text was updated successfully, but these errors were encountered: