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

Question I want to talk to support.

I assume that the permissions of the file have been set to read-only for the group psacln and anonymous users. It's probably a file that was created by a script, so it is owned by the webspace system user arabh1x. The screenshot does not show the file and its owner, group and permissions, but it is likely the cause. Could you please check that?

In that case the easiest solution is to login as "admin" or to login through SSH to your Linux shell, either chrooted or root does not matter in this case. From there you can use the Linux "rm" command to remove the file.

Should that not be a possible approach for you, you can also try to edit the file permissions and change them to at least 664 (write and read permissions for the group psacln), afterwards you will be able to delete the file through file manager, too.

Should that not be possible either, you can use this PHP script to remove the file. Simply create a file ending on .php and upload it into your webspace:
PHP:
<?php
unlink('/var/www/vhosts/arabcomics.net/httpdocs/wp-content/plugins/xemi.php');
?>
Then open the file in a browser once.

Please also consider that the file is located in the Wordpress plugins directory, so it might be part of a plugin. The plugin may not function properly any longer after it was removed. Maybe it is best to remove the plugin instead of only removing the single file.
 
Back
Top