• 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.

Resolved upstream sent invalid "Content-Length" header

Java2107

New Pleskian
Server operating system version
Debian 11.7
Plesk version and microupdate number
Plesk Obsidian Version 18.0.55 Update #1
Hello,

Last night it appears my Plesk installation has updated, and at the same time rendered a PHP script on one of my sites useless. Before images would load through the image proxy, however this is not the case anymore and I am presented with a bad gateway message along with "upstream sent invalid "Content-Length" header" contained within the logs for that specific website.

I've tried working around this to no avail and my site remains unusable. Any help is appreciated.

Regards.
 
I've managed to fix the issue which was caused by an improper header sent by the script, it looks like NGINX didn't take issue with this until recently hence the issues, but all is good now. This post can be locked.
 
Back
Top