ruby-on-rails – nginx错误:(13:权限被拒绝)连接到上游时)
我在使用ubuntu 14.04 LTS的谷歌计算引擎VM上运行带有puma,capistrano和nginx的rails应用程序.
我在外部IP上运行nginx.当我访问它时,我在日志中得到两个nginx错误: 2016/02/03 11:58:07 [info] 19754#0: *73 client closed connection while waiting for request,client: ###.##.##.###,server: 0.0.0.0:443 2016/02/03 11:58:07 [crit] 19754#0: *74 connect() to unix:///home/my-user-name/apps/my-web-app/shared/tmp/sockets/my-web-app-puma.sock failed (13: Permission denied) while connecting to upstream,server:,request: "GET / HTTP/1.1",upstream: "http://unix:///home/my-user-name/apps/my-web-app/shared/tmp/sockets/my-web-app-puma.sock:/",host: "###.###.###.###" 注意:最后一个###.###.###.###是运行代码的google计算VM的外部IP.我相信前两个IP是我的家庭IP. 我尝试过:setsebool httpd_can_network_connect,如下所示: 我也看了(13: Permission denied) while connecting to upstream:[nginx],但它似乎特别适合uwsgi 这是我的nginx.conf upstream puma { server unix:///home/my-user-name/apps/my-web-app/shared/tmp/sockets/my-web-app-puma.sock; } server { listen 80 default_server deferred; listen 443 ssl; # server_name example.com; ssl_certificate /etc/ssl/my-web-app/my-web-app.com.chained.crt; ssl_certificate_key /etc/ssl/my-web-app/my-web-app.key; root /home/my-web-app/apps/my-web-app/current/public; access_log /home/my-user-name/apps/my-web-app/current/log/nginx.access.log; error_log /home/my-user-name/apps/my-web-app/current/log/nginx.error.log info; location ^~ /assets/ { gzip_static on; expires max; add_header Cache-Control public; } try_files $uri/index.html $uri @puma; location @puma { proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_redirect off; proxy_pass http://puma; } error_page 500 502 503 504 /500.html; client_max_body_size 10M; keepalive_timeout 10; } 我用sudo服务nginx restart运行nginx Puma starting in single mode... * Version 2.14.0 (ruby 2.1.7-p400),codename: Fuchsia Friday * Min threads: 0,max threads: 16 * Environment: production * Listening on tcp://0.0.0.0:3000 Use Ctrl-C to stop 编辑1 有人建议我在unix而不是tcp 3000上运行puma,以便它与nginx匹配 我试过通过命令在unix上运行puma: RACK_ENV=production bundle exec puma -d -b unix:///tmp/my-web-app.sock --pidfile /tmp/puma.pid 这给了: Puma starting in single mode... * Version 2.14.0 (ruby 2.1.7-p400),max threads: 16 * Environment: production * Daemonizing... 它读取上面的文本,但它不会停留,尽管最后有’…’,命令提示会立即再次发生. 这个命令似乎不起作用,所以如果有人可以建议如何在unix而不是tcp 3000上运行puma,那么我可以完成建议. (虽然我怀疑在与puma有关的任何事情之前可能会出现配置nginx问题) 编辑2附加puma.rb #!/usr/bin/env puma directory '/home/my-user-name/apps/my-web-app/current' rackup "/home/my-user-name/apps/my-web-app/current/config.ru" environment 'production' pidfile "/home/my-user-name/apps/my-web-app/shared/tmp/pids/puma.pid" state_path "/home/my-user-name/apps/my-web-app/shared/tmp/pids/puma.state" stdout_redirect '/home/my-user-name/apps/my-web-app/current/log/puma.error.log','/home/my-user-name/apps/my-web-app/current/log/puma.access.log',true threads 2,8 bind 'unix:///home/my-user-name/apps/my-web-app/shared/tmp/sockets/my-web-app-puma.sock' workers 1 preload_app! on_restart do puts 'Refreshing Gemfile' ENV["BUNDLE_GEMFILE"] = "/home/my-user-name/apps/my-web-app/current/Gemfile" end on_worker_boot do ActiveSupport.on_load(:active_record) do ActiveRecord::Base.establish_connection end end 编辑3 我现在尝试直接在端口80上运行rails服务器.我键入: => Booting Puma => Rails 4.2.4 application starting in development on http://localhost:80 => Run `rails server -h` for more startup options => Ctrl-C to shutdown server Puma 2.14.0 starting... * Min threads: 0,max threads: 16 * Environment: development * Listening on tcp://localhost:80 Exiting /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:233:in `initialize': Address already in use - bind(2) for "localhost" port 80 (Errno::EADDRINUSE) from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:233:in `new' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:233:in `add_tcp_listener' from (eval):2:in `add_tcp_listener' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/rack/handler/puma.rb:33:in `run' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/rack-1.6.4/lib/rack/server.rb:286:in `start' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/railties-4.2.4/lib/rails/commands/server.rb:80:in `start' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:80:in `block in server' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:75:in `tap' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:75:in `server' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:39:in `run_command!' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/railties-4.2.4/lib/rails/commands.rb:17:in `<top (required)>' from bin/rails:4:in `require' from bin/rails:4:in `<main>' 编辑4 如果我运行sudo服务nginx停止然后运行rvmsudo rails server -p 80再次返回: => Booting Puma => Rails 4.2.4 application starting in development on http://localhost:80 => Run `rails server -h` for more startup options => Ctrl-C to shutdown server Puma 2.14.0 starting... * Min threads: 0,max threads: 16 * Environment: development * Listening on tcp://localhost:80 这意味着方法是不正确的,因为没有nginx当我访问外部IP时它现在没有返回服务器拒绝连接.而不是原来的: We're sorry,but something went wrong. If you are the application owner check the logs for more information. 如果有人知道如何防止原始错误,任何建议将不胜感激. 编辑5 编辑6 我已经尝试直接在80上运行puma并且在80上获得了权限错误. 我尝试:RACK_ENV =生产包exec puma -p 80并得到: Puma starting in single mode... * Version 2.14.0 (ruby 2.1.7-p400),max threads: 16 * Environment: production * Listening on tcp://0.0.0.0:80 /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:233:in `initialize': Permission denied - bind(2) for "0.0.0.0" port 80 (Errno::EACCES) from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:233:in `new' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:233:in `add_tcp_listener' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:98:in `block in parse' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:84:in `each' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/binder.rb:84:in `parse' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/runner.rb:119:in `load_and_bind' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/single.rb:79:in `run' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/lib/puma/cli.rb:215:in `run' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/gems/puma-2.14.0/bin/puma:10:in `<top (required)>' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/bin/puma:23:in `load' from /home/my-user-name/apps/my-web-app/shared/bundle/ruby/2.1.0/bin/puma:23:in `<main>' 我认为这是因为端口80具有比其他端口更高的权限.所以,我运行了sudo RACK_ENV =生产包exec puma -p 80,但刚刚返回:你的Ruby版本是1.9.3,但你的Gemfile指定为2.1.7 解决方法
我和你有同样的错误,我得到了一个解决方案,但不知道它是否正确.
更改文件的第一行/etc/nginx/nginx.conf 用户www-data; 然后使用以下命令重新启动nginx: service nginx restart OR systemctl restart nginx 效果很好! (编辑:李大同) 【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容! |