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

Recent content by Liberator

  1. L

    Resolved Plesk adding hex data to index.php after change of httpdocs folder

    Well, my problem seems to be solved. I was also getting constant http requests from one IP so banned that. This domain is not really live yet so should have no traffic. Next I deleted all content in httpdocs and deleted some other older folders which had previously been httpdocs folders. I...
  2. L

    Resolved Plesk adding hex data to index.php after change of httpdocs folder

    Thanks @Raul A. and @Bitpalast for your input. I installed and ran Imunify. First run it found 9 infected files in various folders. Some of the folders did not exist previously. All except 1 of the infected files were 'index.php' - the other was named 'blank.php'. I deleted the whole...
  3. L

    Resolved Plesk adding hex data to index.php after change of httpdocs folder

    I was uploading using ftp. Then I used SFTP - both the same result. I just tried uploading using plesk file manager and the same thing happens, including setting permissions to 0444. The original file is 26k. When uploaded it changes to 44k and has the huge section of hex characters at the...
  4. L

    Resolved Plesk adding hex data to index.php after change of httpdocs folder

    I have a website on my server where I had to upload a new httpdocs folder. I renamed the old folder and then uploaded the new folder. All went well until I loaded the (new) website in a browser only to find that my old index.php was shown. On inspection I discovered that the file permissions...
  5. L

    Resolved Imunify360 can't find archive

    Strange. mv /etc/apt/sources.list.d/imunify360* /root/ mv: cannot stat '/etc/apt/sources.list.d/imunify360*': No such file or directory Now I can update no problem and no more failure emails - go figure!
  6. L

    Resolved Imunify360 can't find archive

    Unfortunately that fails at the first command - '-bash: imunify360-agent: command not found'. Any other ideas?
  7. L

    Resolved Imunify360 can't find archive

    I am experiencing update failures and receiving failure emails daily. Each time the failure reason is different. 2 days ago: Reason: 2024-09-19 06:25:16 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2024-09-19 06:25:17 ERROR: Apt cache fetch failed: W:GPG error: Index...
See more
Back
Top