As I originally (probably erroneously) reported to abrt: [1] --- Running report_uReport --- Failed to upload uReport to the server 'https://retrace.fedoraproject.org/faf' with curl: Failed to connect to retrace.fedoraproject.org port 443 after 133856 ms: Could not connect to server Error: curl_easy…

Yes, this is part of a planned datacenter move. See https://www.fedorastatus.org/ Things have taken longer than expected due to bad weather in the region where the new datacenter is. ;( Hopefully it will be back soon… kevin

Now that FAF appears to be back, I still don’t appear to be able to generate FAF traces for old bugs, at least via gnome-abrt-1.4.3-8.fc43: [1] --- Running report_uReport --- Server responded with an error: 'Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: Lis…

I am unable to submit FAF reports

Ask Fedora

decathorpe (Fabio Valentini) December 9, 2025, 4:30pm 2

→ https://status.fedoraproject.org
→ https://pagure.io/fedora-infrastructure/issue/12955

notably:

retrace/abrt/faf will be down and not accepting user reports

Why does DebugInfoD lack symbols for DotNet packages?

Topic		Replies	Views
Can, and if so, how does, one submit an abrt report to RHBZ via the (abrt) CLI? Ask Fedora abrt	3	149	August 30, 2025
Can't report bug anymore / Fedora 40 Ask Fedora	8	375	September 26, 2024
ABRT Reporting - Lots of "Reporting is disabled because the generated backtrace has low information value Ask Fedora kde , workstation , f41	2	231	April 25, 2025
Abrt cannot connect to retrace server Ask Fedora f32	0	849	September 2, 2020
Can GNOME Abrt's "not enough information" error be bypassed? Ask Fedora abrt , bugzilla , f42	5	180	May 26, 2025

I am unable to submit FAF reports

Related topics