fedora-infrastructure

#8498 proxy01.fedoraproject.org net down?
Closed: Fixed by petersen. Opened by petersen.

Closed: Fixed
Reopen Issue

I can't access kojiweb or kojihub via proxy01.fedoraproject.org.

$ host koji.fedoraproject.org
koji.fedoraproject.org has address 209.132.181.16
koji.fedoraproject.org has address 209.132.181.15
$ host 209.132.181.16
16.181.132.209.in-addr.arpa domain name pointer proxy01.fedoraproject.org.
$ ping -c3 proxy01.fedoraproject.org | grep From
From proxy01.fedoraproject.org (209.132.181.16) icmp_seq=1 Destination Port Unreachable
From proxy01.fedoraproject.org (209.132.181.16) icmp_seq=2 Destination Port Unreachable
From proxy01.fedoraproject.org (209.132.181.16) icmp_seq=3 Destination Port Unreachable
$ curl https://209.132.181.16/koji
curl: (7) Failed to connect to 209.132.181.16 port 443: Connection refused

This doesn't happen with proxy10.fedoraproject.org (209.132.181.15).

I think it started happening roughly 12+hours ago

it may have fixed itself in the time with this ticket

[smooge@smoogen-laptop ~]$ ping proxy01.fedoraproject.org
PING proxy01.fedoraproject.org (209.132.181.16) 56(84) bytes of data.
64 bytes from proxy01.fedoraproject.org (209.132.181.16): icmp_seq=1 ttl=42 time=75.5 ms
64 bytes from proxy01.fedoraproject.org (209.132.181.16): icmp_seq=2 ttl=42 time=74.7 ms
64 bytes from proxy01.fedoraproject.org (209.132.181.16): icmp_seq=3 ttl=42 time=82.1 ms
64 bytes from proxy01.fedoraproject.org (209.132.181.16): icmp_seq=4 ttl=42 time=77.0 ms
^C
--- proxy01.fedoraproject.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3318ms
rtt min/avg/max/mdev = 74.714/77.370/82.181/2.897 ms

and 

[smooge@smoogen-laptop ~]$ curl https://proxy01.fedoraproject.org/koji
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
<hr>
<address>Apache Server at proxy01.fedoraproject.org Port 443</address>
</body></html>

If it is still not working for you then there is a network block somewhere in the path before Phoenix and you.. a traceroute will be needed.

Metadata Update from @smooge:
- Issue priority set to: Waiting on Reporter (was: Needs Review)

It was up and pinging and sshable from here last night... so yeah, sounds like a route between was having problems?

Dunno, it was working okay for me yesterday again: I didn't have any trouble connecting to proxy10, so...

Metadata Update from @petersen:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
High
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.