No such file or directory: '/etc/nginx/common/redis.conf'

I used command:

sudo ee site create --wpredis

and I got:

[Errno 2] No such file or directory: ‘/etc/nginx/common/redis.conf’


All other stacks are OK, what can I do in this situation? Thanks for help.

Hello asatoma

Could you please tell which Easyengine version you are using right now ?

sudo ee -v

Also please check if /etc/nginx/common/ folder exist .

In the meantime i could suggest you to purge nginx and reinstall nginx on your workspace .

sudo ee stack purge nginx

sudo ee stack install nginx

I had the same error message about missing the common directory and the conf.d directory. I just added both and it installed just fine.

I hate to revive a dead post, but I just experienced this error again today.

OS: Ubuntu 18.04.1 LTS EasyEngine v3.8.1

No “common” folder exists in /etc/nginx

If someone knows what permissions should be granted on the /etc/nginx/common directory, could you share them please? Otherwise I can pull it from another VPS.

I created the “common” folder/directory and proceeded with the installation. The site creation completed, up to the point where NGINX needed to reload, and then it came to a screeching halt, with the following errors/debug info:

 2018-10-16 12:27:54,096 (INFO) ee : Reload : nginx     
 2018-10-16 12:27:54,126 (DEBUG) ee : nginx: [emerg] open() "/etc/nginx/common/acl.conf" failed (2: No such file or directory) in /etc/nginx/common/locations-php7.conf:47
 nginx: configuration file /etc/nginx/nginx.conf test failed
 2018-10-16 12:27:54,126 (INFO) ee : [Failed]
 2018-10-16 12:27:54,126 (INFO) ee : Oops Something went wrong !!
 2018-10-16 12:27:54,127 (INFO) ee : Calling cleanup actions ...

…and then the script goes into removal mode; removing the website I just tried to create.

At this point I uninstalled NGINX using:

 sudo ee stack purge --nginx

…and then re-installed it using:

 sudo ee stack install --nginx

…and finally created a website using:

 ee site create

This time, the creation of the website went as it should have.

Same issue occurred on a completely different deployment today.

Is there any way to get this fixed within EE?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.