• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Varnish for HTTPS WordPress site in a Docker container

Pheonix Support

New Pleskian
Hello,

We've been mulling around issues while trying to setup varnish for https wordpress site in a docker container.

We've followed the link - https://www.plesk.com/blog/product-technology/varnish-wordpress-docker-container/

This article perfectly works with HTTP but not HTTPS. We always get "too many redirects or redirect loop error" once we enable ssl.

Anyone has successfully implemented varnish for HTTPS websites along with plesk,wordpress,docker,nginx ?

Thanks in advance
 
Hi,
Make sure that Wordpress is not redirecting to HTTPS, all communication through varnish is HTTP. All links in wordpres should be HTTPS (images, CSS, etc), otherwise you get mixed content which in Google Chrome is blocked.

We had a custom config in NGinx to redirect all HTTP traffic to HTTPS:
if ($scheme = "http") {
return 301 https://WEBSITE.COM$request_uri;
}

I know it is not the best solution, but we could not find a better one. The option "Permanent SEO-safe 301 redirect from HTTP to HTTPS" also creates a redirect for Apache wich creates the infinite redirect loop.

The current problem we face is that Docker is not stable, we suffered 2 times problems with Docker and we needed to click on recreate Docker image to make it work again. We did not find a way to get a fresh image running every morning.
 
Back
Top