Phoenix Network Forums

Last few days when i try to ssh 208.98.27.3 i get no response.This is what i get...

tastasosos@slackware:~$ ssh -l tasosos 208.98.27.3
Password:

I give the password and then nothing.Not even ctrl+c works.

ssh the domain instead, users.phoenix-hosting.org. that may do it.

tasosos wrote:Last few days when i try to ssh 208.98.27.3 i get no response.This is what i get...

tastasosos@slackware:~$ ssh -l tasosos 208.98.27.3
Password:

I give the password and then nothing.Not even ctrl+c works.

I've had the same problem. A workaround was ssh -l $USERNAME 208.98.27.3 /bin/bash. But now it's working without workaround (no idea what has been changed).
BTW, I cannot change my login shell:

Code: Select all

chsh -s /bin/bash
You may not change the shell for hafner.

Regards
Thomas

Is everything working out now guys?

I'm getting a "Server refused to allocate pty" error sporadically when trying to SSH in. If I keep trying, I can get in eventually, but I get that error most of the time.

i get this:

Server refused to allocate pty

darkholm wrote:ssh the domain instead, users.phoenix-hosting.org. that may do it.

darkholm, stop giving bad advice.

ssh infinity.phoenix-hosting.org
thats the one to sue for ssh'ing into phoenix-hosting.org

I thought one could ssh many ways?

I've done that.

Samppa wrote:I thought one could ssh many ways?

I've done that.

we used to be able to ssh to user.phoenix-hosting.org which would redirect us to default.phoenix-hosting.org but not anymore since the BIG CRASH. since then we can only ssh to infinity.phoenix-hosting.org
atlest thats what my experience tells me. Please correct me if I'm wrong. Try ssh'ing to username.phoenix-hosting.org and connect, maybe its just me.

now everything works perfectly and i didn't to anything.I just ssh to the ip 208.98.27.3

The correct hostname to ssh to is users.phoenix-network.org (not your username, the word users). infinity.phoenix-hosting.org and infinity.phoenix-network.org only exist for your convienience they are no longer the official way to connect to the shell server.

The issue was not about the hostname. does SSH even know the hostname you are conecting to or only the ip? Besides the error occured on all IPs and hostnames by the time it occured.

De Kus wrote:The issue was not about the hostname. does SSH even know the hostname you are conecting to or only the ip? Besides the error occured on all IPs and hostnames by the time it occured.

I wasn't replying to the issue, I was replying to the discussion about the hostname.

The issue just means that too many people are logged in so all TTY's are in use.