nginx : 502 사이트 리디렉션 중에 잘못된 게이트웨이 오류가 발생했습니다.

저는 Nginx를 처음 사용하며 nginx와 thin을 사용하려고했습니다.nginx : 502 사이트 리디렉션 중에 잘못된 게이트웨이 오류가 발생했습니다.

나는 많은 사이트와 블로그를 시도했지만 그것은 helping.I 현재 블로그 http://articles.slicehost.com/2008/5/27/ubuntu-hardy-nginx-rails-and-thin

내가 그러나 502 잘못된 게이트웨이 오류가 발생하고 다음입니다하지 않습니다.

아래 코드는 구현 한 코드입니다.

의 nginx의 conf 파일 : -

user www-data; 
worker_processes 4; 
pid /var/run/nginx.pid; 

events { 
    worker_connections 768; 
    # multi_accept on; 
} 

http { 

    ## 
    # Basic Settings 
    ## 

    sendfile on; 
    tcp_nopush on; 
    tcp_nodelay on; 
    keepalive_timeout 65; 
    types_hash_max_size 2048; 
    # server_tokens off; 

    # server_names_hash_bucket_size 64; 
    # server_name_in_redirect off; 

    include /etc/nginx/mime.types; 
    default_type application/octet-stream; 

    ## 
    # Logging Settings 
    ## 

    access_log /var/log/nginx/access.log; 
    error_log /var/log/nginx/error.log; 

    ## 
    # Gzip Settings 
    ## 

    gzip on; 
    gzip_disable "msie6"; 

    # gzip_vary on; 
    # gzip_proxied any; 
    # gzip_comp_level 6; 
    # gzip_buffers 16 8k; 
    # gzip_http_version 1.1; 
    # gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript; 

    ## 
    # nginx-naxsi config 
    ## 
    # Uncomment it if you installed nginx-naxsi 
    ## 

    #include /etc/nginx/naxsi_core.rules; 

    ## 
    # nginx-passenger config 
    ## 
    # Uncomment it if you installed nginx-passenger 
    ## 

    #passenger_root /usr; 
    #passenger_ruby /usr/bin/ruby; 

    ## 
    # Virtual Host Configs 
    ## 

    include /etc/nginx/conf.d/*.conf; 
    include /etc/nginx/sites-enabled/*; 

} 

#mail { 
# # See sample authentication script at: 
# # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript 
# 
# # auth_http localhost/auth.php; 
# # pop3_capabilities "TOP" "USER"; 
# # imap_capabilities "IMAP4rev1" "UIDPLUS"; 
# 
# server { 
#  listen  localhost:110; 
#  protocol pop3; 
#  proxy  on; 
# } 
# 
# server { 
#  listen  localhost:143; 
#  protocol imap; 
#  proxy  on; 
# } 
#}

의 nginx 기본 파일 (은/etc/nginx를/사이트 가능) : -

# You may add here your 
# server { 
# ... 
# } 
# statements for each of your virtual hosts to this file 

## 
# You should look at the following URL's in order to grasp a solid understanding 
# of Nginx configuration files in order to fully unleash the power of Nginx. 
# http://wiki.nginx.org/Pitfalls 
# http://wiki.nginx.org/QuickStart 
# http://wiki.nginx.org/Configuration 
# 
# Generally, you will want to move this file somewhere, and start with a clean 
# file but keep this around for reference. Or just disable in sites-enabled. 
# 
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples. 
## 

server { 
    listen 80; ## listen for ipv4; this line is default and implied 
    #listen [::]:80 default ipv6only=on; ## listen for ipv6 
     server_name 192.168.1.238:8080; 


    root /home/woi/Development/public; 
    index index.html index.htm; 

    # Make site accessible from http://localhost/ 
    # server_name localhost; 

    location/{ 
     # First attempt to serve request as file, then 
     # as directory, then fall back to index.html 
     try_files $uri $uri/ /index.html; 
     # Uncomment to enable naxsi on this location 
     # include /etc/nginx/naxsi.rules 
    } 

    location /doc/ { 
     alias /usr/share/doc/; 
     autoindex on; 
     allow 127.0.0.1; 
     deny all; 
    } 

    # Only for nginx-naxsi : process denied requests 
    #location /RequestDenied { 
     # For example, return an error code 
     #return 418; 
    #} 

    #error_page 404 /404.html; 

    # redirect server error pages to the static page /50x.html 
    # 
    #error_page 500 502 503 504 /50x.html; 
    #location = /50x.html { 
    # root /usr/share/nginx/www; 
    #} 

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000 
    # 
    #location ~ \.php$ { 
    # fastcgi_split_path_info ^(.+\.php)(/.+)$; 
    # # NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini 
    # 
    # # With php5-cgi alone: 
    # fastcgi_pass 127.0.0.1:9000; 
    # # With php5-fpm: 
    # fastcgi_pass unix:/var/run/php5-fpm.sock; 
    # fastcgi_index index.php; 
    # include fastcgi_params; 
    #} 

    # deny access to .htaccess files, if Apache's document root 
    # concurs with nginx's one 
    # 
    #location ~ /\.ht { 
    # deny all; 
    #} 
} 


# another virtual host using mix of IP-, name-, and port-based configuration 
# 
#server { 
# listen 8000; 
# listen somename:8080; 
# server_name somename alias another.alias; 
# root html; 
# index index.html index.htm; 
# 
# location/{ 
#  try_files $uri $uri/ /index.html; 
# } 
#} 


# HTTPS server 
# 
#server { 
# listen 443; 
# server_name localhost; 
# 
# root html; 
# index index.html index.htm; 
# 
# ssl on; 
# ssl_certificate cert.pem; 
# ssl_certificate_key cert.key; 
# 
# ssl_session_timeout 5m; 
# 
# ssl_protocols SSLv3 TLSv1; 
# ssl_ciphers ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv3:+EXP; 
# ssl_prefer_server_ciphers on; 
# 
# location/{ 
#  try_files $uri $uri/ /index.html; 
# } 
#}

의 nginx의 domain.com 파일 (은/etc/nginx를/사이트 -available) : - 502 나쁜 게이트를 얻고있다

는

upstream domain1 { 
     server 127.0.0.1:3000; 
     server 127.0.0.1:3001; 
     server 127.0.0.1:3002; 
    } 




server { 
      listen 80; 
      server_name 192.168.1.238; 

     # access_log /home/demo/public_html/railsapp/log/access.log; 
     # error_log /home/demo/public_html/railsapp/log/error.log; 

      root /home/woi/Development/public/; 
      index index.html; 

      location/{ 
          proxy_set_header X-Real-IP $remote_addr; 
          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
          proxy_set_header Host $http_host; 
          proxy_redirect off; 

          if (-f $request_filename/index.html) { 
              rewrite (.*) $1/index.html break; 
          } 

          if (-f $request_filename.html) { 
              rewrite (.*) $1.html break; 
          } 

          if (!-f $request_filename) { 
              proxy_pass http://domain1; 
              break; 
          } 
      } 

}

services nginx start 명령을 넣어 후, 나는 얇은 server.I를 실행할 수 없습니다입니다 192.168.1.238 내 IP 주소를 때 길을 잘못.

업데이트 : 년 - 아래에있는 내 오류 로그의 조각입니다 : -

"GET/HTTP/1.1", upstream: "http://domain1/", host: "192.168.1.238" 
2014/01/30 05:14:18 [error] 2029#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://127.0.0.1:3002/", host: "192.168.1.238" 
2014/01/30 05:14:18 [error] 2029#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "192.168.1.238" 
2014/01/30 05:14:18 [error] 2029#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://127.0.0.1:3001/", host: "192.168.1.238" 
2014/01/30 05:14:18 [error] 2029#0: *1 no live upstreams while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://domain1/", host: "192.168.1.238" 
2014/01/30 05:14:18 [error] 2029#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://127.0.0.1:3002/", host: "192.168.1.238" 
2014/01/30 05:14:18 [error] 2029#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "192.168.1.238" 
2014/01/30 05:14:18 [error] 2029#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://127.0.0.1:3001/", host: "192.168.1.238" 
2014/01/30 05:14:18 [error] 2029#0: *1 no live upstreams while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://domain1/", host: "192.168.1.238" 
2014/01/30 05:16:24 [error] 2171#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://127.0.0.1:3002/", host: "192.168.1.238" 
2014/01/30 05:16:24 [error] 2171#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "192.168.1.238" 
2014/01/30 05:16:24 [error] 2171#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://127.0.0.1:3001/", host: "192.168.1.238" 
2014/01/30 05:20:04 [error] 2354#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://127.0.0.1:3002/", host: "192.168.1.238" 
2014/01/30 05:20:04 [error] 2354#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "192.168.1.238" 
2014/01/30 05:20:04 [error] 2354#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://127.0.0.1:3001/", host: "192.168.1.238" 
2014/01/30 05:20:09 [error] 2354#0: *1 no live upstreams while connecting to upstream, client: 192.168.1.142, server: 192.168.1.238, request: "GET/HTTP/1.1", upstream: "http://domain1/", host: "192.168.1.238"

위의 솔루션은 도움이되지 실례합니다 누군가가 저를 도와주세요가. 오랫동안 오래되었습니다.

감사합니다.

출처

2014-01-30 Sanjay Salunkhe

로그에 어떤 오류가 있습니까? – Danack

@Danack 업데이트 된 질문 –

연결이 거부되었습니다. 업스트림에 연결하는 동안 ... "http://127.0.0.1:3002/"NGINX와 마찬가지로 거의 모든 요청을 처리하기 위해 UPSTREAM에 연결할 수 없습니다. – Danack

이것은 씬 서버가 실행 중이 아님을 의미합니다. 시도해보십시오.

 
curl -v http://localhost:3000

아마도 작동하지 않을 수 있습니다. 추가 문제점을 식별하려면 Thin 로그 (stdout/stderr.log)를보십시오.

씬은 별도의 프로세스이므로 개별적으로 다시 시작해야합니다. 동일한 번들의 Rails 앱 내에 설정하는 것이 일반적입니다. 이 경우 당신처럼 실행해야합니다

 
bundle exec thin start

참조 : 당신이 얇은 보석을 포함한 루트로 당신의 보석을 설치 한 경우, 다음이의/etc/초기화에 init 스크립트를 설치해야 http://code.macournoyer.com/thin/usage/

. 디. 이 경우 서비스 명령으로 thin을 다시 시작할 수 있습니다.

새 코드를 배포 할 때 nginx가 아닌 씬 서버 만 다시 시작하면됩니다.

출처

2014-01-30 23:54:42 Arya

내가 nginx를 시작하면 내 씬 서버가 자동으로 시작한다는 것을 의미합니까? 아니면 "씬 시작"명령을 사용하여 씬 서버를 명시 적으로 시작해야합니까? –

내 대답을 수정했습니다. – Arya

nginx : 502 사이트 리디렉션 중에 잘못된 게이트웨이 오류가 발생했습니다.

답변

관련 문제