#1095736 ruby-rails: upgrade results in "502 Bad Gateway" with nginx proxy

#1095736#5
Date:
2025-02-11 11:15:13 UTC
From:
To:
Hi Lucas,

with this version I was able to upgrade my nginx - redmine - rails
installation:

# aptitude -t sid install  '~Uruby~V6\.1\.7'
The following NEW packages will be installed:
   ruby-rack-session{a}
The following packages will be upgraded:
   ruby-actioncable ruby-actionmailbox ruby-actionmailer ruby-actionpack
   ruby-actiontext ruby-actionview ruby-activejob ruby-activemodel
   ruby-activerecord ruby-activestorage ruby-activesupport ruby-rack
   ruby-rails ruby-railties

This installs ruby-rack in version 3.0.8-4 and ruby-rack-session in
version 2.0.0-3.

But when calling my redmine website, I get an "502 Bad Gateway" error
from nginx. The nginx error log says

2025/02/11 11:33:52 [error] 1367#1367: *5 upstream sent duplicate header line:
"content-length: 648", previous value: "Content-Length: 648" while reading
response header from upstream, client: 91.5.102.159, server: _, request: "GET
/redmine HTTP/2.0", upstream:
"http://unix:/run/www/unicorn-redmine-default.sock:/redmine", host:
"skuld.sytes.net"

Downgrading to version 6.1.7.3+dfsg-7 and ruby-rack back to 2.2.7-1.1,
also removing ruby-rack-session makes the redmine website work again.

Any ideas?

Regards,
Jörg.

#1095736#10
Date:
2025-02-11 12:00:58 UTC
From:
To:
Hi Lucas again,

my description of the configuration wasn't complete. I use unicorn
(6.1.0+git.20250131.1370f52-1) as rack-rails server for redmine. That is: nginx
- unicorn - redmine.

And I'm a little bit unsure if the problem is not due to the newer ruby-rack
version.

Regards,
Jörg.

#1095736#15
Date:
2025-02-11 15:12:24 UTC
From:
To:
Here is attached also the error log of unicorn.

Regards,
Jörg.