CODEWITHSUNDEEP
ruby-on-railsnginxpassenger
juicy
juicy

Reputation: 875

"Incomplete response received from application" from nginx / passenger

I tried to deploy my rails app on nginx and ubuntu via capistrano like the tutorial on the page https://gorails.com/deploy/ubuntu/14.04. but at the end i get an error message: 

Incomplete response received from application

in my browser. this is probably an error from passenger, but how can i figure out what to do?

Upvotes: 70

Views: 76169

Answers (10)

mohammad samiei
mohammad samiei

Reputation: 1

This error happened to me. The error that happened to me was that I had put a wrong parenthesis in the answer. I hope this is the same problem for you.:error in line 11 ')'

def department_add(request):
if request.method == 'POST':

    name = request.POST.get('departmentName')
    if  Department.objects.filter(name=name).exists():
        messages.error(request,'با این نام قبلا ثبت شده است')
    else:
        Department.objects.get_or_create(name=name)
        messages.success(request, 'واحد ایجاد شد')
    # if Department.objects.filter(name=name).exists():
    #     messages.error(request,'با این *)*نام قبلا ثبت شده است')
    return redirect('department_list')

Upvotes: 0

Andrew Koster
Andrew Koster

Reputation: 1845

I got this, only on my test server and not in production, because I was requesting a URL that didn't exist, and I guess in the test environment, Rails throws an error instead of returning a 404 response.

Upvotes: 0

fanjieqi
fanjieqi

Reputation: 572

Is there anybody like me who got this error after uploading a file?

My solution is check the name of the file which may has some special characters like `[(~.

Just remove it then upload the file again.

Good luck~

Upvotes: 0

user208769
user208769

Reputation: 2226

I had this problem over the weekend (it turned out there was an incompatibility between my versions of passenger and ruby).

However, nobody seems to be mentioning: the actual error might appear in /var/log/apache2/errors.log, not in any custom log.

Once you know that, hopefully your search will be easier!

Update, since I needed to refer back to this again - this hold true for nginx too - /var/log/nginx/error.log is your friend in that case!

Upvotes: 6

jeremywoertink
jeremywoertink

Reputation: 2341

This means that your rails app tanked before actually getting to rails itself. This could be an exception in middleware, missing ENV key, something at the OS level.

Try booting the app locally first and doing what you did to get the error in production. If everything is fine, check all of your logs. Check nginx logs, your passenger logs, and finally any other OS specific logs pertaining to booting and running your app.

Upvotes: 1

mridula
mridula

Reputation: 3281

In my case, it was because my server was running out of RAM intermittently (during PDF generation). Once the PDF was generated, some RAM was restored and the error would disappear.

I had an ubuntu server with 500M of RAM.

I added some swap space and this error disappeared.

Upvotes: 4

Ctpelnar1988
Ctpelnar1988

Reputation: 1255

For those using Passenger:

• Navigate to root of your project.

• run bundle exec rake secret RAILS_ENV=production

• Copy the output and then run sudo nano config/secrets.yml

• Under production, replace the value of the secret_key_base with the recently copied rake secret.

• press CNTRL+X, then press y, then hit enter.

• run passenger-config restart-app and select the app you wish to restart.

https://www.phusionpassenger.com/library/admin/apache/restart_app.html

Upvotes: 5

Yaniv Vova Alterman
Yaniv Vova Alterman

Reputation: 1660

Your rails_env production don't have required set up,probably missing secret_key_base.

Open /etc/nginx/sites-available/default and change the rails_env to development:

rails_env production;
        to
rails_env development;

If the app is loading it's not a passenger issue.

Production Solution:

  1. Enter your app root
  2. run: rake secret
  3. copy the output
  4. go to /yourapp/config/secrets.yml
  5. set the production secret_key_base

Restart the passenger app : 

touch /yourapp/tmp/restart.txt

Upvotes: 130

William Hu
William Hu

Reputation: 16187

Might be my answer is off topic, but when my database mysql server isn't running, i got this error too. Just in case someone has the same error.

so start/restart your database might be another answer.

Upvotes: 1

Hoa Hoang
Hoa Hoang

Reputation: 1242

This error occurs because you didn't set the secret_key_base. Follow these steps to fix it:

Go to your rails app directory

cd /path/rails-app

Generate secret key base

rake secret RAILS_ENV=production

Set environment variable

SECRET_KEY_BASE=<the-secret-key-base>

Restart the Rails app

touch /path/rails-app/tmp/restart.txt

Upvotes: 25

Related Questions