Beginners • Can't access via http to my Raspberry

Hello I'm beginner on Raspberry pi 5 os lite ( Debian 12) my first project is install pi hole to increase privacy, difficult tracking and block online adds.

I follow the raspberry official guide to create a installation with SSH to little server and disable the user login connection, just in case some day I travel with my device. After that I installed the docker following the instructions on the official website. Once I run docker hello world successfully.

All sounds great until I try to access http to my device, I try on the Raspberry http://192.168.1.100:22 or Docker that I suppose should be http:// 192.168.1.100:9000 but nothing happens in both cases.
When I typing hostname -I I find two IP 192.168.1.100 and second seams a Gateway of docker in a different range of network 172.17.0.1 that's should be normal I guess. But then I check for the active network connection with sudo ss -nltp and find the local addresses as 0.0.0.0 :

State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=794,fd=3))
LISTEN 0 4096 0.0.0.0:9000 0.0.0.0:* users:(("docker-proxy",pid=1019,fd=4))
LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=794,fd=4))
LISTEN 0 4096 [::]:9000 [::]:* users:(("docker-proxy",pid=1026,fd=4))Checking some post, I saw that my file on /etc/chcpcd.config was empty, quite strange, isn't by default empty ?
Then I typing, save and reboot but nothings changes:
interface eth0
static ip_address=192.168.1.100/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1

Also tried sudo ifconfig
sudo ifconfig it's any wrong in eth0 ?
docker0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether txqueuelen 1000 (Ethernet)
RX packets 2 bytes 112 (112.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255
ether txqueuelen 1000 (Ethernet)
RX packets 230 bytes 32258 (31.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 98 bytes 17360 (16.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 107

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 14 bytes 1724 (1.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 14 bytes 1724 (1.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vethfa71673: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether txqueuelen 0 (Ethernet)
RX packets 11 bytes 866 (866.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 83 bytes 4316 (4.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

*** So what's going wrong in my configuration ?
My questions are:
1.- Do I had a wrong configuration?
2.- It's possible to access via http on Debian os little or need extra modules ?
3.- It is easier manage installations on desktop Debian enveroinments ?

Statistics: Posted by birdawn — Tue Apr 09, 2024 11:19 pm

---