Home / user-232531

onnimonni's questions

Martin Hope
Onni Hakala
Asked: 2024-09-20 02:22:07 +0800 CST
  • 6

Now that Zstd is slowly getting support in the browsers I'm wondering if I could keep my Zstd compression and forwarding the files as is with ZFS.

Currently as far as I know ZFS implicitly decompresses the Zstd compressed files before my web server can handle them and the web server needs to again compress them before sending them to users.

Is there a way to pass these files directly to the web server without the back and forth compression?

I'm most likely going to use nginx or caddy to serve these files but I'm interested if there's a way to access the compressed versions of the files in any software running on linux eg python or nodejs or ruby or php.

zfs
Martin Hope
onnimonni
Asked: 2014-07-13 14:13:48 +0800 CST
  • 0

I have few vps machines with private networking. I'm using nginx in all of them to proxy pass pass requests into fourth machine (10.129.xxx.xxx) which is only listens private connections.

I just changed the server_name:s from this config but otherwise they are identical:

upstream panel { server 10.129.xxx.xxx:8000; }
server {
  listen      80;
  server_name *.example.com example.com;
  return 301 https://$host$request_uri;
}

server {
  listen      443;
  server_name *.example.com example.com;

  ssl on;
  ssl_certificate     /etc/private/ssl/server.crt;
  ssl_certificate_key /etc/private/ssl/server.key;
  ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-RC4-SHA:ECDHE-RSA-AES128-SHA:AES128-GCM-SHA256:RC4:HIGH:!MD5:!aNULL:!EDH:!CAMELLIA;
  ssl_protocols TLSv1.2 TLSv1.1 TLSv1;
  ssl_prefer_server_ciphers on;

  location / {
    proxy_pass  http://panel;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_set_header Host $http_host;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Forwarded-For $remote_addr;
    proxy_set_header X-Forwarded-Port $server_port;
    proxy_set_header X-Request-Start $msec;
  }
}

This setting works in 2 machines but third one is only giving 502 with nginx error log:

[error] 31890#0: *27 connect() failed (111: Connection refused) while connecting to upstream, client: 123.456.70.80, server: *.example.com, request: "GET / HTTP/1.1", upstream: "http://10.129.xxx.xx:8000/error/50x.html", host: "example.com"

What nginx rules might cause this? Firewall? Where should I be looking for this error? Server with errors has vestacp-panel and apache installed (port 8080) and other servers don't have.

networking