Skip to main content
Unix & Linux

Return to Answer

The firewall-cmd command was updated and now you must have the /tcp added to the port for this to work (+grammer/formatting)
Source Link
edit approved Mar 18, 2016 at 15:45
mdw7326
edit approved Mar 18, 2016 at 15:45
mdw7326
  • 113
  • 4

Apache requests were being blocked on the firewall. The following commands were run to allow all requests through the firewall;

firewall-cmd --zone=public --add-port=80firewall.

firewall-cmd --reload

firewall-cmd --zone=public --add-port=80/tcp
firewall-cmd --reload

It should also be possible to use the following command instead of allowing port 80;

firewall-cmd --add-service=http

firewall-cmd --reload

firewall-cmd --add-service=http
firewall-cmd --reload

Apache requests were being blocked on the firewall. The following commands were run to allow all requests through the firewall;

firewall-cmd --zone=public --add-port=80

firewall-cmd --reload

It should also be possible to use the following command instead of allowing port 80;

firewall-cmd --add-service=http

firewall-cmd --reload

Apache requests were being blocked on the firewall. The following commands were run to allow all requests through the firewall.

firewall-cmd --zone=public --add-port=80/tcp
firewall-cmd --reload

It should also be possible to use the following command instead of allowing port 80;

firewall-cmd --add-service=http
firewall-cmd --reload
Source Link
Chris Davidson
Chris Davidson
  • 1.5k
  • 1
  • 10
  • 12

Apache requests were being blocked on the firewall. The following commands were run to allow all requests through the firewall;

firewall-cmd --zone=public --add-port=80

firewall-cmd --reload

It should also be possible to use the following command instead of allowing port 80;

firewall-cmd --add-service=http

firewall-cmd --reload