My website warrgames. net will not execute. How do I fix it?
http://warrgames.net and http://www.warrgames.net DO NOT EXECUTE
error message
This site can't be reached
warrgames.net refused to connect
.
.
ERROR_CONNECTION_REFUSED
It worked universally for months before yesterday and briefly yesterday afternoon. I have been trying to install an ssl certificate and in the process I have been changing some permissions.
Linode:
index.html (has not been changed) is located in this directory: var/www/html/index.html
ls -l index.html returns this
-rwxrwxrwx 1 root root 6277 Aug 19 14:05 index.html
In var/www/
ls -l html returns this
drwxrwxrwx 3 root root 4096 Aug 21 19:59 html
User, groups and others should have the right to read, write and execute index.html
Subprograms that are normally launched from index.html DO WORK still when the IP address and various ports are entered in the browser.
Examples 198.58.115.171:2000
198.58.115.171:50001
Any ideas to help me get my site to work properly.
1 Reply
jyoo
Linode Staff
When I curl your website, I get the following message:
curl -IlL warrgames.net
curl: (7) Failed to connect to warrgames.net port 80: Connection refused
This indicates a couple of things. First, your website may not be set to respond on port 443 by redirecting traffic from port 80 to port 443. If your SSL certificate is installed and working, you will want to ensure all visitors to your site are using the HTTPS version of your site over port 443. You may need to set your web server to enable SSL.
Second, port 80 is not responding to connections. I ran an nmap scan on your domain's IP address and found the following:
PORT STATE SERVICE
80/tcp closed http
443/tcp closed https
A state of closed indicates that your web server is not running. You'll need to ensure that the web server is running and active, and restart it if needed. The specific command to do so will depend on your distro and web server; an example command for Apache on a recent Debian version would be sudo service apache2 restart. Based on the fact that both web server ports are closed, I don't think this is a permissions issue. That said, once the web server is running and serving connections, you'll have a better idea of whether there are additional complications.