I cannot access RPiB+ from my local network

Troubleshooting
1

Hello together,

Before start I need to mention that I have searched for a fix on Google and here for several weeks. But nothing found. For the moment I do not want to start with a fresh install.

I have a RPiB+ with Diet OS configured as DHCP (using Wi-fi with local IP 192.168.0.150) and I cannot access it through local network even that I can ping it with success and I can see it when I’m scanning the network with Advanced IP Scanner.

I have NextCloud installed and I want to access it via port 80. SSH the same is not available on local network.

One thing to mention (maybe this is the problem) : I have Remote.it account installed and guess what HTTP and SSH is working (on their links).

Am I missing something?

Thanks

2

Hi,

question: are you able to access your system via Remote.it?

3

yes, all the time! (if system == RPiB+)

4

pls can you connect to your system and run the following command

lsof -i -P -n | grep LISTEN

if lsof command is not available, it can be installed like the following

apt install lsof
5 



root@DietPi:~# lsof -i -P -n | grep LISTEN
rpcbind    629      root    8u  IPv4   12564      0t0  TCP *:111 (LISTEN)
rpcbind    629      root   11u  IPv6   12567      0t0  TCP *:111 (LISTEN)
dropbear  2810      root    3u  IPv4   18485      0t0  TCP *:22 (LISTEN)
dropbear  2810      root    4u  IPv6   18486      0t0  TCP *:22 (LISTEN)
redis-ser 3000     redis    4u  IPv4   16110      0t0  TCP 127.0.0.1:6379 (LISTE                                                                                        N)
mysqld    3121     mysql  109u  IPv4   18690      0t0  TCP 127.0.0.1:3306 (LISTE                                                                                        N)
lighttpd  3251  www-data    4u  IPv4   20569      0t0  TCP *:80 (LISTEN)
lighttpd  3251  www-data    5u  IPv6   20570      0t0  TCP *:80 (LISTEN)
mosquitto 3273 mosquitto    4u  IPv4   21640      0t0  TCP *:1883 (LISTEN)
mosquitto 3273 mosquitto    5u  IPv6   21641      0t0  TCP *:1883 (LISTEN)
netdata   3286   netdata    3u  IPv4   18900      0t0  TCP 127.0.0.1:19999 (LIST                                                                                        EN)
netdata   3286   netdata   13u  IPv6   18916      0t0  TCP [::1]:8125 (LISTEN)
netdata   3286   netdata   14u  IPv4   18917      0t0  TCP 127.0.0.1:8125 (LISTE                                                                                        N)
rpimonito 3591    dietpi    5u  IPv4   22760      0t0  TCP *:8888 (LISTEN)
miniserv. 3689      root    5u  IPv4   19130      0t0  TCP *:10000 (LISTEN)
6

basically your system should be available on local network as well because you have dropbear SSH server (port 22) as well as lighttpd web server (port 80) listen on all interfaces. It’s not blocked or used by something else.

dropbear  2810      root    3u  IPv4   18485      0t0  TCP *:22 (LISTEN)
dropbear  2810      root    4u  IPv6   18486      0t0  TCP *:22 (LISTEN)
lighttpd  3251  www-data    4u  IPv4   20569      0t0  TCP *:80 (LISTEN)
lighttpd  3251  www-data    5u  IPv6   20570      0t0  TCP *:80 (LISTEN)

pls can you try telnet from another host/computer on your network to the DietPi RPi system.

telnet 192.168.0.150 22
telnet 192.168.0.150 80
7

thanks for your answer:

on telnet I have the following:


C:\Users\user>telnet 192.168.0.150 22
Connecting To 192.168.0.150...Could not open connection to the host, on port 22: Connect failed

C:\Users\user>telnet 192.168.0.150 80
Connecting To 192.168.0.150...Could not open connection to the host, on port 80: Connect failed

and with ping

C:\Users\user>ping 192.168.0.150

Pinging 192.168.0.150 with 32 bytes of data:
Reply from 192.168.0.150: bytes=32 time=5ms TTL=64
Reply from 192.168.0.150: bytes=32 time=4ms TTL=64
Reply from 192.168.0.150: bytes=32 time=5ms TTL=64
Reply from 192.168.0.150: bytes=32 time=5ms TTL=64

Ping statistics for 192.168.0.150:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 4ms, Maximum = 5ms, Average = 4ms

strange…

8

Just an idea. Did you tried to restart the RPi?

9

yep for several times. seems that going back to Rasbian OS seems that a more plausible way… :frowning: :frowning:

10

Well DietPi is basically a Raspbian lite. Just with reduced amount of packages and some scripts on top. And local access is working fine on all my RPi. So something special on your system.

As I have seen, you are running rpcbind service. Not sure if this could have any impact

11

Can you check the firewall?

iptables-save -c
12

Hi. I am from remote.it. Good to hear remote.it connections are working but odd you cannot connect from the LAN even though Ping is working fine on the LAN? I noticed you used port 22 for Telnet. I thought Telnet is on 23? Anyway if you still have the problem … I am not expert on dietpi but the command to ssh to a pi running Raspbian (a.ka Raspberry OS) is “ssh -l pi 192.168.0.150 -p 22” for default port 22. You might have to give the username in the command? Also if you explicitly type the port number I think you need the “-p” operator.