Configure an access control policy on the origin server to whitelist WAF IP addresses.Capture packets on the client and WAF, respectively, at the same time to check whether the origin server firewall proactively discards packets of the persistent connection to WAF.Check whether your origin server has security groups, firewalls, and security software deployed.WAF back-to-source IP addresses are blocked by the firewall on the origin server.įollow the solutions below for troubleshooting:.The WAF back-to-source IP addresses are not whitelisted or service port is not enabled in the security group.Use CC attack protection rules to block malicious traffic.If you configure Client Protocol to HTTPS, to relieve burden on backend servers, configure HTTP for Server Protocol for WAF forwarding traffic to backend servers.įor details, see Editing Server Information.To create a load balancer, see Step 1 to Step 7. For details, see Adding or Removing Backend Servers (Shared Load Balancers). You are advised to add backend server groups or create new load balancers to support the increasing service workloads, if your website is connected to a cloud WAF instance.Optimize the server configurations, including TCP network parameters and ulimit parameters.If the origin server performance is insufficient, check the origin server access logs and access traffic to analyze issues. Table 1 Troubleshooting 504 Gateway Timeout errorsĬause 1: Backend server performance issues (such as too many connections or high CPU usage)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |