New answers tagged

0

You can set up IP whitelisting for Magento 2 admin area using NGINX by allocating a separate location, and unconditionally route requests through index.php. Citing the article linked: location ~ "^/admin_" { allow 1.2.3.4; allow 1.2.3.5; allow 1.2.3.6; deny all; fastcgi_pass unix:/var/run/php-fpm/example.com.sock; ...


0

X-Magento-Debug is from varnish.. If you read the vcl file, you'll see X-Magento-Debug there.. it will change to X-Magento-Cache-Debug once you're in production mode


0

The problem was when using the Magento\Framework\App\State class in our Console Command (as well as any other classes that might change or load global state) in your module Console Commands. When Magento build a list of available console commands it creates instances for all command classes so all of their dependencies as well. As a workaround you may pass ...


0

Got into contact with Magento Cloud Support about this. Magento Cloud Support Response You should not need to configure http-cache-hosts with the Advanced Fastly settings. The Fastly settings will generate the needed VCL for you, so it should only be necessary to upload the VCL snippet from the admin to configure Fastly Purging. So it appears that the ...


1

What the source code says If we look at the error, we can see that an assert error is triggered in cache/cache_esi_parse.c on line `1039. A little bit of context: this is the place where ESI tags get parsed and where the corresponding ESI endpoints are called. According to the source code on https://github.com/varnishcache/varnish-cache/blob/4.0/bin/varnishd/...


0

There is a bug report here which seems to be closed at the moment: https://github.com/magento/magento2/issues/5980 I agree with @moonhawk comment that cloudflare won't be the problem. Instead, you might be experiencing that github issue as many other people (including me).


1

The problem you're probably experiencing is the fact that Magento thinks you're connecting through using regular HTTP request, despite the fact that you terminated your TLS connection in Nginx. Varnish Cache doesn't handle TLS natively, but facilitates it Varnish Cache, the open source version of Varnish, doesn't support native TLS. This means TLS has to be ...


Top 50 recent answers are included