当使用独角兽启动rails时,Nginx失败(13:权限被拒绝)

时间:2015-08-03 15:50:37

标签: nginx unicorn

我的rails应用程序在UnicornNginx的服务器上运行,但在配置Nginx并启动它后,我收到错误:

2015/08/03 15:43:44 [crit] 13951#0: *1 stat() "/home/ec2-user/apps/mybest/current/public//index.html" failed (13: Permission denied), client: 123.185.144.80, server: 52.74.148.194, request: "GET / HTTP/1.1", host: "52.74.148.194"
2015/08/03 15:43:44 [crit] 13951#0: *1 stat() "/home/ec2-user/apps/mybest/current/public/.html" failed (13: Permission denied), client: 123.185.144.80, server: 52.74.148.194, request: "GET / HTTP/1.1", host: "52.74.148.194"
2015/08/03 15:43:44 [crit] 13951#0: *1 stat() "/home/ec2-user/apps/mybest/current/public/" failed (13: Permission denied), client: 123.185.144.80, server: 52.74.148.194, request: "GET / HTTP/1.1", host: "52.74.148.194"

这里是nginx_myapp.conf

upstream unicorn {
  server unix:/tmp/unicorn.myapp.sock fail_timeout=0;
}

server {
  listen 80 default deferred;
  server_name 52.74.148.194;

 root /home/ec2-user/apps/mybest/current/public;
 location ^~ /assets/ {
    gzip_static on;
    expires max;
    add_header Cache-Control public;
  }
try_files $uri/index.html $uri.html $uri @unicorn;
  location @unicorn {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $http_host;
    proxy_redirect off;
    proxy_pass http://unicorn;
  }

  error_page 500 502 503 504 /500.html;
  keepalive_timeout 10;
}
我用谷歌搜索了几个小时但仍然无法解决这个问题。我猜是否有任何路径拼写错误,并且不确定为什么错误消息带有“public//index.html”,而不是“public/index.html”任何提示?谢谢!

Nginx与用户“nginx”一起运行,如下所示:

修改

$ groups nginx
nginx : nginx ec2-user
groups ec2-user
ec2-user : ec2-user wheel

路径权限:(当前)

current]$ ls -l
total 76
drwxrwxr-x 8 ec2-user ec2-user 4096 Aug  3 14:06 app
drwxrwxr-x 2 ec2-user ec2-user 4096 Aug  3 14:08 assets_manifest_backup
drwxrwxr-x 2 ec2-user ec2-user 4096 Aug  3 14:26 bin
-rw-rw-r-- 1 ec2-user ec2-user  830 Aug  3 14:06 Capfile
drwxrwxr-x 6 ec2-user ec2-user 4096 Aug  3 14:08 config
-rw-rw-r-- 1 ec2-user ec2-user  153 Aug  3 14:06 config.ru
drwxrwxr-x 2 ec2-user ec2-user 4096 Aug  3 14:08 db
-rw-rw-r-- 1 ec2-user ec2-user 1720 Aug  3 14:06 Gemfile
-rw-rw-r-- 1 ec2-user ec2-user 5262 Aug  3 14:06 Gemfile.lock
drwxrwxr-x 4 ec2-user ec2-user 4096 Aug  3 14:06 lib
drwxrwxr-x 2 ec2-user ec2-user 4096 Aug  3 14:35 log
drwxrwxr-x 2 ec2-user ec2-user 4096 Aug  3 14:08 public
-rw-rw-r-- 1 ec2-user ec2-user  249 Aug  3 14:06 Rakefile
-rw-rw-r-- 1 ec2-user ec2-user  478 Aug  3 14:06 README.rdoc
-rw-rw-r-- 1 ec2-user ec2-user    8 Aug  3 14:07 REVISION
drwxrwxr-x 8 ec2-user ec2-user 4096 Aug  3 14:06 test
drwxrwxr-x 4 ec2-user ec2-user 4096 Aug  3 14:35 tmp
drwxrwxr-x 3 ec2-user ec2-user 4096 Aug  3 14:06 vendor

公开:(我甚至改为777)

ls -l
total 16
-rwxrwxrwx 1 ec2-user ec2-user 1564 Aug  3 14:06 404.html
-rwxrwxrwx 1 ec2-user ec2-user 1547 Aug  3 14:06 422.html
-rwxrwxrwx 1 ec2-user ec2-user 1477 Aug  3 14:06 500.html
lrwxrwxrwx 1 ec2-user ec2-user   47 Aug  3 14:08 assets -> /home/ec2-user/apps/mybest/shared/public/assets
-rwxrwxrwx 1 ec2-user ec2-user    0 Aug  3 14:06 favicon.ico
-rwxrwxrwx 1 ec2-user ec2-user  202 Aug  3 14:06 robots.txt

将nginx.conf中的nginx用户从'nginx'更改为'ec2-user'解决它。

1 个答案:

答案 0 :(得分:0)

确保nginx在正确的用户(主nginx配置文件中的user ...指令)下运行,然后确保该用户可以访问/home/ec2-user/apps/mybest/current/public/*个文件(即它们属于同一个组)作为用户,并具有读取权限。)

您还需要在路径上的每个目录上拥有+ x权限。您可以在终端中看到ls -l的权限,如果缺少,则可以执行类似的操作:

chmod g+x apps
cd apps
chmod g+x mybest
cd mybest
chmod g+x current
cd current
chmod g+x public
cd public
chmod g+r *

<强> UPD 即可。正如在评论中发现的那样,nginx在ec2-user用户名(user ec2-user中的配置)下正常运行。对于/home和/或/home/ec2-user,很可能存在限制性权限(对于目录组没有“+ x”/“+ r”)。就个人而言,我认为在ec2-user用户名下运行nginx并没有错。或者您可以将您的Rails应用程序移动到/var/www/my_app,为nginx用户设置权限,并让它从那里运行。