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

WAF not working on port 80

I'm getting crazy with WAF on XG 18: it works on every port but not on port 80. The first rule on top is the WAF rule. If I use port 80 as listening port, I cannot reach the webserver, but if I use any other port, it works perfectly. What should I check?



This thread was automatically locked due to age.
Parents
  • Can you check system access - administration - device access if you have enabled the user portal (and admin services) on the wan interface. Can you check by disabling them?  

  • User portal was enabled on WAN, I was already happy to have the solution but... still doesn't work

  • The user portal redirects http to https. It does not let you redirect http to https in WAF for that reason as you get an error message. Did you create a path spefic route in the WAF rule and webserver destination you created? Check the webserver section. Check the WAF and corresponding NAT rule again.  Enable logging.

    Leave user portal on the WAN disabled and look at log viewer to see what happens to the traffic send from your src IP and src Port. Check if the correct firewall rules nd NAT rules are shown in the log. The URL call should also be visible under webserver protection in the log viewer. 

    You have created a rule one before last block all with logging?

    Otherwise share more info on your WAF rule.

Reply
  • The user portal redirects http to https. It does not let you redirect http to https in WAF for that reason as you get an error message. Did you create a path spefic route in the WAF rule and webserver destination you created? Check the webserver section. Check the WAF and corresponding NAT rule again.  Enable logging.

    Leave user portal on the WAN disabled and look at log viewer to see what happens to the traffic send from your src IP and src Port. Check if the correct firewall rules nd NAT rules are shown in the log. The URL call should also be visible under webserver protection in the log viewer. 

    You have created a rule one before last block all with logging?

    Otherwise share more info on your WAF rule.

Children
No Data