I deleted sudo on purpose and terminal is asking me for sudo passwd - chromebook

I was getting a lot of errors that I didn't know how to fix everytime I typed "sudo apt-get update" I was kinda new and didn't know who to fix it after countless hours of research so I decided to remove sudo. Now everytime I try to install sudo back I get prompted with the following:
We trust you have received the usual lecture from the local system Administrator. It usually boils down to these three things:
#1)Respect the privacy of others.
#2)Think before you type.
#3)With great power comes great responsibility.
[Sudo] password for "my user name is here"
I don't know my sudo password and I now know I should never have deleted it. Is there a way I can reset everything so I can have a new terminal that ask me for a user name and password. I'm using linux(beta) on chrome os.
Thanks a lot if you are able to help me.

Your sudo password is your normal login password. If for some reason you aren't admin, become root(this may help) and then change permissions (and passwords if necessary. In the end, all you need to be is root, and that by itself can and reset the sudo password.

Related

SVN Wordpress keeps asking for authentication when providing correct credentials

I'm having trouble commiting to my wordpress plugin after switching to a new laptop. I did a checkout to retrieve the repository again after which I made changes and tried committing them.
However, each time I try to commit it replies Authentication realm: <https://plugins.svn.wordpress.org:443> Use your WordPress.org login and asks for my credentials again and again (even with --username myusername --password mypassword), until it returns No more credentials or we tried too many times..
I have tried clearing my svn password cache, am aware that the username is case sensitive and also tried installing subversion using brew, without any luck.
From my old laptop, it still works. But it is unclear to me what is different in my new setup.

Giving write permission back to Wordpress on AWS EC2 via PuTTY

I recently had a PHP syntax error that crashed my server after using the plugin editor on my Wordpress website. It is an AWS Elastic Beanstalk hosted website, so I had to use PuTTY to change the file permissions and allow ec2-user to read/write durring SFTP via Filezilla.
I am not experienced with his sort of thing and followed the information from this question to accomplish this task.
Everything went well, but now I cannot edit or "write" anything via my Wordpress website. No plugin updating, no file editing, nothing. It says I need to change my permissions.
Due to my lack of knowledge on this, I have no idea how to reverse what I did when I entered
chown -R ec2-user /var/app
chmod -R 755 /var/app
How do I set the permissions back so I can edit files and update plugins via Wordpress admin?
EDIT: I found out that all I did was change ownership of the files to ec2-user. SO I guess my new question is how do I find out what username to use for my WordPress site to give it back ownership of the files?
Fixed:
I wound up adding
echo(exec("whoami"));die();
to the top of my WordPress index.php file to figure out the user. Make sure to remove it once you're done.
Lets say my username wound up being "foo".
After I had the username, I went back into PuTTY, and ran
sudo chown -R foo /var/app
and can now modify files through wordpress again.

Wordpress requires FTP information to update plug-ins

I'm trying to update Wordpress plug-ins, and I'm presented with the familiar FTP login screen.
I have read other posts indicating the lines in wp-config.php to be filled in. However, I don't have FTP installed on this server, just SFTP.
Also, I don't want to have to do this for each Wordpress install.
As far as I know, wp-content is already owned by apache:apache, and PHP is also running as user apache.
Is there something I'm missing? Is there some other way to handle this?
This has happened to me alot, when installing wordpress on my own server. Usually it has to do with a permission problem.
A lot webservers use the user www-data, instead of apache. So check your apache configuration for what your webserver user is set to.
Also you will want to check your directory permissions, and make sure both the user and group has read, write, and execute access. I am not sure if execute access is necessary, but that is usually what I set my server too.
You can do this with the command
chmod 775 -r your_wp_content_directory
And if all else fails, if you have shell access you can also use wget in the directory to install plugins.
After trying everything I could find regarding permissions, I added the following line of code to this site's wp-config.php:
define('FS_METHOD', 'direct');
That immediately solved the problem. Not sure if I also needed to modify the permissions first, since i did that before trying this fix.

WordPress SVN Commit Failed

My plugin has been approved in wordpress. But I am having trouble to upload the plugin via SVN. When I am filling out the username and passowrd and ticking on the save authentication this box is showing again and comes 4 times. Finally it shows Commit Failed! Please anyone help me how I can solve this issue.
Thanks
If your credentials aren't accepted, either you're entering them wrong (make sure you've got the correct case, as it's case-sensitive), you don't have the required permissions on the URL you're committing to, or the URL you're committing to is incorrect (again, it's case-sensitive, so make sure that you've got everything perfect).
But to get an authoritative answer, you need to ask the WordPress folks as they're running the server and granted you the access.

Could not remove the old plugin

I'm trying to update the plugins on my clients site and I'm getting this error for multiple plugins. He's using plesk.
Downloading update from https://downloads.wordpress.org/plugin/awesometastic.131026.zip…
Unpacking the update…
Installing the latest version…
Removing the old version of the plugin…
Plugin update failed.
An error occurred while updating Awesometastic Plugin: Could not remove the old plugin.
I'm sure it's got something to do with directory permissions, although, could someone explain to me what the possible issues are and how to fix this?
Thanks!
It's a permissions issue. Run this on SSH:
chmod -R 0755 /var/www/<yourpathtowordpress>/wp-content/plugins
chown -R www-data /var/www/<yourpathtowordpress>/wp-content/plugins
The first grants writing permissions, while the second ensures the user who needs the permission is correctly set
WordPress does not display OS level errors by default but this is most definitely a permission issue on your plugins folders in your site's wp-content/plugins.
You could enable debugging in order to see the original error which triggered the more generic one you've seen if you want to work with a better view of the world.
Multiple debugging options are documented in WordPress' online manual. To enable debugging and log messages set the following variables in wp-config.php:
Enable debugging via WP_DEBUG
define('WP_DEBUG', true);
Enable logging debug messages to the /wp-content/debug.log file with WP_DEBUG_LOG
define('WP_DEBUG_LOG', true);
You should probably make sure to disable these options and delete the debug.log file after gathering enough information as they could contain server information you do not want to be accessible publicly through your WordPress installation.
Alternatively we can try to guess what the most plausible cause can be:
If you installed your plugins manually on the server and not via the
WordPress administration console it is likely you did it as a
different user then the one who is executing WordPress' PHP code and
thus requires proper access to perform such OS operations.
Finally the solution may be to fix the permissions or upgrade the plugins manually.
Basically this is permission issue.
and you will have to provided or make FTP user as owner of the plugins folder.
Most of the cases where you will be using same user for WordPress install and run as well as FTP access. If you are using different users for both above purpose then providing ownership to FTP user will fix this issues just like that.
Ex:
chown -R ftpadmin /var/www/wordpress/wp-content/plugins
Hope this would be helpful if any body at this stage.
first you have to delete the old plugin than update
If you have SSH access to your blog
Login your site via SSH.
Use SSH commands to nagivate “../wp-content/plugins/”.
type the given command to see all files and folders in the plugin folder
ls -al
Search for the particular plugin folder in the list.
Next, type the given command to delete that folder.
In the command, replace the folder name with your plugin folder name which is you want to delete.
rm folder name
now you're able to delete your old plugin.
Hi this is the permission issue at wordpress so follow this command
sudo chmod -R 0777 /var/www/html/thewayivogue/wp-content/plugins
like this where thewayivogue replace to your folder name.
Open FTP ank kill em all :)
Then reinstall those plugins. It is better not to open admin panel while removed so you have it still activated.
But do backup. It can Save Willy

Resources