I can't hit my website on http because of redirection created to https on previous droplet with Nginx

Hello there, I’m setting up my website again step by step on a new droplet. On earlier droplet I had added nginx certificate from let’s encrypt to make it secure and added a redirection to https when site was hit on http.

Now on new droplet first of all I’ve installed nginx from official NGINX repository instead of Debian or Ubuntu repositories to get the latest version. Because of this from my understanding I only have to add server block in /etc/nginx/conf.d/*.conf and there won’t be /etc/nginx/sites-enabled/*;.

As I’m yet to setup certificate on this new droplet I was expecting I should be able to visit my website with, but it is still redirecting to Can anybody please explain why this is happening?

Note: I can visit my website with IP address.

Is it because of certificate I had created earlier? What can I do in this case?

Thanks, Dhanesh


Submit an 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.

Hello folks, though it was stupid mistake, I later got to know what had happened. It was cached in the memory, when I cleared the cache memory, I was able to hit it on http.