You have problems before that step. Your server has no internet access or the DNS server configured isn’t working. See it says also “failure resolving archive.ubuntu.com”.
It’s not your current problem, but the instructions tell you to become the root user before running any of the commands, so you should start with sudo su to become root before doing mkdir, wget etc.
The response clearly points to a network connectivity issue, specifically a DNS resolution failure.
Try running ping -c 4 8.8.8.8 and if you get responses, check your DNS config with cat /etc/resolv.conf. If the file doesn’t contain valid nameservers, post the output here so we can troubleshoot further.
Hm with the information provided, it’s like searching for a needle in a haystack. The latest log files would help (e.g. journalctl -u NetworkManager --no-pager | tail -n 100 or with dmesg | grep -i network) Keep in mind to omit e.g. sensitive IPs.
Some guesses:
Network Interfaces down? wrong IP / subnet? ip a
Incorrect gateway or missing route? ip route
traceroute to check where the connection fails: traceroute 8.8.8.8 (install with sudo apt install traceroute)
The Network Interface is DOWN and has no IP… You could bring it up and assign it manually, but the problem should be somewhere else. You might want to check the network setup and the hardware → routers, switches, cables, ports, etc.