Description of problem: I went through the abort procedure to file a bug report, and the last step failed with a fatal error in libcurl. I remembered that I had blocked almost every port with the firewall. Someone using Fedora 17 at home or on a laptop should block as many ports as possible for security and would be unlikely to run a server on port 443. I opened 443 and then it worked. This isn't really a bug but a request for abrt to show a better diagnostic when port 443 is blocked, or even offer to open the port. For example, the printer administration under system -> administration -> printing offers to open ports when you scan for network printers. --- Running report_Bugzilla --- Logging into Bugzilla at https://bugzilla.redhat.com Checking for duplicates Creating a new bug New bug id: 835650 Adding attachments to bug 835650 fatal: libcurl failed to execute the HTTP POST transaction, explaining: Failed connect to bugzilla.redhat.com:443; Connection refused (exited with 1) Version-Release number of selected component (if applicable): Fedora 17 How reproducible: Every time Steps to Reproduce: 1. Block port 443 on the firewall 2. Report a bug with abrt (provided that abrt has already captured something to send) 3. Actual results: Fails with fatal: libcurl failed to execute the HTTP POST transaction, explaining: Failed connect to bugzilla.redhat.com:443; Connection refused (exited with 1) Expected results: Fails with a message that says that you need to open port 443 on the firewall or else says that you have 443 blocked and asks if it should open it. Additional info:
Actually what you saying would mean that such functionality sould be in every application which uses network. I think it should go into some central point managing the firewall (like https://fedoraproject.org/wiki/FirewallD) which should detect that some application is trying to use a blocked port and offer to open it (as windows fw does).