Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 20 replies
  • Subscribers 2 subscribers
  • Views 50210 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Web Application Firewall - Real webserver "in error"

thenetstriker
I' am trying to setup an Web Application Firewall on my Sophos UTM 9. I've configured some real webservers and one virtual webserver. In the virtual webserver on the left always appears an icon that says "in error". I get nothing in the logs. What could cause this problem?


This thread was automatically locked due to age.
Parents
  • 0

    I ran into this after a power failure at my house.  For some reason, it would not bind port 80 to my IPv6 address:

    # /var/mdw/scripts/reverseproxy restart
    :: Restarting reverseproxy
    reverseproxy not running
    :: Starting reverseproxy
    [Thu Jun 01 12:35:00.997875 2017] [core:warn] [pid 3973:tid 1435722960] AH00111: Config variable ${URLHardening_HTTP_Hostname} is not defined
    [Thu Jun 01 12:35:00.997986 2017] [core:warn] [pid 3973:tid 1435722960] AH00111: Config variable ${URLHardening_HTTP_Hostname} is not defined
    [Thu Jun 01 12:35:01.000681 2017] [core:warn] [pid 3973:tid 1435722960] AH00111: Config variable ${URLHardening_HTTP_Hostname} is not defined
    [Thu Jun 01 12:35:01.000718 2017] [core:warn] [pid 3973:tid 1435722960] AH00111: Config variable ${URLHardening_HTTP_Hostname} is not defined
    AH00112: Warning: DocumentRoot [/var/www/REF_RevFroCcsweb01] does not exist
    AH00112: Warning: DocumentRoot [/var/www/REF_RevFroCcsweb01] does not exist
    (99)Cannot assign requested address: AH00072: make_sock: could not bind to address [2606:6000:5fc0:5:44bd:ad76:3adc:27bd]:80
    no listening sockets available, shutting down
    AH00015: Unable to open logs

     

    I was able to work around this by disabling IPv6 temporarily, then restarting the reverseproxy service again.

    Has anyone else seen this?

Reply
  • 0

    I ran into this after a power failure at my house.  For some reason, it would not bind port 80 to my IPv6 address:

    # /var/mdw/scripts/reverseproxy restart
    :: Restarting reverseproxy
    reverseproxy not running
    :: Starting reverseproxy
    [Thu Jun 01 12:35:00.997875 2017] [core:warn] [pid 3973:tid 1435722960] AH00111: Config variable ${URLHardening_HTTP_Hostname} is not defined
    [Thu Jun 01 12:35:00.997986 2017] [core:warn] [pid 3973:tid 1435722960] AH00111: Config variable ${URLHardening_HTTP_Hostname} is not defined
    [Thu Jun 01 12:35:01.000681 2017] [core:warn] [pid 3973:tid 1435722960] AH00111: Config variable ${URLHardening_HTTP_Hostname} is not defined
    [Thu Jun 01 12:35:01.000718 2017] [core:warn] [pid 3973:tid 1435722960] AH00111: Config variable ${URLHardening_HTTP_Hostname} is not defined
    AH00112: Warning: DocumentRoot [/var/www/REF_RevFroCcsweb01] does not exist
    AH00112: Warning: DocumentRoot [/var/www/REF_RevFroCcsweb01] does not exist
    (99)Cannot assign requested address: AH00072: make_sock: could not bind to address [2606:6000:5fc0:5:44bd:ad76:3adc:27bd]:80
    no listening sockets available, shutting down
    AH00015: Unable to open logs

     

    I was able to work around this by disabling IPv6 temporarily, then restarting the reverseproxy service again.

    Has anyone else seen this?

Children
No Data
Unfiltered HTML