I can not login SSH

I am running CentOS.
I setted SSH password authentication disabled and SSH direct root logins disabled.
After that,I can not login SSH with @root suddenly.
I was able to login @root until these change.
Putty shows this message Server refused our key

Try VCN

best thing its rebuild your os.

Reinstall OS. Next time you need to add another user before you disable root login.

Zombie Pop said:

Reinstall OS. Next time you need to add another user before you disable root login.

Click to expand...

I already created another user.And I can not login with this account as well.

mirrorer said:

Try VCN

Click to expand...

What is VCN?

SSTTweb said:

I already created another user.And I can not login with this account as well.

Click to expand...

You did mention that you disabled SSH password authentication. That is why. If you don’t want to login with private keys then you can’t disable password authentication.

You have to reinstall the OS. Do not disable password authentication next time if you do not plan on using private key authentication.

check your ip is not blacklisted by server. easiest is to reinstall os or change ssh root password on your vps dashboard

yojimbo45 said:

check your ip is not blacklisted by server. easiest is to reinstall os or change ssh root password on your vps dashboard

Click to expand...

He is not looking for a solution after 3 months haha

If this is a VPS or dedi, you might be able to connect with a KVM console through the hosting admin interface without the need of SSH

I try one week using ssh keys with my mac terminal and Termius tool (mac) but no success.
The same on azure's own vm serial console and Hetzner's own ssh console.

What I have done;
Generate ssh key rsa 2048 in Termius without password/passphrase, copy and paste the public key to the Hetzner dashboard.
Then try to connect- whamm! The tool asks for password- I not have generated.

The same with azure serial console, the same issue with my mac terminal.
I can connect with ssh +passwort (without keys) into google cloud who makes it easy for me and to azure vm with my mac terminal (not with their own serial console).

On Hetzner no luck- no matter if I use their ssh console or my mac terminal or Termius tool. It always ask for a password.
Hetzner support here is not helpful.
It looks like they force you to have ssh keys, but these tools not accept your keys, also make the vps service is useless.

Any tips here how I can get ssh connection with keys without get ask for password?

Have a nice day !

Hi guys

today a new day try to install wordops but no luck. (google cloud vm ssh console)
First I follow this. guide: https://www.wpdoze.com/how-to-host-wordpress-with-wordops/

also at first set A record for hostname (panel) then do the installion.
All outputs are fine wordops i sinstalled with panel domain.

Then use this command to set wordpress site with ssl;
wo site create myrootdomain.com --wpredis -le --force --php80

Then get this error:

Issuing SSL cert with acme.sh [KO]
Your domain is properly configured but acme.sh was unable to issue certificate.

Then I tried some commands:

sudo acme.sh --set-default-ca --server letsencrypt= command not found
-bash: /etc/letsencrypt/config/account.conf: Permission denied
sudo: /etc/letsencrypt/config/account.conf: command not found

what a sick big crap is this.
I was not able to create my root domain with Let's encrypt ssl and the wordops dashboard not has a "one click" add a site with ssl like with Hestia panel as example.

So no luck to set up this crap so I purged the whole wordops stack.
What is wrong here, why wordops can not set up my root domain with Let's encrypt ssl ?

Have a nice day!

SSTTweb said:

I am running CentOS.
I setted SSH password authentication disabled and SSH direct root logins disabled.
After that,I can not login SSH with @root suddenly.
I was able to login @root until these change.
Putty shows this message Server refused our key

Click to expand...

You need a private key to login. The message says that clearly.

make sure that you using correct SSH key pair for authentication. If you generated a new key pair after disabling password authentication, make sure you are using that private key for authentication.