Problem logging in Raspberry PI

[Jgrboer]

Hi there,


I tried to setup my raspberry Pi 3.
Put the latest image on the sd card, put the file SSH on the same sd card...

Put the sd card in the RPI....

When I try to logon to the RPI I receive the following message:
\
ssh_dispatch_run_fatal: Connection to 192.168.1.24 port 22: Invalid key length
jochemgrootenboer@MacBook-Air-********** ~ %

Whats going wrong and what can I do about it..??

Hope somebody can help me...

[RaspbianUser1]

I am no expert but I would like to ask and suggest a couple of things.
Question 1:
Are you able to turn your pi on and use it using the HDMI port

Question 2:
Have you actually looked at the pi, using the pi, (not running headless)

Suggestion 1:
look at the pi and just look if ssh is enabled on the pi, you possibly done something wrong (not doubting you)

Suggestion 2:
Make sure you are connecting to the correct internal IP address by going to your 192.168.1.0 page and seeing if the raspberry pi is connected and see its internal ip address, it might not be 192.168.1.24

Hope this helps

[Jgrboer]

Sorry,

found the problem, the IP address changed from 24 to 31...... pffff took me a lot of time

thanx for your help

[RaspbianUser1]

You will most likely have to change your SSH command every day, week or month as it may be dynamic

[HawaiianPi]

Check your router's DHCP settings. Many routers have the ability to reserve an IP address for a device, and if yours does, you can reserve the IP of your Raspberry Pi so it won't change when either are rebooted.

[Jgrboer]

Normaly the raspberry is connected through WiFi Wich has a fixed ip address, this 24 - 31 address was from the eth0, for weeks it uses the 24 address but last friday it changed from 24 to 31.. now the eth0 is disconnected... it looks strange to me because there was sort of an answer....

[Jgrboer]

Normaly the raspberry is connected through WiFi Wich has a fixed ip address, this 24 - 31 address was from the eth0, for weeks it uses the 24 address but last friday it changed from 24 to 31.. now the eth0 is disconnected... it looks strange to me because there was sort of an answer....

[Jgrboer]

Normaly the raspberry is connected through WiFi Wich has a fixed ip address, this 24 - 31 address was from the eth0, for weeks it uses the 24 address but last friday it changed from 24 to 31.. now the eth0 is disconnected... it looks strange to me because there was sort of an answer....

[Jgrboer]

Normaly the raspberry is connected through WiFi Wich has a fixed ip address, this 24 - 31 address was from the eth0, for weeks it uses the 24 address but last friday it changed from 24 to 31.. now the eth0 is disconnected... it looks strange to me because there was sort of an answer....

[HawaiianPi]

The IP address might remain the same until the router is rebooted, then all bets are off. On the other hand, if your Pi is not left on all the time, another new device might take that address. That's the nature of DHCP.

If you want it to remain the same, reserve the IP address. However, that will only work if the connection is also the same, in other words, always WiFi (or you could reserve one IP for the Pi's WiFi and another for Ethernet).

I run most of my Pi computers headless, so I have IP reservations in my router for them. That way I know they will always get assigned the same IP, even with a different OS or newly flashed card. No need to mess with OS configuration files or other such nonsense.

[FTrevorGowen]

...
I run most of my Pi computers headless, so I have IP reservations in my router for them. That way I know they will always get assigned the same IP, even with a different OS or newly flashed card. No need to mess with OS configuration files or other such nonsense.

+1 and I also use reserved IP addresses for other (household members') computers, a habit I got in to when I set up a wired network "backbone" in our previous house, before WiFi became "cheap & cheerful" (There was also a time when an IP provider would only allow one, specified, computer to be connected ie. you had to build/use your own "router" system using, for example, Smoothwall Linux IIRC the name ...)
Trev.