That’s not a valid repository link (download.example is an example URL). Have you made any changes to your repository files in /etc/yum.repos.d/? Can you please post the contents of the /etc/yum.repos.d/fedora.repo file?
When I ping fedoraproject.org I do get a response.
— fedoraproject.org ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
Similarly pasting anything starting with mirrors.fedoraproject.org into my browser address bar comes back:
I pinged mirrors.fedoraproject.org from a RaspberryPi and from Fedora34 (a Qubes VM on my laptop). Both of these DO get a response.
I have never seen a problem like this before. My Fedora36-desktop is selectively ignoring mirrors.fedoraproject.org.
All devices access the same Internet account and have the same IP address. The desktop is a cable connection to the modem-router, the Pi and laptop are WiFi.
I have a few school projects going on which access port 3000 & ports 8080 - 8086. These projects are closed right now. Could this have anything to do with blocking access to mirrors.fedoraproject.org?
I live in southeastern Colorado, and ping has no trouble finding mirrors.fedoraproject.org. If this hasn’t cleared up, try using traceroute instead to see how far the pings are getting.
Are you sure something hasn’t changed in your network settings firewall selinux router.Can you surf the internet and have you checked fedora’s mirror sites to see if one works.
If @ilikelinux’s suggestion doesn’t help, try the traceroute again and see if it’s stalling at the same point. If so, the problem is between them and what should be the next hop, and you may need to ask the technical contact at twelve99.net for help.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31545
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;mirrors.fedoraproject.org. IN A
;; ANSWER SECTION:
mirrors.fedoraproject.org. 295 IN CNAME wildcard.fedoraproject.org.
wildcard.fedoraproject.org. 55 IN A 140.211.169.196
wildcard.fedoraproject.org. 55 IN A 8.43.85.73
wildcard.fedoraproject.org. 55 IN A 8.43.85.67
wildcard.fedoraproject.org. 55 IN A 67.219.144.68
wildcard.fedoraproject.org. 55 IN A 152.19.134.198
wildcard.fedoraproject.org. 55 IN A 209.132.190.2
wildcard.fedoraproject.org. 55 IN A 152.19.134.142
wildcard.fedoraproject.org. 55 IN A 35.81.0.97
wildcard.fedoraproject.org. 55 IN A 38.145.60.20
wildcard.fedoraproject.org. 55 IN A 38.145.60.21
;; Query time: 35 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Jun 09 08:21:50 CDT 2022
;; MSG SIZE rcvd: 237
resolvectl status
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (enp5s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 64.59.176.13
DNS Servers: 64.59.176.13 64.59.177.226 2001:4e8:0:4002::14
2001:4e8:0:4012::14
DNS Domain: wp.shawcable.net
Link 3 (virbr0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
mirrors.fedoraproject.org: 80.239.156.215
-- Information acquired via protocol DNS in 785us.
-- Data is authenticated: yes; Data was acquired via local or encrypted transport: yes
-- Data from: synthetic
systemctl status systemd-resolved.service
systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled;>
Active: active (running) since Tue 2022-06-07 18:16:40 CDT; 1 day 14h ago
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://www.freedesktop.org/wiki/Software/systemd/writing-network->
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver>
Main PID: 815 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 9403)
Memory: 3.7M
CPU: 14.007s
CGroup: /system.slice/systemd-resolved.service
└─ 815 /usr/lib/systemd/systemd-resolved
Jun 07 18:16:40 fedora-main-drive systemd-resolved[815]: Positive Trust Anchors:
Jun 07 18:16:40 fedora-main-drive systemd-resolved[815]: . IN DS 20326 8 2 e06d>
Jun 07 18:16:40 fedora-main-drive systemd-resolved[815]: Negative trust anchors>
Jun 07 18:16:40 fedora-main-drive systemd-resolved[815]: Using system hostname >
Jun 07 18:16:40 fedora-main-drive systemd[1]: Started systemd-resolved.service >
Jun 07 18:17:24 fedora-main-drive systemd-resolved[815]: enp5s0: Bus client set>
Jun 07 18:17:24 fedora-main-drive systemd-resolved[815]: enp5s0: Bus client set>
Jun 07 18:17:24 fedora-main-drive systemd-resolved[815]: enp5s0: Bus client set>
Jun 07 18:17:25 fedora-main-drive systemd-resolved[815]: enp5s0: Bus client set>
Jun 08 23:28:22 fedora-main-drive systemd-resolved[815]: Flushed all caches.
lines 1-25/25 (END)
I think this could be a routing issue caused by twelve99.net. Why would they route you from chicago to NY to London to Paris to Frankfurt and then to nowhere…?
I haven’t used tor in years but I know it bounces all over the world finding servers that can’t be traced back to your ip.If one of those servers is no longer working it will fail until you reset the tor settings.You might try to disable your firewall and try fedora again and if it works you will know where to trouble shoot by removing whatever is blocking you.