Website, and/or webmail, and/or webadmin are not accessible. The following error appears:
CONFIG_TEXT: Server not found
CONFIG_TEXT: Could not locate remote server
CONFIG_TEXT: Internet Explorer cannot display the webpage or shows
This page can’t be displayedmessage
CONFIG_TEXT: This site can’t be reached DNS_PROBE_FINISHED_NXDOMAIN
The following error occurs when accessing via HTTPS:
CONFIG_TEXT: Secure Connection Failed An error occurred during a connection to example.com. Peer reports it experienced an internal error. Error code: SSL_ERROR_INTERNAL_ERROR_ALERT
- The domain is not registered.
- DNS servers are not specified for the domain.
- DNS servers are specified but not configured.
- A domain is resolved to IP address not available on the Internet, or hosting is not configured on this IP address.
- Firewall blocks inbound connections to 80 or 443 port.
Firstб connect to the server over SSH to run diagnostic tools.
Check if the domain is registered:
# whois example.com
No match for domain "example.com".
No whois server is known for this kind of object.
So this domain is not registered. It is required to register it before usage.
Check DNS servers for this domain:
# whois example.com
Name Server: A.NS.EXAMPLE.COM
Name Server: B.NS.EXAMPLE.COM
If Name Servers are not specified, it is required to add them at the registrar.
Check if DNS servers are configured for the domain or not:
# nslookup example.com A.NS.EXAMPLE.COM
If DNS servers are not configured it is required to set IP address for the domain.
Check if DNS servers are accessible via domain name:
# nslookup ns1.example.com
If servers are not accessible, login to registar's control panel and create A records for NS serves that point to proper IP address:
A ns1.example.com 203.0.113.3
A ns1.example.com 203.0.113.4
Check if hosting server is configured on the domain resolved IP address:
Web service should be available at tcp ports 80 or 443 for https:
# telnet 203.0.113.2 80
Connected to 203.0.113.2.
Escape character is '^]'.
This command verifies if the connection to the web server can be established. If not, then web hosting service is not running on the host or firewall blocks inbound connections at TCP port 80 on the server. Add the firewall rule to allow connection to 80 and 443 ports:
# iptables -I INPUT 1 -p tcp --dport 80 -j ACCEPT
# iptables -I INPUT 2 -p tcp --dport 443 -j ACCEPT
Ensure that website, and/or webmail, and/or webadmin is actually accessible by adding record in the '
hosts' file and trying to access web service afterwards. For example:
On Windows (connect to the server via RDP):
C:\> findstr example.com "%windir%\system32\drivers\etc\hosts"
203.0.113.2 example.com webmail.example.com mssql.example.com
# grep example.com /etc/hosts
203.0.113.2 example.com webmail.example.com
Note: Do not forget to remove the record from the