By delwiiin
I bought a domain through Godaddy and set up a landing page. Last week, I configured a DO droplet with SSL from LetsEncrypt (the automatic one on the WP droplet), used DO’s nameservers on GoDaddy, and everything is working fine over HTTP (except I’m getting ‘Not Secure’ warnings on Chrome). HTTPS is still forwarding to GoDaddy. I can’t make any DNS changes on GoDaddy obviously, because I’m using DO’s DNS & their nameservers.
Any idea what has been going on? I did this last Thursday, it should have all propagated by now (and a propagation checker verifies that it’s all going through the DO IP address).
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!
Hi there @delwiiin,
Indeed as you are using the DigitalOcean nameservers, you should make all DNS changes via your DigitalOcea Control panel. Also as you’ve made the DNS change 1 week ago then it should not be DNS propagation
The issue could be due to a couple of things:
-
Make sure that you’ve cleared your browser’s cache
-
Check if your www version is pointing to your Droplet’s IP address
-
Make sure that your Apache Vhost for port 443 is set up correctly
Freel free to share the content of your Apache Vhost here so that I could try to advise you further.
Regards, Bobby
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.