This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 835653 - [RFE] automatically offer to open firewalled ports
[RFE] automatically offer to open firewalled ports
Product: Fedora
Classification: Fedora
Component: abrt (Show other bugs)
x86_64 Linux
unspecified Severity low
: ---
: ---
Assigned To: abrt
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-06-26 13:52 EDT by William Bader
Modified: 2012-08-09 17:16 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-09 17:16:05 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description William Bader 2012-06-26 13:52:53 EDT
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
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; 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)
Actual results:

Fails with
fatal: libcurl failed to execute the HTTP POST transaction, explaining:  Failed connect to; 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:
Comment 1 Jiri Moskovcak 2012-08-09 17:16:05 EDT
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 which should detect that some application is trying to use a blocked port and offer to open it (as windows fw does).

Note You need to log in before you can comment on or make changes to this bug.