[SOLVED] why does ssh to my server give me a blank shell?
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
This is my first attempt at ssh and I ran into the following problem - tried to find an answer and maybe it is an obvious one but haven't found it yet - :
i can log into my server using ssh (both from windows via Putty and from my puredyne computer using the terminal), but once I've logged in there is only a blank terminal that doesn't respond to commands. It is as if I had gotten up a notebook where I can write stuff, but the computer doesnt give a hoot what it is! : )
To further your investigation, you may want to look at some documentation on how to configure the ssh.conf file to ensure it is configured properly. There are some links below. This is assuming you are trying to access a Ubuntu server. It should make no difference if you are running different shells on each machine. SSH is just a bit smarter 'dumb terminal'. A gateway application for remote management of servers. It will present you with the shell the remote server is running.
Ok, so now I finally got to my server today sunday, and I looked through the sshd_config file again. I realized that "AllowUsers" had been set to "username" instead of "username@ip#". I wasn't sure if this was ok, so i decided to comment out AllowUsers, since the default is that all users are allowed login.
I set the file to chmod 755, which it already was, but after i chmoded it, it showed green in the terminal, which I optimistically take as a good sign.
I set my firewall ufw to allow port 22.
Now I'm going home to try to access the server again.. will give an update on how that goes.
Is there any difference whether you enter the correct or a wrong password by intention? If you enter any command in such a session (i.e. blindly something like ls) do you get any output? You can run ssh it with -vvv to get verbose output of the connection.
when i write ssh "hostuser@ip#" the cursor jumps down a step, and upon entering commands such as ls it doesnt give any response. Im not required to be root. Neither does anything different happen if i enter a random ip# instead of my own.
After a minute or two, i get:
ssh: connect to host ip# port 22: Connection timed out
zsh: exit 255 sudo ssh david@ip#
Then you don’t have a connection at all, and not a blank screen because of any shell setting. Even with putty you would get the question for your password otherwise. Is there any firewall on port 22 on the target machine?