Fedora 37 break: Software app resolves mirrors.fedoraproject.org to 192.168.1.103

Ask Fedora
1

Just upgraded to Fedora 37 and something weird is happening with the Software app. It can’t refresh package lists or display anything. After booting I get a notification that it failed to install a system update, but the error message shows it’s trying to hit mirrors.fedoraproject.org for packages, but curl exits with error 7 saying it can’t connect to 192.168.1.103:5555.

I do not have a proxy configured in Gnome, and I can’t find any proxy settings set in /etc/yum.repos.d/.

nslookup resolves the domain just fine.

[brady@fedora ~]$ nslookup mirrors.fedoraproject.org
Server:		127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
mirrors.fedoraproject.org	canonical name = wildcard.fedoraproject.org.
Name:	wildcard.fedoraproject.org
Address: 8.43.85.73
Name:	wildcard.fedoraproject.org
Address: 38.145.60.20
Name:	wildcard.fedoraproject.org
Address: 209.132.190.2
Name:	wildcard.fedoraproject.org
Address: 152.19.134.142
Name:	wildcard.fedoraproject.org
Address: 152.19.134.198
Name:	wildcard.fedoraproject.org
Address: 67.219.144.68
Name:	wildcard.fedoraproject.org
Address: 140.211.169.196
Name:	wildcard.fedoraproject.org
Address: 38.145.60.21
Name:	wildcard.fedoraproject.org
Address: 8.43.85.67
Name:	wildcard.fedoraproject.org
Address: 2600:2701:4000:5211:dead:beef:fe:fed3
Name:	wildcard.fedoraproject.org
Address: 2604:1580:fe00:0:dead:beef:cafe:fed1
Name:	wildcard.fedoraproject.org
Address: 2605:bc80:3010:600:dead:beef:cafe:fed9
Name:	wildcard.fedoraproject.org
Address: 2620:52:3:1:dead:beef:cafe:fed7
Name:	wildcard.fedoraproject.org
Address: 2620:52:3:1:dead:beef:cafe:fed6
2

My download (upgrade) stopped at 43%.
next day

ping wildcard.fedoraproject.org -v4
PING  (18.159.254.57) 56(84) bytes of data.
64 bytes from ec2-18-159-254-57.eu-central-1.compute.amazonaws.com (18.159.254.57): icmp_seq=1 ttl=48 time=25.0 ms

But: 'aborted by applications callback for http://ftp.cc.uoc.gr/fedora/linux/updates/37/Everything/x86_64/Packages/…

3

192.168… are local addresses. I’m guessing you have an entry for it in /etc/hosts to point it to a resource on your local network. If you remove that entry, it should pull from the public mirrors again.

Alternatively, you might have a proxy (SOCKS5, https, etc.) set to that address and that proxy is having an issue.

4

I do not have any host entries for that domain, or a socks proxy configured.

5

The issue seems to have resolved itself… software app is working now.