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

    Resolved nginx: [emerg] "proxy_read_timeout" directive is duplicate

    The error disappeared - can you describe, for noobs like me, what exactly went wrong there?
  2. G

    Resolved nginx: [emerg] "proxy_read_timeout" directive is duplicate

    There is not much output :D root@xxxxxx:/# plesk sbin nginxmng -d root@xxxxxx:/# plesk sbin nginxmng -e root@xxxxxx:/# As in: there is no output. Is there a verbose-option? ***EDIT*** The error message in the plesk admin console disappeared, though.
  3. G

    Resolved nginx: [emerg] "proxy_read_timeout" directive is duplicate

    Hey Milan! I reset PHP settings on both subdomains to default, removed the proxy_read_timeout-option from both nginx settings and reloaded the nginx service: the error persists. Is there anything I can do to provide more info on this?
  4. G

    Resolved nginx: [emerg] "proxy_read_timeout" directive is duplicate

    Hey Lloyd! Thanks a lot for your answer - unfortunately, it didn't work yet. In the PHP-settings for the subdomain, I had max_execution_time and max_input_time on increased settings, too. I reset those to default - no change. I also removed the proxy_read_timeout value - still no change. Do...
  5. G

    Resolved nginx: [emerg] "proxy_read_timeout" directive is duplicate

    Hey guys! I got this error message, which I don't really understand: New configuration files for the Apache web server were not created due to the errors in configuration templates: nginx: [emerg] "proxy_read_timeout" directive is duplicate in...
  6. G

    Unable to generate the web server configuration file after "upgrade" to V12

    Oh wow, 3 PMs - thanks igor, I didn't get a mail-notification... will look them up at once! :)
  7. G

    After upgrade from 11.5 to 12.0.8 apache does not run anymore

    Hey Peter! A lot of people, me included, seem to be running into a similar problem, as lined out here: http://forum.parallels.com/showthread.php?305049-Unable-to-generate-the-web-server-configuration-file-after-quot-upgrade-quot-to-V12 Think you could shed some more details on how you...
  8. G

    Unable to generate the web server configuration file after "upgrade" to V12

    I have to chime in with the same problem - from the error mail: "Unable to generate the web server configuration file on the host <xxxxxxxxx> because of the following errors: Template_Exception: nginx: [emerg] PEM_read_bio_X509_AUX("/opt/psa/var/certificates/certrKAR5Gk") failed (SSL...
  9. G

    qmail / relaylock Problem

    Ok, will give that a try... also: why is the server running normally for well over 600 days and suddenly it freezes with this (reproducable) problem?
  10. G

    qmail / relaylock Problem

    Hello everybody! Using SuSE 9.3 with Plesk 8.2.1 - upon booting the Server, all seems to work normally - shortly (really shortly) afterwards, Ples frontent dies with "too many SQL connections, SQL server unreachable". On the console, ps -A yields hundreds of "relaylock" processes. They add...
Back
Top