Newly installed Yunohost on Raspberry Pi, facing internet connectivity issue

Support Installation
, , ,
1

Hello, I bought a Raspberry Pi 4B 8 GB RAM (headless) recently and installed Yunohost in it. However, upon running diagnosis, it says that the server is not connected to the internet although port forwarding and DNS seem to have no issues. I am also not able to access through my .nohost.me subdomain.

My YunoHost server

Hardware: Raspberry Pi 4
YunoHost version: 11.2.8.2 (stable)
I have access to my server : Through SSH | through the webadmin |
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : No

Description of my issue

As said above, the diagnosis is showing internet connectivity issue with my server. My raspberry pi is connected to the internet through an ethernet cable connected to my router. Also, I was able to install etherpad-My Pads to the server (I was just seeing if it is able to download the files) successfully. But I can’t really use it because I can’t access the server through outside internet.

Here is the YunoPaste link to my logs from diagnosis: https://paste.yunohost.org/raw/leqopegora

I am also getting the following error under Domain > Certificate:

This domain doesn’t seem ready for a Let’s Encrypt certificate. Please check your DNS configuration and HTTP server reachability. The ‘DNS records’ and ‘Web’ section in the diagnosis page can help you understand what is misconfigured.

2

Yes they have no issues reported, because it precisely can’t test those if the server is not connected to the internet

If you are able to run commans on the server, what does ping -c3 8.8.8.8 reports ?

4

Here is the response:

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=120 time=2.61 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=120 time=2.63 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=120 time=2.71 ms

— 8.8.8.8 ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 2.608/2.648/2.708/0.042 ms

5

mokay, what about ping -c3 google.com ?

6

PING google.com (142.250.179.110) 56(84) bytes of data.
64 bytes from par21s20-in-f14.1e100.net (142.250.179.110): icmp_seq=1 ttl=112 time=349 ms
64 bytes from par21s20-in-f14.1e100.net (142.250.179.110): icmp_seq=2 ttl=112 time=349 ms
64 bytes from par21s20-in-f14.1e100.net (142.250.179.110): icmp_seq=3 ttl=112 time=349 ms

— google.com ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 348.510/348.837/349.250/0.308 ms

7

And the diagnosis still reports that there is no internet connectivity even if you force re-run it ?

8

Nope. Even rebooted and tried. No luck.

9

Mokay, what about: ip -4 route show table all | grep default ?

10

default via 192.168.0.1 dev eth0 proto dhcp src 192.168.0.101 metric 202

11

mokay … so let’s try displaying the default resolver IPs with

cat /usr/share/yunohost/conf/dnsmasq/plain/resolv.dnsmasq.conf

and trying to ping a few of those and seeing if at least one does work

12

This is the response I got

This file will be used to generate /etc/resolv.dnsmasq.conf

To avoid that every instance rely on the first server as primary

server, this list is shuffled during every regen-conf of dnsmasq

In the possibility where the first nameserver is down, dnsmasq

will automatically switch to the next as primary server.

List taken from

http://diyisp.org/dokuwiki/doku.php?id=technical:dnsresolver

(FR) FDN

nameserver 80.67.169.12
nameserver 2001:910:800::12
nameserver 80.67.169.40
nameserver 2001:910:800::40

(FR) ARN

nameserver 89.234.141.66
nameserver 2a00:5881:8100:1000::3

(FR) Aquilenet

nameserver 185.233.100.100
nameserver 2a0c:e300::100
nameserver 185.233.100.101
nameserver 2a0c:e300::101

(DE) CCC Berlin

nameserver 195.160.173.53

(DE) AS250

nameserver 194.150.168.168

(DE) Ideal-Hosting

nameserver 84.200.69.80
nameserver 2001:1608:10:25::1c04:b12f
nameserver 84.200.70.40
nameserver 2001:1608:10:25::9249:d69b

(DK) censurfridns

nameserver 91.239.100.100
nameserver 2001:67c:28a4::
nameserver 89.233.43.71
nameserver 2a01:3a0:53:53::

13

Yes, as said, lets try a bunch of these such as :

ping -c3 89.234.141.66
ping -c3 80.67.169.40
ping -c3 195.160.173.53
ping -c3 89.233.43.71
14

Seems to have resulted in 100% packet loss

PING 89.234.141.66 (89.234.141.66) 56(84) bytes of data.

— 89.234.141.66 ping statistics —
3 packets transmitted, 0 received, 100% packet loss, time 2040ms

PING 80.67.169.40 (80.67.169.40) 56(84) bytes of data.

— 80.67.169.40 ping statistics —
3 packets transmitted, 0 received, 100% packet loss, time 2053ms

PING 195.160.173.53 (195.160.173.53) 56(84) bytes of data.

— 195.160.173.53 ping statistics —
3 packets transmitted, 0 received, 100% packet loss, time 2053ms

PING 89.233.43.71 (89.233.43.71) 56(84) bytes of data.

— 89.233.43.71 ping statistics —
3 packets transmitted, 0 received, 100% packet loss, time 2053ms

15

Theeeen I would conclude that something funky happens on your network for some reason … I can’t see why ping 8.8.8.8 would work but not pinging other IPs …

what about ping -c3 1.1.1.1 and ping -c3 9.9.9.9 ?

16

Both showed 100% packet loss

17

Since both are showing 100% loss, in your opinion, is this an issue with my router or my ISP?

18

Yes, this is not normal to not be able to ping any IP beside google’s 8.8.8.8, this sounds super strict firewall or similar network mechanism somehow

19

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.