Skip to main content

Unable to Access Page

When a page is not accessible, it may be caused by various reasons. This article lists common scenarios and diagnostic methods to help quickly locate and resolve the issue.

Basic Checks​

Before diving into analyzing the issue, please confirm the following basics are correct:

  1. URL accuracy

    • Ensure that the entered page URL is correct, including the protocol (http:// or https://) and whether the path is complete.

  2. Network environment

    • Try changing the network (such as using a mobile hotspot) or device to rule out local network or device issues.

  3. Service status

    • Check the container's running status: Use the docker ps -a command to confirm if the container is running.
    • View microservice container logs: Use the docker logs $(docker ps | grep community | awk '{print $1}') command to check the microservice logs, which should normally be INFO level log outputs.
    • If the container is not running or there are many errors in the health check logs, you can try restarting the HAP service by running the bash service.sh restartall command in the directory where the manager is located.

Common Issues and Solutions​

Network Issues​

Common Prompts​

  • Unable to access this website.
  • Prompt to check network connection, proxy server, or firewall.
  • Error message ERR_CONNECTION_TIMED_OUT.

Possible Causes​

  • Cloud host security group has not opened specific ports.
  • Enterprise network firewall restricts external access.
  • The server's local firewall (such as firewalld) has not opened necessary ports.

Solutions​

  1. Check cloud service's network security group (applicable to cloud servers)
    • Log in to the cloud service management platform and check the security group rules bound to the instance.
    • Check the inbound rules to ensure the required ports for services are open and allow access.
  2. Check enterprise network firewall
    • Contact the IT department to confirm firewall rules and ensure external traffic is not restricted.
  3. Check server firewall configuration
    • Ensure firewalld is in a closed state.

SSL/TLS Certificate Issues​

Common Prompts​

  • This website cannot provide a secure connection.
  • Error message: ERR_SSL_PROTOCOL_ERROR.

Possible Causes​

  • SSL certificate has expired.
  • SSL certificate does not match the accessed domain.
  • Using a self-signed certificate but did not install the root certificate.

Solutions​

  1. Check the SSL certificate validity period, and if expired, update it immediately.
  2. Confirm that the certificate's domain (Common Name or SAN) matches the accessed URL.
  3. Ensure the client has installed the corresponding root certificate.

DNS Configuration Issues​

Common Prompts​

  • Unable to find the IP address of the server.
  • Check for any spelling errors.
  • Error messages: ERR_NAME_NOT_RESOLVED or DNS_PROBE_FINISHED_NXDOMAIN.

Possible Causes​

  • DNS records are not set up correctly or resolved.
  • Domain name has not been registered or resolved.

Solutions​

  1. Use DNS tools (such as nslookup or dig) to check the domain resolution status.
  2. Ensure DNS records are configured correctly (such as A record or CNAME record).
  3. If DNS configuration has been recently changed, wait a few minutes to ensure DNS cache has been updated.