Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

To answer my own question.

A small SELinux alert box popped up lower left corner of the screen, which I haven't noticed before (although there have been a number of alerts).

Clicking on the details button gives suggested solutions:

SELinux is preventing httpd from name_connect access on the tcp_socket port 1111.

*****  Plugin connect_ports (85.9 confidence) suggests   *********************

If you want to allow httpd to connect to network port 1111
Then you need to modify the port type.
Do
# semanage port -a -t PORT_TYPE -p tcp 1111
    where PORT_TYPE is one of the following: dns_port_t, dnssec_port_t, http_port_t, kerberos_port_t, ocsp_port_t.

...

*****  Plugin catchall_boolean (7.33 confidence) suggests   ******************

If you want to allow httpd to can network connect
Then you must tell SELinux about this by enabling the 'httpd_can_network_connect' boolean.
You can read 'None' man page for more details.
Do
setsebool -P httpd_can_network_connect 1