Why ssh authentication fails after changing IP address? - authentication

I recently changed the static IP address for local network of my Ubuntu 14.4
After doing that change I'm not able anymore to authenticate via ssh on the machine with root user. Tried from different clients on the network.
I Didn't make any change on machine's users
I got a permission denied
$ ssh root#192.168.1.13
Permission denied, please try again.
Should I go somewhere to update ssh users, according to the new IP?
I didn't find anything about this issue related to IP change.
Thanks

Related

SSH connection refused on external network with the default username

I recently tried to configure port fowarding on my raspberry pi, to be able to connect through it from anywhere. So, I changed my box parameters to permit it.
It seems to work, as my raspberry pi is responding. But I still use the pi username, and it seems to cause the rejection of the connection. When I try to connect to my raspberry pi, the following message appears:
PS C:\Users\MyUser> ssh pi#xx.xx.xx.xx
You are trying to login with the default username.
For security reasons this can only be done from a local network or console.
pi#xx.xx.xx.xx's password:
Permission denied, please try again.
Of course, I can assure you that the password I enter is correct. When I'm connected to my local network, even if I'm using the ip adress of my box (the one with the ip forawrding) to connect to my raspberry pi, it works perfectly. But if I try from another network, this message appears.
I've been trying to search on internet how to solve this problem but couldn't find anything, event by trying to modify the sshd config.
Any clues to remove this behavior and allow me to connect to my raspberry pi, from a distant network, only with a port redirection (yeah I've heard about tunnelin, pitunnel, etc but that's not what I'm looking for) and without changing the username (Yes I'm aware that chaning it will allow me to ssh succesfully but that's not what I'm looking for) ? Thanks in advance.

The SSH Tunnel could not authenticate with the remote host

I am trying to connect Laravel Forge database from Sequel pro. I am getting the "The SSH Tunnel could not authenticate with the remote host. Please check your password and ensure you still have access" error.
Initially I was asked to enter the paraphrase. I got the same result even with the right paraphrase.
Thanks in advance.

Access Server via SSH When IP Address Is Blocked

The entire scenario of my situation seems 10/10 sketchy, I'll admit. So I won't bother convincing you this isn't a malicious attempt to access a server that isn't mine - I'll simply say once, that this is a legitimate need for assistance.
That said, basically my problem goes back to me being a little too restrictive when it came to SSH access to my CentOS 6 server. Basically I restricted access to my custom SSH port from only two IP addresses - one being my home address, and one being my work address - via iptables. The problem is, I no longer work where I do, and my home IP address changed ever since I upgraded my internet.
Obviously this means I no longer am able to connect to my server via SSH since I don't own that IP address anymore.
My question is, is there anything I can do to access this server? I have no console access, but I do at least know the IP address I used to use to log into the server (maybe possible to spoof an IP address, but I have no clue). The only other thing I can think of is I have DirectAdmin installed on the server and can still login with the admin account. Other than that, I've got nothing.
If anyone has any idea on what I can do, it would be greatly appreciated.
You can change the SSH port number from Directadmin file editor (if you have root password),
Then restart the sshd service from service manager
And you can connect to SSH via new port number!

Google Cloud server (GCE), custom image, SSH login issue

I'm playing with Google Compute Engine(GCE) as I'm planning to migrate the cloud service provider from Rackspace(reason: GCE has good upgrade plans with best discount price).
I have few issues with GCE and one of them is Ubuntu os/image not supported by default. But there is an alternate method to run any linux distro in GCE, which is called Building an image from scratch for uploading custom images and creating instances(servers) from uploaded image.
I could able to create and run the instances from the Ubuntu image I uploaded to GCE following the link hagikuratakeshi.hatenablog.com. This is simply running ubuntu in general. I didn't face any problem but google's gcutil tool prompts for ssh passphrase and adds the key in GCE meta data but accepts only password logins(then why it prompts for passphrase).
I want to strictly follow Building an image from scratch as recommended by google. But after following all the steps, I could not able to login to my server instance via SSH. I guess this happens when I install Google Compute Engine image packages: google-startup-scripts_1.1.2-1_all.deb, google-compute-daemon_1.1.2-1_all.deb & python-gcimagebundle_1.1.2-1_all.deb. These packages/scripts make some changes to the instance at the startup and also to SSH configuration which are Strongly recommended. Once I strictly follow the link or once I install these packages I could not able to establish SSH connection once the instance is rebooted. The error message similar to the one below is shown while trying to connect:
test#machine1:~$ gcutil --service_version="v1" --project="mypro-555" ssh --zone="asia-east1-a" "server-instance-1"
INFO: Running command line: ssh o UserKnownHostsFile=/dev/null -o CheckHostIP=no -o StrictHostKeyChecking=no -i /home/test/.ssh/google_compute_engine -A -p 22 test#101.167.xxx.xxx -
ssh: connect to host 101.167.xxx.xxx port 22: Connection refused
NOTE: The user account test is available and common on both local and GCE server!.
My main problem is SSH connection when I strictly follow the steps. If I upload the fresh image and then follow the recommended steps connecting SSH, I could not do SSH again once I restart the instance (or) if I setup everything in the uploaded image before uploading, the created instance will be running but I could not able to connect atleast ones and the error is same.
Anybody using GCE with your custom image?, are you allowed to connected even after following the recommended settings?. Anyone already fixed this SSH issue?. Please post your comments!
EDIT 1
I could not figure out from the logs and here is the output of gcutil getserialportoutput server-instance-1.
The key here is that your ssh client says "connection refused". This indicates that there is indeed a machine at that IP address, but it's not accepting SSH connections. There are a few possible explanations:
The ssh daemon isn't running, or is listening on the wrong interface
Your instance is configured with a firewall that's denying SSH traffic
The GCE firewall rule to allow SSH traffic has been removed

Server Refuses SSH key

I purchased shared hosting from Vexxhost.I wanted to host my Rails application with them.I was given cpanel details.I generated SSH keys using the cPanel and converted it to .ppk format.Next, i downloaded the key.But when i try SSH login using Putty, i get the message Server Refused Our Key.Then i'm prompted for the password.When i enter password, message is displayed: Shell access is not available for your account.Contact support.I did contact support, but no reply.Am I doing any mistake in the procedure?
I haven't used cpanel to generate ssh keys, usually I do it at the ubuntu console. Is it possible that the ppk conversion has encoding issues? or it not done right?
Do you have access to a linux box? It would be simpler to test it there.
I have configured a server myself with ssh access, and if user does not have ssh access they are presented with user/pass. So it appears that your ssh credentials are denied, but your password is recognized as accurate. Authentication is happening.
About the issue of shell support. It could be that they enable shell support only if you connect with valid ssh credentials - in which case, you need to contact support.
Or, your account does not have ssh access, and you still need to contact support.
hope it helps