Related

How can i find what is causing my CPU/Disk Write usage to boost? Question Question
How to Set Up Cloudflare SSL with Digitalocean Droplet ? Question Question

Question

root access problem after changing ssh_config to PermitRootLogin no

Posted June 13, 2016 3.1k views
ApacheLAMP Stack

Hi people

I hope someone can help me

I created a sudo user
after that i made keys for that user
all workes fine with that user
then i set in ssh_config to PermitRootLogin no
and i think i did that when i loged in a root....
i have the feeling i locked myself out from the server

now the problem is i cant login as root anymore....but i need that to change some stuff around.

Be careful im a Newbie to all this :-)

Anyway I hope some points me in a right direction

Thanks

Add a comment
SwissCheese
By:
SwissCheese

Related

How can i find what is causing my CPU/Disk Write usage to boost? Question Question
How to Set Up Cloudflare SSL with Digitalocean Droplet ? Question Question

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.

×
2 answers
gparent June 13, 2016

Log in as your new user?

Reply Report
  • SwissCheese June 13, 2016

    well that i tried but that user has not enough perms, no clue why but i can not change the sshd_config with that.

    solution for newbie.... DO console… root works still there

    did not know that, had to reset my pwd, because mine is extrem long lol but im back in now.

    thank you for your kind help

    Reply Report
    • gparent June 13, 2016

      You could’ve used sudo after logging in as your new user, but if that didn’t work then yes the console is there afterwards.

      Good luck.

      Reply Report
ddulic June 14, 2016

A few tips when creating a new user on a fresh droplet. Do these commands when logged in as root:
useradd -m -G sudo newuser (the group sudo depends on your distribution)
passwd root
passwd newuser
chsh -s /bin/bash (changes the log in console)*
mkdir /home/newuser/.ssh && cp /root/.ssh/authorized_keys /home/newuser/.ssh/ (this is if you used the ssh key to create the droplet)*

Now just remove login as root, relog and the new user and you should be fine :)

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help