Everything works fine until I get to the download of either of these. Then it says it cannot connect to the download site. Internet connection is fine as it downloaded everything before this step. Ideas?
Hi,
Many thanks for your report.
Pls can you be a little bit more specific on your issue.
Do you have some error messages or screenshots you can past?
- Command: Connection test:
│ https://download.nextcloud.com/server/releases/nextcloud-17.0.1.tar.bz2
│ - Exit code: 4
│ - DietPi version: v6.28.0 (MichaIng/master) | HW_MODEL:3 | HW_ARCH:2 | DISTRO:5
│ - Image creator: DietPi Core Team
│ - Pre-image: Raspbian Lite
│
│ Log file content:
│ Spider mode enabled. Check if remote file exists.
│ --2020-01-14 00:51:32–
│ https://download.nextcloud.com/server/releases/nextcloud-17.0.1.tar.bz2
│ Resolving download.nextcloud.com (download.nextcloud.com)… failed: Connection timed
│ out.
│ wget: unable to resolve host address ‘download.nextcloud.com’
pls can you run the following 2 commands an past the output
ping -c 1 download.nextcloud.com
ping -4 -c 1 download.nextcloud.com
root@DietPi:~# ping -c 1 download.nextcloud.com
PING download.nextcloud.com(download.nextcloud.com (2a01:4f8:130:32f1::52)) 56 data bytes
64 bytes from download.nextcloud.com (2a01:4f8:130:32f1::52): icmp_seq=1 ttl=44 time=127 ms
— download.nextcloud.com ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 127.376/127.376/127.376/0.000 ms
root@DietPi:~# ping -4 -c 1 download.nextcloud.com
PING download.nextcloud.com (176.9.217.52) 56(84) bytes of data.
64 bytes from download.nextcloud.com (176.9.217.52): icmp_seq=1 ttl=49 time=122 ms
— download.nextcloud.com ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 122.481/122.481/122.481/0.000 ms
weird. yesterday you reported an issue that you are not able to resolve the host name.
unable to resolve host address ‘download.nextcloud.com’
but today you are able to resolve the name for both IPv4 as well as IPv6 as shown in your test.
PING IPv4 download.nextcloud.com (176.9.217.52)
PING IPv6 download.nextcloud.com (2a01:4f8:130:32f1::52)
So connection should work.
pls can you try to restart your software installation!
I restarted and get the same error. It’s very odd.
well you could try to tweak it by entering the IPv4 as well as IPv6 address to your /etc/hosts file. This should avoid the DNS resolving error at least.
BTW what DNS/Nameserver you are using. Your own one or a public like Google or Cloudflare
I am using my own - pihole, however I have it disabled while doing this. Should I try another?
well maybe for testing you could switch to Google or Cloudflare. But usually PiHole should show blocked request. As well you could go to whitelist download.nextcloud.com
within PiHole. Or tweaking /etc/hosts as another option
I’m a bit of a noob.
How do I edit that etc/hosts?
You can do the following
nano /etc/hosts
add the following two lines
176.9.217.52 download.nextcloud.com
2a01:4f8:130:32f1::52 download.nextcloud.com
Save the file. To be on save side, reboot your system. Now your system should resolve download.nextcloud.com
by using the /etc/hosts instead of asking PiHole
Well I made progress looked like the hosts file worked and then ran into this -
https://raw.githubusercontent.com/MichaIng/DietPi/master/.conf/dps_114/lighttpd.nextcl
│ oud.conf
│ Resolving raw.githubusercontent.com (raw.githubusercontent.com)… failed: Connection
Maybe I am not meant to do this LOL
did you tried to change your DNS Server to 8.8.8.8 ??
If yes and you still facing this issues, we would need to continue adding IP’s to the /etc/hosts file
well 8.8.8.8 didn’t help LOL
what IP addresses next?
your system getting more and more weird
Anyway let’s do the following to enable you to find out IP addresses yourselves
Pls install the small package dnsutils. It will install the tool nslookup which can be uses to check DNS and what will be resolved.
G_AGI dnsutils
once done you can run the command
nslookup raw.githubusercontent.com
your preferred DNS server should now answer the following
root@DietPi4:~# nslookup raw.githubusercontent.com
Server: 192.168.0.11 <--- my own DNS serer
Address: 192.168.0.11#53
Non-authoritative answer:
raw.githubusercontent.com canonical name = github.map.fastly.net.
Name: github.map.fastly.net
Address: 151.101.64.133 <--- DNS serer feedback
Name: github.map.fastly.net
Address: 151.101.128.133
Name: github.map.fastly.net
Address: 151.101.192.133
Name: github.map.fastly.net
Address: 151.101.0.133
root@DietPi4:~#
take one of the IP addresses and put it into your /etc/hosts. If you have IPv6 working, you will receive IPv6 addresses as well.
I’m thinking this isn’t meant to be for some reason
yes there is something strange on your system. You have DNS issues during installation but testing ping is working fine. I still don’t understand why this happen. Maybe you could disable IPv6 within dietpi-config Network settings and test again.