• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Search results

  1. S

    Resolved Postfix milter-reject after upgrade to Onyx

    I've upgraded our Plesk to 17.8 Onyx, and now customers can't send Mails through Postfix SMTP. Log: postfix/smtpd[17394]: connect from unknown[X.X.X.X] postfix/smtpd[17394]: warning: connect to Milter service inet:127.0.0.1:12768: Connection refused postfix/smtpd[17394]: NOQUEUE: milter-reject...
  2. S

    Resolved Auto-Installer won't install Plesk 12.5.30

    Thanks, this was a crystal clear case of RTFM :) Ironically, I need the 12.5 version for a hot spare instance while we upgrade our main server to ubuntu 16.04/Plesk Onyx...
  3. S

    Resolved Auto-Installer won't install Plesk 12.5.30

    I want to set up a 12.5.30 server for testing, but the installer won't let me chose to install anything prior to 17 (Onyx). I downloaded the latest autoinstaller (md5 970c6481aaf5d67591136722118ba0de) and ran it with --all-versions from cli as root (fresh Ubuntu 16.04.2), but this will only...
  4. S

    Resolved Unable to install extensions

    Installation via cli succeeded: root@mx01:/tmp# md5sum migrator.zip 20d9fee96872707a504932a0a5812639 migrator.zip root@mx01:/tmp# plesk bin extension -i migrator.zip File `meta.xml` contains an error Error 1871: Element 'category': This element is not expected. (Line: 6) (Column: 0)...
  5. S

    Resolved Unable to install extensions

    I've got a problem with my Plesk installation, the extensions installer won't work, both when uploading a zip and installing through the catalog browser in Plesk itself. After clicking install, the page just loads and will eventually fail with 504 Gateway Time-out. Product version: 12.5.30...
  6. S

    Resolved Debugging "Premature end of script headers"

    Hey, Their sites were hacked (probably through old WP and/or plugins). Fulll disclosure for anyone experiencing bad performance / weird PHP errors on all of one customer's domains: I searched the logs for the first appearance of the error, which was Aug 9 9:37 As UFHH01 kindly told me, the...
  7. S

    Resolved Debugging "Premature end of script headers"

    Thanks, that's all I wanted to hear (/read). I was actually in the middle to write a close-up for this thread, as the problem was resolved. See my next post for more information ;) Thanks for your support!
  8. S

    Resolved Debugging "Premature end of script headers"

    Thanks for your answer! Indeed, I just wanted to make sure the problem is(n't) caused by the server system (CPU/MEM limit by plesk, wrong config...). Just to be on the safe side: Can a WP update really cause this intermittent behavior? The errors are on every page delivered. But only some...
  9. S

    Resolved Debugging "Premature end of script headers"

    New Theory: That 1 affected client runs WordPress. 1st Appearance of the error is [Tue Aug 09 09:39:47 2016]. Apparently, 3 hours before plesk-wp-cli was updated: 2016-08-09 06:29:42 status installed plesk-wp-cli 0.24.0-ubuntu12.04.16080218 There were requests to the blog inbetween wp upgrade...
  10. S

    Resolved Debugging "Premature end of script headers"

    Hey everyone, I experience weird behavior on the domains of 1 customer I have in my Plesk Panel. Generally, sites take a tad long to load. >5 Seconds for a Wordpress index. But occasionally, ony 500 Server Error is returned. The Apache error log contains this: [warn] mod_fcgid: read data...
View older results
Back
Top