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

    Question Issue Implementing Dynamic CORS Headers in Plesk’s Additional NGINX Directives

    Hello everyone, I’m encountering a problem with setting up dynamic CORS headers in our Plesk environment for our Capacitor-based React application. While the app works perfectly in a browser, the iOS simulator reports the following error: Origin capacitor://app is not allowed by...
  2. Y

    Issue Wrong Subscription ID's / Context

    Hello, we are facing some problems. After the last update we have the problem that the scheduled tasks for each domain are working but when I try to change a script path or something like that we are in a completely wrong directory from other subscriptions or other domains. Is there a way to...
  3. Y

    Issue SSL issue with Let's Encrypt always sets CN name to plesk

    We have the problem that every ssl certificate which we are issued over Let's Encrypt is set to issuer name (CN) "plesk" not the domain. What cause this problem? Clearing Cache, restarting Server is not the solution.
Back
Top