Root set to permission 771 - need help!!

  • Posted June 21, 2014

Root was set to permission 771 using the command

sudo chmod -R 771 /

Well this let go a long list of “… cannot change permission” errors before just kicking me out. I now can no longer long into the server with my root or user accounts.

I get the following error

“OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 ssh_exchange_identification: Connection closed by remote host”

Very Very stupid and was a mistake – I’m also very new to this (3 days) but had a lot of progress in setting up my sites. Now those are a 404 error.

From my (very) limited understanding on how permissions work, I think I blocked access from myself to the whole server and thus can’t log in - but not sure if that’s the issue.

Any solutions? I really would hate to loose all the work I’ve done. I will also start backing things up (but there are no backups sadly)… ugh terrible day.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Man, I really appreciate your help! I’ll do some research on how to pull everything

You can simply set the machine to full write access via 777 (similar to what you did to begin with) this will make read/write all and give you time to pull everything. Remember to fix this when you move the files to the recreated host. Always snapshot before a big change and always try to know what your command will do before you execute it, it happens to the best of us!

I see what you’re saying… man. I guess this is a hard lesson to learn. So I can get into the console through DO — is there anyway from there to download my files, the nginx files (config & site-available files), and export my databases?

Honestly as I’ve never been down this road I can’t even fathom an estimate. We have to assume we have no idea how mny permissions are now broken and the machine should be viewed as insecure and/or high liabiliy… Resetting manual permissions to the correct perams will take much longer than scratching and restarting.

oh took so long to set this up - what are we talking about with permission migration?

It will be there but the permission mitigation is going to be a nightmare. You can either attempt to fix this or simply pull what you need and start over which will be faster.

Yes, just tried that and was able to get in - it looks like everytrhing is still there

Can you attempt to log in from the web console on the DO panel?