What I did until now:

trace the occurance of “unretrievable_query” -> this is found mostly in I18n, but relates to http GET requests.
Since I am using nginx , I tried

1. proxy_pass_request_headers on;
   and
2. underscores_in_headers on;

This resulted in GET parameters being written to the url. But without success.
Also I tried to suppress url masking. Also without success. Signs like {[]} in the url do not change behavior.
Anyone here to provide an idea? Please?

Best,
Oliver

Hey Oliver,

You’ll receive that notification when the frontend was unable to retrieve the results to a WorkPackage query.
I’m also still wondering why that is, so could you search the production.log for requests with query_id=X ?

The upgrade process you mentioned in your first message is correct at least for the core and/or our maintained plugins.

Best,
Oliver

Hi Oliver!
Thank you so much!

Knowing how things work is just priceless.

At first I thought, that the error is raised if the backend could not parse it.

So I started navigating to the Work packages of a project and tailed the log output.
I searched for “query_id” to no avail.

Reading your information again and realizing that the frontend raises the error when no results can be retrieved, it became absolutely clear to me…

In nginx a “proxypassReverse” like in Apache does not exist.
Hence, when I forward the query to the application server, the returning headers will not be accepted by nginx.

So for future readers:

adding

proxy_pass_request_headers on;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

solved the issue.
Headers will be forwarded an retrieved by nginx like a charm! :)

Once again, thank you for that valuable piece of information. It is highly appreciated.

Best
Oliver

Hey Oliver,

great news, thanks for your thorough update. We don’t have many active nginx installations ourselves so these pieces of knowledge are very valuable.

Would you be open to write up this post as part of the installation guide (https://github.com/opf/openproject/blob/dev/doc/operation_guides/manual/installation-guide.md) to make an nginx guide more visible for others? In the main installation guide, we only have Apache2 covered at the moment.

If you have a GitHub account, you can simply edit that page in the browser and open a Pull Request for us to merge. If not, you could just send me a mail to o.guenther -at- openproject.com with some basic instructions similar to https://github.com/opf/openproject/blob/dev/doc/operation_guides/manual/installation-guide.md#serve-openproject-with-apache-and-passenger

Best,
Oliver

Hi Oliver,

I’ll make sure to go through the installation guides this weekend and open a pull request as soon as I think they’re okay.

Best,
Oliver