First steps: Take the server offline, if you can access it directly. – The chance of your server being part of a larger scheme at this point is pretty high. If you can’t take it offline, check your authorized_keys files in ~/.ssh/authorized_keys and remove entries that don’t belong to you. (Repeat this step for every … Read more
I solved this by making the webserver user the owner and the group of all the files in the WordPress directory. I figured out the webserver user was daemon with: ps aux | egrep ‘(apache|httpd)’ Then I changed the permissions with: sudo chown -R daemon:daemon /your-path-to-wordpress
you need to change the owner of the wordpress folder to www-data. For example, if you put your wordpress folder in /var/www/my_new_wordpress_site, you will need to run the following command: sudo chown -R www-data:www-data /var/www/my_new_wordpress_site
Connect to your server via SSH. and remove System temporaty files: rm -rf /tmp/* Delete files that are older than 12 days from the /tmp and /var/tmp/ directories: find /tmp -type f -mtime +12 -exec rm {} \; find /var/tmp -type f -mtime +12 -exec rm {} \; Delete temporary files created by Plesk and … Read more
Ideally, you install php-suexec, so that the php script runs as the file’s owner. This allows the direct method to be used without requiring any permission changes.
Based on your needs, yes: you should probably be using a Network (WordPress with MultiSite enabled). All network sites run the same version of WordPress Each network site can activate its own Plugins. You can explicitly allow each site to manage its own Plugins. Each network site can have access to different Themes (though you … Read more
I ran into the same problem: tried to delete a folder (as admin), but got an error message “You need permissions from MYCOMPUTER\Admin …” Somehow this worked: I just went into the folder and deleted everything inside. Now when I try to delete the folder, it works fine. Not sure why, but it seems like you found … Read more
I already said that I was new to exec() function. After doing some more digging, I came upon 2>&1 which needs to be added at the end of command in exec(). Thanks @mattosmat for pointing it out in the comments too. I did not try this at once because you said it is a Linux command, I am on Windows. So, what … Read more
For reading through a symlink1, which is usually not what you want (you usually don’t want to confuse the user this way), try: IMO, that’ll produce confusing output. “I ran foo.sh, but it’s saying I’m running bar.sh!? Must be a bug!” Besides, one of the purposes of having differently-named symlinks is to provide different functionality … Read more
Remove ; from the end of your script lines. This doesn’t happen in my bash, so I’m not sure what exactly is wrong, but my guess is this: ; is a separator of commands. Since your last command ends in ;, your bash probably expects another command after. Since the script finishes, though, it reads an empty command, which … Read more