Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 2185 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

WAF not working on port 80

Pablo_CV

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.
  • 0

    I don't know, you are using XG, and this is the UTM forum  Stuck out tongue

    Besides, I'm not proficient at all with XG, sorry I can't help with WAF on that platform.

    With anything else though, I'd check your logs related to WAF and see if it gives any errors.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • 0

    Moved to the correct Forum.

    Is there any NAT Rule using TCP/80 ?

    If a post solves your question use the 'Verify Answer' button.

    Ryzen 5600U + I226-V (KVM) v20 GA @ Home

    XG 115w Rev.3 8GB RAM v19.5 MR3 @ Travel Firewall

  • 0

    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?  

  • 0 in reply to Fred_B

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

  • 0

    Use packet capture tool to filter incoming traffic to see what happens to inbound traffic. See if traffic reaches to firewall and if it's forwarded which firewall rule an NAT rule is applied. Try "host source_client_ip_address and port 80" for packet capture filter. do not include double quotations and post the results here for further investigations.

  • 0 in reply to Pablo_CV

    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.

  • +1 in reply to Mojtaba Roustaei

    Nice tool... again if in the rule I set port 81, packet is captured and the WAF rule is applied. With port 80 nothing happens.

  • 0 in reply to Pablo_CV

    so no packages? What happens when you enable User portal on the WAN and try to connect with http on your wan IP? It should redirect you to https. If that doesn't happen there is something in front of the XG.

  • 0 in reply to Fred_B

    No packages even if I enable user portal on WAN... really strange. In front of the XG there is our ISP's router, but we have 2 public IPs, one for the router and one for the firewall therefore it should filter nothing

Unfiltered HTML