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

    Plesk 12: BEAST and other SSL vulnerabilities

    This fixed Poodle vulnerability but didn't fix Beast vulnerability. Any suggestions?
  2. S

    Plesk 12: BEAST and other SSL vulnerabilities

    I managed to solve the issue with this -> http://kb.odin.com/en/123160 <- article by running the script for Linux - Disables Apache, nginx, proftpd, courier-imap, qmail, postfix, dovecot, Plesk server engine (for versions 11.5 and later). But your right now I have no email :D so thanks for...
  3. S

    Plesk 12: BEAST and other SSL vulnerabilities

    I recently changed my SSL Certs for SHA-2 and while I was generating Certs from my provider they prompted me to Scan for SSL vulnerabilities and 3 warning came up. Sessions may be vulnerable to BEAST attack Server does not have session resumption enabled Server has not enabled HTTP...
  4. S

    Plesk API: 502 Bad Gateway, Subscription

    Problem Resolved the issue was the Plesk Application Firewall or Watch Dog. Unfortunately I removed Watch Dog and disabled the firewall at the same time in my desperation so im not sure which fixed it but it resolved the 502 error.
  5. S

    Plesk API: 502 Bad Gateway, Subscription

    Instead of getting the XML response I get the 502 Error.
  6. S

    Plesk API: 502 Bad Gateway, Subscription

    This is driving me nuts, why would I get an error when creating a new subscription but not when im adding a new domain? Proxy log: 2014/12/04 13:27:20 [error] 7658#0: *3 upstream prematurely closed connection while reading response header from upstream, client: xxx.xxx.xxx.xxx, server...
  7. S

    Plesk API: 502 Bad Gateway, Subscription

    I have a plain php file that has the CURL script that connects with the Plesk server to grab the customer information. I can retrieve info, add new customers, but when I add a customer to a subscription I get the 502 error. I wish I could show you a log, but I don't know where I could look for...
  8. S

    Plesk API: 502 Bad Gateway, Subscription

    When ever I create a new subscription the page returns: 502 Bad Gateway I found this article but it did not resolve the issue. http://kb.odin.com/en/118671 This error only occurs when I create a new subscription. I use the following XML: <webspace> <add> <gen_setup>...
  9. S

    How to: disable Plesk welcome email?

    Thanks IgnoG I looked around in the panel for this and could not find it. I Also used the search option in the panel. Thanks again!
  10. S

    How to: disable Plesk welcome email?

    I'm in need of a solution to disable Plesk's welcome email, that is sent out when a new user is created. I'm currently using Plesk's api to manage my server, but we don't allow our customers access Plesk unless they ask for it. We have built our own interface that uses the api. We send are...
Back
Top