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

    Issue SQLmap attack detected (ID: 218500) on blank page

    Is is save to switch of the security rule, because I am facing the same challenge after migrating wordpress site to plesk, I tried uploading the website file to a brand new wordpress site yet it returns 403 forbidden error. When I checked the Web Application Firewall log it discovered it was...
  2. A

    Question Server Error 403 Forbidden - Wordpress migration

    I have similar error Server error 403 Forbidden after uploading website files. I have checked folders and files the have right permissions.
  3. A

    Resolved Problem when migrating subscription. Unhashable type list

    I have been trying run migration. I have open port 22, 110, 8443, 143 on both source and destination servers has advised in the documentation but yet, pre-migration checks returns "Failed to check SSH connection to the source server 'source' (51.79.19.219): Unable to connect to 'source IP' by...
Back
Top