TUESDAY, SEPTEMBER 8, 2026
gcc — Proposed —
Sentiment 8 / 10
502 errors on gcc.gnu.org and sourceware.org
Website experienced 502 errors due to a server issue, which has now been resolved.
Haochen Jiang reported intermittent 502 bad gateway errors when trying to access gcc.gnu.org and sourceware.org. Mark Wielaard confirmed it was a server issue caused by the httpd server falling over and unable to restart automatically. The issue has since been resolved.
In the Thread
- proposer
Reported experiencing 502 bad gateway errors on gcc.gnu.org and sourceware.org, inquiring if it was a server issue or a local problem.
“I am meeting issues on visiting gcc.gnu.org (including mail archive, Bugzilla, etc.) and sourceware.org (like Binutils archive) with 502 bad gateway. Is the server totally down or it is the issue from my side?”
- other
Confirmed a server issue where the httpd server had fallen over and could not automatically restart due to a failed SSL socket setup.
“It was a server issue. The httpd server had fallen over (still investigating why) and couldn't automatically restart because it tied to also setup a listening ssl socket. Which failed because tha”
- other
Acknowledged Mark Wielaard's explanation regarding the server issue.
- other
Provided further details on the server issue.
In Details
N/A
For Context
- 502 Bad Gateway
- An HTTP status code indicating that one server on the internet received an invalid response from another server.