Revision history [back]
 | 1 | initial version | posted 2014-03-18 09:25:49 +0200  |
After update, no more ssh access
Hello, I followed all the suggestions about disabling openrepos etc, updated, the telephone works nicely - but I cannot connect through ssh anymore. What to do?
It seems at least one other user has the same problem
| | 2 | No.2 Revision |
After update, no more ssh access
Hello, I followed all the suggestions about disabling openrepos etc, updated, the telephone works nicely - but I cannot connect through ssh anymore. What to do?
It seems at least one other user has the same problem
The response is this
ssh nemo@192.168.1.31 ssh: connect to host 192.168.1.31 port 22: No route to host
| | 3 | No.3 Revision |
After update, no more ssh access
Hello, I followed all the suggestions about disabling openrepos etc, updated, the telephone works nicely - but I cannot connect through ssh anymore. What to do?
It seems at least one other user has the same problem
The response is this
ssh
nemo@192.168.1.31nemo@192.168.1.31 ssh: connect tossh: connect tohost 192.168.1.31 port 22: No routetoto host
| | 4 | No.4 Revision |
After update, no more ssh access
Hello, I followed all the suggestions about disabling openrepos etc, updated, the telephone works nicely - but I cannot connect through ssh anymore. What to do?
It seems at least one other user has the same problem
The response is this
ssh nemo@192.168.1.31 ssh: connect
toto host 192.168.1.31 port 22: No routetoto host
| | 5 | No.5 Revision |
After update, no more ssh access
Hello, I followed all the suggestions about disabling openrepos etc, updated, the telephone works nicely - but I cannot connect through ssh anymore. What to do?
It seems at least one other user has the same problem
The response is this
ssh nemo@192.168.1.31
ssh: connect to host 192.168.1.31 port 22: No route to host
After update, no more ssh access
Hello, I followed all the suggestions about disabling openrepos etc, updated, the telephone works nicely - but I cannot connect through ssh anymore. What to do?
It seems at least one other user has the same problem
The response is this
ssh nemo@192.168.1.31
ssh: connect to host 192.168.1.31 port 22: No route to host