This article discusses the many common problems and solutions for server setup and configuration.You can download the world to view the document details the steps¡£
Other people can reach my server, but I can't view it locally?
Instead of correctly interpreting your request and routing you locally, the router gets confused and you simply can't connect. In some instances, this can be fixed by changing security settings in your router such as the "Filter Internet NAT Redirection" setting in devices.
If I visit my host, it brings up my router?
The router mistakenly believes you that are attempting to connect to the router instead of to local services running on port 80. External visitors do not see your router's login screen, however, and should be able to properly access your services.
I can ping my host, but I can't view my server?
Being able to ping a host does not indicate connectivity. Many firewalls, routers and even some ISPs reject ICMP (ping) packets. Likewise, even if a host responds to a ping, that doesn't indicate that services are available at that location. Instead, you should attempt to reach services at your network using our Common port numbers or a Telnet command.
The port numbers are divided into three ranges: the well-known ports, the registered ports, and the dynamic or private ports. The well-known ports are those from 0 through 1023. Examples include:
21: File Transfer Protocol (FTP)
22: Secure Shell (SSH)
23: Telnet remote login service
25: Simple Mail Transfer Protocol (SMTP)
53: Domain Name System (DNS) service
80: Hypertext Transfer Protocol (HTTP) used in the World Wide Web
110: Post Office Protocol (POP)
119: Network News Transfer Protocol (NNTP)
143: Internet Message Access Protocol (IMAP)
161: Simple Network Management Protocol (SNMP)
443: HTTPs with Transport Layer Security or Secure Sockets Layer (TLS/SSL)