Why Is My Domain Name or IP Address Inaccessible?
Symptoms
If Access Progress for a website you have added to WAF is Accessible, the connection between WAF and the website domain name or IP address has been established.
- WAF automatically checks the access status of protected websites every hour. If WAF detects that a protected website has received 20 access requests within 5 minutes, it considers that the website has been successfully connected to WAF.
- By default, WAF checks only the Access Status of domain names added or updated over the last two weeks. If a domain name was added to WAF two weeks ago and has not been modified in the last two weeks, you can click in the Access Progress column to refresh the progress.
- Cloud - CNAME: protects your web applications that have domain name and are deployed on any clouds or in on-premises data centers.
- Cloud - Load balancer: protects your web applications that are deployed on Huawei Cloud and accessible over domain names or IP addresses.
- Dedicated: protects your web applications that are deployed on Huawei Cloud and accessible over domain names or IP addresses.
Troubleshooting and Solutions for Cloud WAF Instances
Refer to Figure 1 and Table 1 to fix connection failures for websites protected in cloud mode.
Possible Cause |
Solution |
---|---|
Cause 1: Access Status of Protected Website not updated |
In the Access Status column for the protected website, click to update the status. |
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 settings |
NOTICE:
WAF can protect the website using the following types of domain names:
Domain names example.com and www.example.com are different. Ensure that correct domain names are added to WAF. Perform the following steps to ensure that the domain name settings are correct.
For details, see Testing WAF. If there are incorrect domain name settings, remove the domain name from WAF and add it to WAF again. |
Cause 4: DNS record or the back-to-source IP addresses of proxies not configured |
Check whether the website connected to WAF uses proxies such as advanced anti-DDoS, CDN, and cloud acceleration service.
For details, see Connecting a Domain Name to WAF. |
Cause 5: Incorrect DNS record or proxy back-to-source address |
Perform the following steps to check whether the domain name CNAME record takes effect:
If the CNAME record fails to take effect, modify the DNS record or back-to-source address. For details, see Connecting a Domain Name to WAF. |
Troubleshooting and Solutions for Dedicated WAF
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 to update the status. |
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 by referring to View the basic information about the domain name. 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 |
|
Troubleshooting and Solutions for Cloud ELB-Access WAF
Refer to Figure 3 and Table 3 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 protected website, click to update the status. |
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 |
View the basic information about the domain name and 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. |
Service Interruption Check FAQs
- How Do I Troubleshoot 404/502/504 Errors?
- Why Is My Domain Name or IP Address Inaccessible?
- How Do I Handle False Alarms as WAF Blocks Normal Requests to My Website?
- Why Does WAF Block Normal Requests as Invalid Requests?
- Why Is the Handle False Alarm Button Grayed Out?
- How Do I Whitelist IP Address Ranges of Cloud WAF?
- What Is the Connection Timeout Duration of WAF? Can I Manually Set the Timeout Duration?
- How Do I Solve the Problem of Excessive Redirection Times?
- Why Are HTTPS Requests Denied on Some Mobile Phones?
- How Do I Fix an Incomplete Certificate Chain?
- Why Does My Certificate Not Match the Key?
- Why Am I Seeing Error Code 418?
- Why Am I Seeing Error Code 523?
- Why Does the Website Login Page Continuously Refreshed After a Domain Name Is Connected to WAF?
- Why Does the Requested Page Respond Slowly After the HTTP Forwarding Policy Is Configured?
- How Can I Upload Files After the Website Is Connected to WAF?
- Why Am I Seeing Error Code 414 Request-URI Too Large?
- What Do I Do If the Protocol Is Not Supported and the Client and Server Do Not Support Common SSL Protocol Versions or Cipher Suites?
- Why Cannot I Access the Dedicated Engine Page?
- Why Is the Bar Mitzvah Attack on SSL/TLS Detected?
- What Do I Do If the CPU Usage of the Origin Server Reaches 100%?
- Why Cannot the Vulnerability Scanning Tool Scan Real Services on My Website Protected with WAF?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore