HAproxy 1.5 Standalone LoadBalancing

Having read some older posts on Load Balancing, I installed version 1.5.9 of HAproxy on my Yosemite server.

Although HAproxy seems to run, and I can start my individual nodes by entering the port they run on,
I get nothing when I just enter the URL www.posterq.com without a port number.

My HAproxy config is;

[code]global
log 127.0.0.1 local0
maxconn 4096
daemon

defaults
log global
mode http
option httplog
option dontlognull
retries 3
option redispatch
maxconn 2000
timeout connect 5000
timeout client 50000
timeout server 50000

frontend http-in
bind *:80
acl is_myapp1 hdr_end(host) -i www.posterq.com
acl is_myapp2 hdr_end(host) -i myapp2.mydomain.com

    use_backend myapp1pool if is_myapp1
    use_backend myapp2pool if is_myapp2
    default_backend myapp1pool

backend myapp1pool
option httpchk OPTIONS /
option forwardfor
option http-server-close
cookie serverid insert indirect nocache
server node1 localhost:8080 check cookie node1
server node2 localhost:8081 check cookie node2
server node3 localhost:8082 check cookie node3

backend myapp2pool
option httpchk OPTIONS /
option forwardfor
option http-server-close
cookie serverid insert indirect nocache
server node1 localhost:8090 check cookie node1
server node2 localhost:8091 check cookie node2
server node3 127.0.0.1:8092 check cookie node3

listen haproxyapp_admin:9100 127.0.0.1:9100
mode http
stats uri /

[/code]

when I start HAproxy with these settings the web interface on port 9100 gives me a status screen that looks like its working
but entering the URL posterq.com does not give me anything on other devices than the server on which HAproxy runs.

Can anyone help me get this fixed?

Thanks in advance,

Is there something else running on port 80? Is haproxy running as root? If not, it may not have permissions to bind to port 80. Is there a firewall running that might be blocking port 80?

@Kevin Windham
Nothing else was running, but your Firewall question made me try switching it off for a minute and then it did work, thanks!
A bit odd, as Haproxy was already getting permissions to get inbound connections, but I think it solved it.