F5F Stay Refreshed Hardware Desktop Unable to connect via SSH to Raspberry Pi – Investigated all possibilities for two weeks.

Unable to connect via SSH to Raspberry Pi – Investigated all possibilities for two weeks.

Unable to connect via SSH to Raspberry Pi – Investigated all possibilities for two weeks.

Pages (2): 1 2 Next
P
pinkwolf_pvp
Member
144
09-26-2018, 05:48 AM
#1
Hello everyone, I'm working on a project that needs SSH access to a Raspberry Pi, but after two weeks I'm still having trouble. Here are the settings I've used in Raspberry Pi Imager: Hostname: raspberrypi.local Username: raspberrypi Password: [redacted] Wi-Fi SSID: [redacted] Wi-Fi Password: [redacted] Country: BE (Belgium) SSH: Enabled I've tried everything: flashed the SD card multiple times, changed power cables and sources, used different versions of the Raspberry Pi Imager, added an empty ssh file plus a valid wpa_supplicant.conf to the boot partition, and even pinged raspberrypi.local but got no response. The router doesn't list the Pi in its connected devices. A note: I had a working Pi before but accidentally damaged it. Recently I got a replacement board (raspberry pi 2 zero w), yet nothing seems to work despite following the same steps. I'm really stuck and would appreciate any advice or help from anyone who's faced a similar problem. I'm eager to finish this project but need fresh ideas. Thanks in advance! Edited July 23, 2025 by Kilrah Removed credentials
P
pinkwolf_pvp
09-26-2018, 05:48 AM #1

Hello everyone, I'm working on a project that needs SSH access to a Raspberry Pi, but after two weeks I'm still having trouble. Here are the settings I've used in Raspberry Pi Imager: Hostname: raspberrypi.local Username: raspberrypi Password: [redacted] Wi-Fi SSID: [redacted] Wi-Fi Password: [redacted] Country: BE (Belgium) SSH: Enabled I've tried everything: flashed the SD card multiple times, changed power cables and sources, used different versions of the Raspberry Pi Imager, added an empty ssh file plus a valid wpa_supplicant.conf to the boot partition, and even pinged raspberrypi.local but got no response. The router doesn't list the Pi in its connected devices. A note: I had a working Pi before but accidentally damaged it. Recently I got a replacement board (raspberry pi 2 zero w), yet nothing seems to work despite following the same steps. I'm really stuck and would appreciate any advice or help from anyone who's faced a similar problem. I'm eager to finish this project but need fresh ideas. Thanks in advance! Edited July 23, 2025 by Kilrah Removed credentials

R
rosaliE65
Member
211
09-27-2018, 04:29 PM
#2
The issue lies several levels above the basic "can't SSH" problem. Here are some steps to troubleshoot your setup. You're using a custom Raspi 2 Zero W version, not just the standard one.
R
rosaliE65
09-27-2018, 04:29 PM #2

The issue lies several levels above the basic "can't SSH" problem. Here are some steps to troubleshoot your setup. You're using a custom Raspi 2 Zero W version, not just the standard one.

I
ImSquirrel
Junior Member
10
10-14-2018, 08:00 PM
#3
Use the IP Address instead of the host name. This domain works only if DNS is set up for that address.
I
ImSquirrel
10-14-2018, 08:00 PM #3

Use the IP Address instead of the host name. This domain works only if DNS is set up for that address.

1
111carys111
Posting Freak
832
10-15-2018, 12:02 AM
#4
OP isn't able to locate the IP address because it isn't shown in the router's device inventory.
1
111carys111
10-15-2018, 12:02 AM #4

OP isn't able to locate the IP address because it isn't shown in the router's device inventory.

X
XxRohaanxX
Junior Member
26
10-17-2018, 04:25 AM
#5
Using a Raspi 2 Zero W version for flashing is possible.
X
XxRohaanxX
10-17-2018, 04:25 AM #5

Using a Raspi 2 Zero W version for flashing is possible.

T
Triggerchop86
Junior Member
12
10-17-2018, 04:59 AM
#6
I don’t possess the IP address since I can’t send a ping.
T
Triggerchop86
10-17-2018, 04:59 AM #6

I don’t possess the IP address since I can’t send a ping.

M
Markoxx1
Junior Member
41
10-17-2018, 05:28 AM
#7
Hi there! Your issue isn't on the network. You can try connecting a monitor and some peripherals to see if that helps.
M
Markoxx1
10-17-2018, 05:28 AM #7

Hi there! Your issue isn't on the network. You can try connecting a monitor and some peripherals to see if that helps.

X
xSapir
Member
138
10-18-2018, 01:08 AM
#8
In advance, clarify whether the Wi-Fi comes from the Pi or your personal network. Sharing both SSID and password openly in a public area isn't advisable.
X
xSapir
10-18-2018, 01:08 AM #8

In advance, clarify whether the Wi-Fi comes from the Pi or your personal network. Sharing both SSID and password openly in a public area isn't advisable.

O
OmqDace
Posting Freak
798
10-19-2018, 08:48 AM
#9
You can't use the host name to send a ping since no DNS server is mapping it to an IP address. If the device isn't showing up in the DHCP lease list, it means the Pi isn't requesting an IP address. It might not even connect to the Wi-Fi network. Attaching a screen would help you observe what's happening inside.
O
OmqDace
10-19-2018, 08:48 AM #9

You can't use the host name to send a ping since no DNS server is mapping it to an IP address. If the device isn't showing up in the DHCP lease list, it means the Pi isn't requesting an IP address. It might not even connect to the Wi-Fi network. Attaching a screen would help you observe what's happening inside.

D
dive0s
Junior Member
14
10-19-2018, 04:10 PM
#10
Absolutely, we all concur. However, we’d first need to locate the OP in Belgium and be within a few hundred feet of the AP to act on this data. This likely stems from the absence of a DHCP lease, meaning the connection isn’t establishing properly. It’s possible you could flood your network and try SSH on every IP, but the issue remains unresolved. It seems you might have used the same Wi-Fi password as your rPi user account—something worth questioning. Edited July 23, 2025 by Kilrah Removed credentials
D
dive0s
10-19-2018, 04:10 PM #10

Absolutely, we all concur. However, we’d first need to locate the OP in Belgium and be within a few hundred feet of the AP to act on this data. This likely stems from the absence of a DHCP lease, meaning the connection isn’t establishing properly. It’s possible you could flood your network and try SSH on every IP, but the issue remains unresolved. It seems you might have used the same Wi-Fi password as your rPi user account—something worth questioning. Edited July 23, 2025 by Kilrah Removed credentials

Pages (2): 1 2 Next