I created a user using 'adduser' on a Ubuntu 18 virtual machine that I ssh'd into using Vagrant. I am now trying to ssh into the server using the user credentials I created. I keep getting connection refused. I believe it is my syntax that is causing this so what is the correct syntax for this?
Maybe add here your "code"
but Connection refused can be caused by several reasons.
SSH service is down, Wrong credentials, port is closed, wrong permissions or don't have permissions to connect at all.
Take a look here and try to solve it.
Related
I have a ssh server on an old CentOS 5 installation. I can connect to the server without any problems. However, if i disconnect from the server and want to login again after exiting the previous session, the server is not responding and i got a "connection timed out" error. After a while (must be between 1 and 5 minutes) i can login normally. If i then exit the session, the same timeout happens again.
From the network where the client resides, i can connect to other ssh servers without any problems, so i dont think, this is a firewall issue.
Any suggestions, where i can look for the problem?
I tried to login with key instead of password and i stopped the fail2ban service on the ssh server. Both without any success.
I solved my problem:
There is a iptables rule, which is limiting the connections per ip to one attempt per minute. I have whitelisted my ip and now there is no delay when reconnecting.
Trying to setup ssh server on my WSL 2 for local development. I can connect to it from Putty but having trouble connecting from another machine in the same local network. I try to follow scripts from WSL GitHub Issue #4150 but I might not be able to modify the script well enough to make it work for the use case. I'm getting a connection timed out message error.
Thank you in advance.
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.
I'm trying to see if there's anything I can do to re-gain access to my vm instance via SSH. I had access before, I was creating an ssh tunnel to another server and realized I used the wrong one. I killed ssh via 'pkill sshd' and figured I would be able to regain access after a minute however now I'm unable to at all. I just get connection refused, error 255. Is there any way to send a command to the vm instance to have it restart sshd?
Thanks!
Try using the serial console. Alternately, try rebooting the VM, there's a chance SSH will come up without an error if you give it another shot.
I am trying to connect to SFTP server using notepad++ plugin NppFTP. However, while connecting to the remote server I always get below error:
Connecting
[SFTP] Connection failed : Timeout connecting to <IP address>
Unable to connect
Disconnected
Here are the important configuration details set in NppFTP window for your reference:
Port: 22
Connection Type: SFTP
Authentication: Try password authentication
I tried to go through some of the solutions stated in few the questions in Stack Overflow but to no avail.
Would really appreciate your suggestions/pointers to resolve this. If it is related to SSH private key, would appreciate if you can provide the steps as well.
Edit: I am able to access the server using another FTP tool FileZilla which eliminates any mess with the access front.
You need to find out more about where the issue is:
Can you ping the server you are trying to connect to?
ping 166.178.233.70
Did you try connecting with another ftp tool, like FileZilla, that gives more detailed log information?
The possible issues are numerous:
The ftp server config: set up to exclude connections from certain ip addresses or domains, requires public/private keys...
Your local connection/VPN is not passing the connection.
It may require a
I got the same issue. The problem was solved after I updated NppFTP.
in my case, I changed the wifi connection then, it works.