I am following this tutorial: How To Install Nginx on Ubuntu 18.04 and have followed it to the letter. My domain is linked and resolving to DO via NS.
ookma-kyi.tk. 1799 IN NS ns1.digitalocean.com.
ookma-kyi.tk. 1799 IN NS ns2.digitalocean.com.
ookma-kyi.tk. 1799 IN NS ns3.digitalocean.com.
ookma-kyi.tk. 1799 IN SOA ns1.digitalocean.com. hostmaster.ookma-kyi.tk. 1532983840 10800 3600 604800 1800
ookma-kyi.tk. 21599 IN MX 10 mx.yandex.net.
ookma-kyi.tk. 21599 IN TXT "v=spf1 redirect=_spf.yandex.net"
My firewall is setup correctly:
22 LIMIT ANYWHERE
80 ALLOW ANYWHERE
443 ALLOW ANYWHERE
Nginx HTTP ALLOW ANYWHERE
22 (v6) LIMIT ANYWHERE (v6)
80 (v6) ALLOW ANYWHERE (v6)
443 (v6) ALLOW ANYWHERE (v6)
Nginx HTTP (v6) ALLOW ANYWHERE (v6)
Any Nginx is definitely running
nginx.service - A high performance web server and a reverse proxy server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2018-08-08 19:33:43 UTC; 7 h ago
Main PID: 2651 (nginx)
Tasks: 2
CGroup: /system.slice/nginx.service
├─2651 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
└─2652 nginx: worker process
Here is my server block /etc/nginx/sites-available/ookma-kyi.tk:
server {
listen 80;
listen [::]:80;
root /var/www/ookma-kyi.tk;
index index.html index.htm index.nginx-debian.html;
server_name ookma-kyi.tk www.ookma-kyi.tk;
location / {
try_files $uri $uri/ =404;
}
}
Here is the code to my page:
<html>
<head>
<title>Welcome to ookma-kyi.tk!</title>
</head>
<body>
<h1>Success!</h1>
<p>The ookma-kyi.tk server block is working!</p>
</body>
</html>
Any ideas on why accessing my domain from a browser gives me a can’t connect error message in firefox?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
How long does it takes to propagate?
Hello friend!
This sounds like DNS propagation. From my location/resolvers your domain is resolving and showing that page in browser. You are probably seeing the same by now, but if not I imagine you should be soon :)
Kind Regards, Jarland