'fail to fetch' and DNS related issues? Topic is solved

Having issues with your DietPi installation, or, found a bug? Post it here.
brtravel
Posts: 51
Joined: Sat Sep 16, 2017 2:04 pm

Re: 'fail to fetch' and DNS related issues?

Post by brtravel »

trendy wrote: Fri Mar 27, 2020 4:35 pm Could it be that someone is blocking your access to the internet?
Are you connecting from home or office?
Maybe due to state censorship?
This is home internet, coming from a WISP. I doubt it's ISP or state censorship, and I can't fathom the motive.
brtravel
Posts: 51
Joined: Sat Sep 16, 2017 2:04 pm

Re: 'fail to fetch' and DNS related issues?

Post by brtravel »

Joulinar wrote: Fri Mar 27, 2020 4:55 pm at least I would try to open the following on a web browser on same network

http://fuzon.co.uk/meveric/pool/xu3/l/l ... _armhf.deb

At least I don't have issues with it. I can open and download the file from my side. So the Website is working and accessible from internet

same for the other 2 links

https://download.mono-project.com/repo/ ... s/stretch/
https://oph.mdrjr.net/meveric/dists/all/

Do you use any own DNS server like PiHole or something like this?

@trendy
you simply could install traceroute if you are missing it

Code: Select all

apt install inetutils-traceroute
I did have PiHole as part of this DietPi install, but I have deactivated it, and the Buster image didn't have it installed at all.

I am able to open all 3 of those links and download files on my computer on the same network. :?
brtravel
Posts: 51
Joined: Sat Sep 16, 2017 2:04 pm

Re: 'fail to fetch' and DNS related issues?

Post by brtravel »

traceroute installed fine, here's some I tried. what does !N mean? I'll start googling...

Code: Select all

root@DietPi:~# traceroute google.com
traceroute to google.com (216.239.38.120), 64 hops max
  1   192.168.1.1  2.449ms  2.832ms  4.121ms 
  2   192.168.14.1  11.712ms  7.949ms  16.074ms 
  3   192.168.13.1  16.001ms  9.857ms !N  8.056ms 
root@DietPi:~# traceroute fuzon.co.uk
traceroute to fuzon.co.uk (185.101.93.34), 64 hops max
  1   192.168.1.1  3.560ms  3.626ms  2.587ms 
  2   192.168.14.1  10.421ms  11.889ms  7.822ms 
  3   192.168.13.1  8.652ms !N  16.452ms  8.777ms 
root@DietPi:~# traceroute download.mono-project.com
traceroute to cs9.wpc.v0cdn.net (117.18.232.200), 64 hops max
  1   192.168.1.1  5.161ms  2.415ms  2.285ms 
  2   192.168.14.1  22.075ms  15.654ms  10.913ms 
  3   192.168.13.1  23.023ms !N  28.733ms  23.428ms 
root@DietPi:~# traceroute oph.mdrjr.net
traceroute to main.mdrjr.net (216.155.157.42), 64 hops max
  1   192.168.1.1  4.722ms  5.006ms  2.962ms 
  2   192.168.14.1  31.304ms  13.165ms  16.203ms 
  3   192.168.13.1  21.770ms !N  19.344ms  23.497ms 
User avatar
Joulinar
Posts: 2064
Joined: Sat Nov 16, 2019 12:49 am

Re: 'fail to fetch' and DNS related issues?

Post by Joulinar »

Hi,

honestly your trace looks quite strange. Doesn't matter what you to trace, you have 3 hops only. And all 3 a from a privat network.

https://en.wikipedia.org/wiki/Private_network

And it looks like you never going to reach the target. Do you know what 192.168.14.1 and 192.168.13.1 is about? I assume 192.168.1.1 is your internet router.

For me the trace looks like this

Code: Select all

traceroute to google.com (172.217.22.78), 64 hops max
  1   192.168.0.1  0.997ms  1.377ms  0.622ms
  2   192.168.2.1  2.029ms  1.408ms  1.477ms
  3   *  *  *
  4   *  *  *
  5   80.154.91.157  13.306ms  12.221ms  10.923ms
  6   217.0.197.229  17.690ms  15.671ms  16.970ms
  7   62.157.250.46  17.862ms  16.943ms  16.634ms
  8   *  *  *
  9   66.249.94.146  19.761ms  18.627ms  18.906ms
 10   108.170.251.209  17.685ms  17.335ms  16.382ms
 11   209.85.240.113  17.269ms  16.764ms  16.291ms
 12   172.217.22.78  17.289ms  15.951ms  15.797ms
root@DietPiVM1:~# traceroute fuzon.co.uk
traceroute to fuzon.co.uk (185.101.93.34), 64 hops max
  1   192.168.0.1  0.995ms  0.470ms  0.430ms
  2   192.168.2.1  1.834ms  1.509ms  1.116ms
  3   *  *  *
  4   *  *  *
  5   195.145.92.33  13.447ms  11.989ms  12.704ms
  6   217.5.116.42  17.404ms  17.078ms  17.300ms
  7   62.157.249.186  17.677ms  17.174ms  17.885ms
  8   129.250.6.13  25.879ms  *  *
  9   129.250.4.77  18.075ms  18.029ms  16.390ms
 10   213.198.72.154  17.311ms  17.008ms  17.001ms
 11   93.115.91.22  17.647ms  16.846ms  17.887ms
 12   5.254.68.150  18.226ms  16.858ms  16.233ms
 13   5.254.14.94  20.057ms  19.495ms  20.138ms
 14   62.141.47.20  20.522ms  20.393ms  19.923ms
 15   *  62.141.47.65  22.219ms  *
 16   *  *  *
 17   62.141.47.191  22.717ms  20.487ms  20.864ms
 18   194.125.248.134  21.252ms  20.247ms  19.790ms
 19   *  *  *
 20   185.101.93.34  23.051ms  20.278ms  21.864ms
root@DietPiVM1:~#
!N means that your machine received ICMP message "destination host unreachable". Could be as well !P or !H
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
trendy
Posts: 121
Joined: Tue Feb 25, 2020 2:54 pm

Re: 'fail to fetch' and DNS related issues?

Post by trendy »

It is not so strange, you had seen this message before when you were trying to apt-get the packages.
Talk to your ISP, they have messed up something and they are rejecting these IP addresses for no apparent reason.
User avatar
Joulinar
Posts: 2064
Joined: Sat Nov 16, 2019 12:49 am

Re: 'fail to fetch' and DNS related issues?

Post by Joulinar »

honestly I would go to find out what 192.168.14.1 and 192.168.13.1 is. These are 2 privat IP's and trace stopped somewhere there.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
trendy
Posts: 121
Joined: Tue Feb 25, 2020 2:54 pm

Re: 'fail to fetch' and DNS related issues?

Post by trendy »

It's common for ISPs, especially WISPs to use private IPs in their backbone. That is not a problem.
User avatar
Joulinar
Posts: 2064
Joined: Sat Nov 16, 2019 12:49 am

Re: 'fail to fetch' and DNS related issues?

Post by Joulinar »

well but he never reached the target on his trace
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
trendy
Posts: 121
Joined: Tue Feb 25, 2020 2:54 pm

Re: 'fail to fetch' and DNS related issues?

Post by trendy »

And that is why I advised him to contact his ISP.
If he was reaching the destination we wouldn't be discussing the issue here.
User avatar
Joulinar
Posts: 2064
Joined: Sat Nov 16, 2019 12:49 am

Re: 'fail to fetch' and DNS related issues?

Post by Joulinar »

But still the question why he is able to access the website from another computer on the same network while the SBC is failing?
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Post Reply