There is something wrong with my DSN domain configuration that I can't understand

Posted October 10, 2020 738 views

Hello everybody,

I have a problem with my droplet DSN configuration. Five days ago I bought a new domain on Godaddy and I set it up in order to point the droplet ip out by configurating the nameservers:

my domain:
droplet ip:

The propagation has gone well as I received an email by GoDaddy saying so, but as you can see, the requests to the domain above retrive a error (sometimes showing a 404 bad request).

What is weird is that I can reach out my website only by Tor browser (not always actually) and this is uncomprensible for me. Nevertheless, this suggest me that the problem is in my network configuration on Digital Ocean but I can’t figure out waht is it.

I belive I created a proper record on it, this is my download zone:

$TTL 1800 IN SOA 1602252637 10800 3600 604800 1800 1800 IN NS 1800 IN NS 1800 IN NS 3600 IN A 3600 IN A

I also check out the server configuration, I added my new domain to the ip address already listed in my Nginx config file and in my file (it’s a django project).

Last but not least, I didn’t configurate the SSL standard certificate that was included in the package. Could it be the problem? I don’t think so.

Please someone help me.

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.

Submit an Answer
1 answer

Hi there @marklore,

Yes, your DNS configuration looks absolutely correct.

The problem is due to the redirect from HTTP to HTTPS, but you don’t seem to have an SSL certificate installed.

What you could do is follow the steps here on how to install Let’s Encrypt certificate for Nginx:

Hope that this helps!

by Hazel Virdó
by Kathleen Juell
In this tutorial, we will show you how to use Let's Encrypt to obtain a free SSL certificate and use it with Nginx on Ubuntu 18.04. We will also show you how to automatically renew your SSL certificate. If you're running a different web server, simply follow your web server's documentation to learn how to use the certificate with your setup.