I was following the tutorial how to setup django in ubuntu 18.04 . I used DigitalOcean first and have some problems with domain ,domain is ending on .app , everything worked fine , web-app works normal on server ip . Let’s imagine my server ip is 192.24.45 ( I don’t want to enter my real server ip) , so bought domain on Go Daddy , changed the name servers to ns1.digitalocean.com. , ns2.digitalocean.com. , ns3.digitalocean.com. I waited almost 48 hours before configuring the domain on my project Also I created domain on Digital Ocean Here is screenshots
https://imgur.com/gh3NwDC https://imgur.com/9JxbF3g https://imgur.com/BIZEnP5
First screen is DigitalOcean domain page Second screen is go daddy screen Third is sites.avaliable file that I needed to create by tutorial
What my problem ?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
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.
There are a couple of things that need to be checked if we don’t have any of the real information. Firstly, I’ll recommend you to make sure your domain is actually loading from your Droplet. To do that, you can simply ping it from your terminal
Once you are sure it’s loading from the right place would be time to turn your attention to your Droplet. SSH into it and type in the following command
Make sure the output contains both your port 80 (http) and the proxy port Nginx should be redirecting connections to, in most cases and in the tutorial - https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-18-04 is 8000.
If you can’t see it in the output, then something in the configurations file is not properly configured and I’ll recommend going through the Tutorial one more time.
Let’s say you see everything necessary from the above command. In that case, most probably it’s a Firewall issue. You can run a command called
nmapon your droplet’s IP to see which ports are publicly open. To do so, open a new terminal window and run
If you can’t see either port 80 or 8000 than your application is not reachable by the world. You’ll need to enable both ports for the public in your Firewall.
If after all that nothing is working still, then I’ll recommend turning your attention to your Nginx error_log.