• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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