The first is a warning, and it tells you how to suppress it.
The second implies that you need to remove the pidfile before you can
restart httpd, so do that.
On Sun, Dec 25, 2022 at 3:10 PM Jeffrey Denison
wrote:
> @vicky chb
> I changed ssl.conf but don't know how to replace the
>
> As far as I understood, the "P" flag implies "L"
True, so that part of the docs seems redundant
> Reading through the report, this bug probably hit me, too. GitLab is a Ruby-
on-rails application using a Puma Webserver internally, connected to Apache
all over UNIX-sockets; this cable-stuff
Am Dienstag, 27. Dezember 2022, 20:32:28 CET schrieb Florian Schwalm:
> As far as I understand Gitlab sends a HTTP GET request first to ask the
> backend to upgrade to websockets. By always proxying /-/cable to ws right
> away you prevent that first upgrade request from succeeding which is
>
As far as I understand Gitlab sends a HTTP GET request first to ask the backend
to upgrade to websockets. By always proxying /-/cable to ws right away you
prevent that first upgrade request from succeeding which is probably where the
new error message originates. That's why the
Hi,
Am Sonntag, 25. Dezember 2022, 10:56:07 CET schrieb Florian Schwalm:
> Specifying ws instead of http in the RewriteRule should be good.
thanks for the reply! I did that, that's how I got the log error. At first,
the wstunnel-module was not installed; but installing (and loading) it did not