Apache with ProxyPass and Websockets

Community Support
2

Ohhhh! Now I get it.

Hestia also adds an Nginx in front of the Apache. I wasn’t aware of that.

And the Nginx doesn’t properly forward the websocket.

I’ve added another nginx template and configured the / location like this:

location / {
                proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto  $scheme;
                proxy_set_header Host               $http_host;

                proxy_set_header Upgrade            $http_upgrade;
                proxy_set_header Connection         "upgrade";

                proxy_http_version                  1.1;

                proxy_pass https://%ip%:%web_ssl_port%;

Now it apparently forwards the request to apache, but together with my configuration about, I get an 101 status code back now, which doesn’t seem to be correct either.

Does somebody know how to fix this as well?

OR: Is it possible to deactivate the Nginx and just use Apache in Hestia?

1 Like