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

Search results

  1. yusuf

    Resolved Server Error 502 Bad Gateway

    thanks for reply my issue is resolved by its own i do nothing this is error log
  2. yusuf

    Question how to compile uploadprogress extension to all php

    i installed uploadprogress on plesk onyx 17.5 but only found for php 5.4 how can i compile uploadprogress extension to all php versions installed ?
  3. yusuf

    Resolved Server Error 502 Bad Gateway

    after update plesk to 17.5 i reboot server then i can't access plesk admin panel https://213.136.89.33:8443/ and i have this error
  4. yusuf

    Resolved Update to Plesk Onyx Version 17.5.3 failed on centos 7

    ok thnak you your answer resolve issue
  5. yusuf

    Resolved 413 Request Entity Too Large

    ok thank you i will do
  6. yusuf

    Resolved 413 Request Entity Too Large

    okey the problem about duplicate is resolved you said to add two lines to /usr/local/psa/admin/conf/panel.ini ... [webserver] nginxClientMaxBodySize = 128m ... and that cause duplicate problem you should add this ... [webserver] nginxClientMaxBodySize = ... without 128m value thanks
  7. yusuf

    Resolved 413 Request Entity Too Large

    i have this error Invalid nginx configuration: nginx: [emerg] "client_max_body_size" directive is duplicate in /var/www/vhosts/system/zippyloads.com/conf/vhost_nginx.conf:1 nginx: configuration file /etc/nginx/nginx.conf test failed
  8. yusuf

    Resolved 413 Request Entity Too Large

    Invalid nginx configuration: nginx: [emerg] unexpected end of file, expecting ";" or "}" in /var/www/vhosts/system/vidwe.net/conf/vhost_nginx.conf:1 nginx: configuration file /etc/nginx/nginx.conf test failed
  9. yusuf

    Resolved Update to Plesk Onyx Version 17.5.3 failed on centos 7

    i have plesk onyx installed on OS: CentOS 7.3 (64) this is error log " Execution failed. Command: autoinstaller Arguments: Array ( [0] => --select-product-id [1] => plesk [2] => --select-release-current [3] => --upgrade-installed-components ) Details: Doing restart of Plesk...
Back
Top