Raspberry Pi 3B v1.2 no SSH connection

Question

Raspberry Pi 3B v1.2 no SSH connection

Closed this issue a year ago · 7 comments

Salute,
as described in the title, I just can't get an SSH connection after booting the TorBox....

No matter if via 192.168.42.1 or IP set in the router.

With the image that can be flashed, the WLAN "TorBox051" appears and I can connect but no SSH connection can be established....

Have also tried the install scripts based on Debian or Ubuntu. Where the installation works without errors. But after reboot no wlan appears

If I install again a "normal" OS, no matter which, I can again establish an SSH connection.

Under the Raspberry Pi 4B works, everything as it should, but this I need for something else.

Maybe someone can tell me how to get the debugs to post here?

Answer 1 · 2022-12-19T10:31:09.000Z

Hello
If I understand you right, the problem exists only with the Raspberry Pi 3 Model B+, it exists from the very beginning, meaning that it never worked, and you didn't change anything in the configuration (password and so on)?

The easiest way to help you would be to attach a monitor to the Raspberry Pi and look for errors (failed to start Access point and authentication server for Wi-Fi and Ethernet / failed to start /etc/rc.local Compatibility).

Answer 2 · 2022-12-24T12:59:08.000Z

Soo sorry for the long wait time. With an Display attached I was able to configure the TorBox.
And there shows everything fine.. "TOR IS RUNNING" and the graph shows activity.

Now i`m also able to connect to the AP.
But I cant go with it to the WWW.. DNS problems and sometimes just hanging and loading before he says me no connections.

Looks like I need to buy an Raspberry 4, there seems to work everything

Answer 3 · 2022-12-24T13:13:57.000Z

Also at boot the raise network interface failed to start

Answer 4 · 2022-12-24T13:46:23.000Z

It seems like he have a connection but dont share it with the clients

Answer 5 · 2022-12-24T13:51:30.000Z

ssh still dont work

Answer 6 · 2022-12-30T21:09:24.000Z

Hello again

Regarding the "raise network interface failed to start" message: it does not automatically mean something is wrong.

I guess there is no problem with the AP anymore. However, not being able to log in with ssh is strange. To search for the reason, you can try the following:

Check on the client, if it gets the IP address. Not static IP address, but full DHCP must be activated on the client to get the correct IP, Gateway and DNS address. Most likely, that's not the case because that would explain the problem with the SSH connection and the DNS problems.
On the terminal, you can check if the ssh service is running with sudo systemctl status sshd.service
Check if the wlan0 interface has the correct IP address with ifconfig
Re-run the first start-up dialogue by choosing entry number 11 in the "Update and Maintenance" sub-menu. In the process, activate TorBox's automatic counter actions, but deactivate Vanguards. For more information about the first start-up dialogue, see here.
Share more information to analyze the problem by sending me the files listed here.

The yellow log entries on the top of the statistics monitor could be problematic. You are connected with a entry guard which is failing. With TorBox's automatic counter actions activated (see above), TorBox will automatically try to fix the problem and choose another entry guard. A failing entry guard can also lead to DNS resolution and connection problems, but it doesn't explain your problem connecting TorBox with ssh.

Last but not least, in the next 7-10 days, TorBox v.0.5.2 should be released, which has numerous fixes and lets you filter out slow relays. That was responsible for terrible slow connections in the last months.

Answer 7 · 2023-01-24T00:07:00.000Z

Issue closed due to inactivity