If Access Progress/Status for a website you have added to WAF is Inaccessible, the connection between WAF and the website domain name or IP address fails to be established.
Refer to Figure 1 and Table 1 to fix connection failures.
Possible Cause |
Solution |
---|---|
Cause 1: Access Status for Domain Name/IP Address not updated |
In the Access Status column for the website, click |
Cause 2: Website access traffic not enough for WAF to consider the website accessible NOTICE:
After you connect a website to WAF, the website is considered accessible only when WAF detects at least 20 requests to the website within 5 minutes. |
|
Cause 3: Incorrect domain name or IP address settings |
Check domain name or IP address settings. If there are incorrect settings for the domain name or IP address, remove this domain name or IP address from WAF and add it to WAF again. |
Cause 4: No load balancer configured for the dedicated WAF instance or no EIP bound to the load balancer configured for the dedicated WAF instance |
|
Cause 5: Incorrect load balancer configured or incorrect EIP bound to the load balancer |
|
Refer to Figure 2 and Table 2 to fix connection failures.
Possible Cause |
Solution |
---|---|
Cause 1: Access Status for Domain Name/IP Address not updated |
In the Access Status column for the website, click |
Cause 2: Website access traffic not enough for WAF to consider the website accessible NOTICE:
After you connect a website to WAF, the website is considered accessible only when WAF detects at least 20 requests to the website within 5 minutes. |
|
Cause 3: Incorrect domain name or IP address settings |
Check whether the domain name or IP address settings are correct. If there are incorrect settings, remove the domain name or IP address from WAF and add it to WAF again. |