Comments on: Set up Magento 2 with Redis, Varnish and Nginx as SSL termination

By: admin

admin — Fri, 29 Mar 2019 17:52:26 +0000

In reply to faruk. Did you try to increase the values as suggested in the output?

By: faruk

faruk — Thu, 28 Mar 2019 07:48:49 +0000

Hi;
Help me pls,
nginx: [warn] could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

nginx version: nginx/1.14.0 (Ubuntu)
built with OpenSSL 1.1.0g 2 Nov 2017
TLS SNI support enabled
configure arguments: –with-cc-opt=’-g -O2 -fdebug-prefix-map=/build/nginx-FIJPpj/nginx-1.14.0=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2′ –with-ld-opt=’-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -fPIC’ –prefix=/usr/share/nginx –conf-path=/etc/nginx/nginx.conf –http-log-path=/var/log/nginx/access.log –error-log-path=/var/log/nginx/error.log –lock-path=/var/lock/nginx.lock –pid-path=/run/nginx.pid –modules-path=/usr/lib/nginx/modules –http-client-body-temp-path=/var/lib/nginx/body –http-fastcgi-temp-path=/var/lib/nginx/fastcgi –http-proxy-temp-path=/var/lib/nginx/proxy –http-scgi-temp-path=/var/lib/nginx/scgi –http-uwsgi-temp-path=/var/lib/nginx/uwsgi –with-debug –with-pcre-jit –with-http_ssl_module –with-http_stub_status_module –with-http_realip_module –with-http_auth_request_module –with-http_v2_module –with-http_dav_module –with-http_slice_module –with-threads –with-http_addition_module –with-http_geoip_module=dynamic –with-http_gunzip_module –with-http_gzip_static_module –with-http_image_filter_module=dynamic –with-http_sub_module –with-http_xslt_module=dynamic –with-stream=dynamic –with-stream_ssl_module –with-mail=dynamic –with-mail_ssl_module

/etc/nginx/nginx.conf added
server_names_hash_bucket_size 64;
server_names_hash_max_size 512;
subrequest_output_buffer_size 8k;
variables_hash_max_size 1024;
variables_hash_bucket_size 64;

service nginx reload

but, return this issue nginx: [warn] could not build optimal proxy_headers_hash, you should increase either proxy_headers_hash_max_size: 512 or proxy_headers_hash_bucket_size: 64; ignoring proxy_headers_hash_bucket_size

By: Jeroen

Jeroen — Fri, 27 Apr 2018 16:59:04 +0000

503 fix: https://github.com/magento/magento2/issues/10165#issuecomment-340121586

By: admin

admin — Thu, 22 Mar 2018 11:34:56 +0000

In reply to Matt. You can edit the daemon_opts in /etc/default/varnish too. Thanks.

By: Matt

Matt — Wed, 21 Mar 2018 21:40:02 +0000

In reply to admin. What's the rational behind the customexec config vs just changing the /etc/default/varnish daemon_opts?

By: Matthew Lenz

Matthew Lenz — Tue, 13 Mar 2018 12:04:58 +0000

We had issues with redirect loops. Disabling http2 in the server block(s) fixed the issue.

By: dgranville

dgranville — Thu, 01 Feb 2018 01:01:37 +0000

One of my clients followed this blog post and got the same “Error 503 Backend fetch failed” error, so he retained me to resolve it. After some troubleshooting, I found that the varnish.vcl file generated by magento configures a health check for /pub/health_check.php, but the nginx config file on this blog and in /var/www/myMagentoSite.com/nginx.conf.sample denied access to that script. Because of this, varnish thought the origin server was down and thus wouldn’t fetch content from it. The solution was to adjust the nginx config files to allow for varnish to perform the health check.

By: admin

admin — Thu, 04 Jan 2018 09:18:26 +0000

In reply to Prasoon. You can check the official magento documentation about how to set up multiple websites or stores with nginx: http://devdocs.magento.com/guides/v2.2/config-guide/multi-site/ms_nginx.html