Content
OP 7 RPM install on standalone CentOS7 VM: PATCH not getting through proxy
Added by Josh Busath about 7 years ago
CentOS 7 Virtual Machine minimal install — dedicated standalone VM for OpenProject
OP 7.4.1 installed from yum RPM and configured using ‘openproject configure’ wizard — wizard autmatically installed and configured apache2, mariadb and databases, and OP backend
Stock configuration has apache web traffic for example.com/project/ (for example) proxy to the OP backend (consisting of Ruby on Rails and Unicorn) listening on 127.0.0.1:6000/project/
I am running into ’Internal Error’s when editing elements within work packages. These errors appear to be related to issues passing PUT/PATCH requests through a web proxy, which have been mentioned on these forums a few times. I am no crack sysadmin by any stretch, but as of yet I have not been able to identify any particular config setting within apache or otherwise that is restricting this traffic. I have no experience with Ruby/Rails or Unicorn up until this new install. I am under the impression that, unless explicitly restricted, apache is “supposed” to allow all methods by default.
The stock answer when this issue comes up is that one needs to allow these requests through the proxy, but there is not much in the form of suggestions on how to go about that. I understand that that can prove difficult due to differing setups for a myriad of reasons. I am puzzled that in this case this is an issue that has presented seemingly as a product of the auto-installer, and nothing else.
I can see the PATCH requests (after timing out) in the apache /access_log, as well as the error in the <log_dir>/error_log. Even while logging with the debug flag set, OP’s production log does not see the request come in.
Does anyone have any suggestions?