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

upstream

  1. V

    Issue upstream timed out (110: Connection timed out) while reading response header from upstream

    Hi, Im new to plesk and usgin it on linode. We have a website developed in ReactJS, NodeJS and mongo db. Attached is the log on Nginx error. My Nginx config file: /etc/nginx/nginx.conf #user nginx; worker_processes 1; #error_log /var/log/nginx/error.log; #error_log...
  2. M

    Issue FastCGI errors in /var/log/sw-cp-server/error_log [error] 9941#0

    CentOs 6.10 Obsidian 18.0.31 Error: [error] 9941#0: *3190655 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: , request: "POST /modules/monitoring/public/index.php/G6-JY7G4M69kycgIKtgAu77nYMs5sqqb1CMS8WHk/query HTTP/1.1"...
  3. five

    Resolved NGINX error: upstream sent too big header

    Hello everybody, we receive errors during working with WordPress installations on our server: 84381#0: *2908 upstream sent too big header while reading response header from upstream Sometimes when updating plugins, but also when just clicking around. An example out of our logfile is attached...
  4. 1

    Apache / DrWeb stops after Auto-Update Plesk 12.5.30

    Horror when in the night automatic updates comes and after the installation the server with 100 clients stops about apache not startet correctly! We have this problem 2 years much often and then this was resolved and now that begins again, about why files not completed on the plesk-update...
    • 1awww.com
    • Thread
    • apache auto-update connection refused hangs plesk stop stopped update upstream
    • Replies: 0
    • Forum: Plesk 12.x for Linux
Back
Top