2 Messages
•
80 Points
http to https
I manually updated my @ and www records to 34.102.134.10, but the homesteadssl.com validation tool is giving me a 'doesn't exist on builder' error. Can you force-provision my SSL certificate from your end?
2 Messages
•
80 Points
I manually updated my @ and www records to 34.102.134.10, but the homesteadssl.com validation tool is giving me a 'doesn't exist on builder' error. Can you force-provision my SSL certificate from your end?
russell5607
3K Messages
•
30.4K Points
2 months ago
To complete the SSL, follow these directions exactly.
You can SSL your Sitebuilder Plus website by following this article:
Can I Secure My Homestead Website With HTTPS?
https://community.homestead.com/conversations/sitebuilder-plus/can-i-secure-my-homestead-website-with-https/5f2a9b1658180958845a60de
If you're having trouble with the Cloudflare setup, you can always call for assistance at 1-800-710-1998.
Make your Websitebuilder website secure?
Follow the steps: https://homesteadssl.com/. If you're having trouble with the Cloudflare setup, you can always call for assistance at 1-800-710-1998.
0
0
joeana_velasco
151 Messages
•
1.6K Points
2 months ago
Hi @tyler3813,
Upon checking, your website seagullcharters.net was created using SiteBuilder Plus, which means homesteadssl.com cannot be used to secure the website.
I also noticed that the domain is still using our old nameservers, and the A record (34.102.134.10) you've added for the website is not propagating properly.
To resolve this, you have two options:
Option 1: Use Homestead Nameservers
Update your domain's nameservers to:
ns3.homestead.com
ns4.homestead.com
This will allow the DNS records to be managed through Homestead.
Option 2: Use Your Registrar's Nameservers
If you prefer to manage your DNS through your domain registrar, you can point the domain's nameservers to your registrar's nameservers and then configure the following A record there: 34.102.134.10
If the website was built with another provider and they supplied the A record above, this is typically the preferred option. Once the DNS changes have been made, please allow 24 to 48 hours for propagation to complete.
If, after propagation, the website still shows as Not Secure, you'll need to contact the provider hosting the website associated with 34.102.134.10 so they can review and configure the SSL certificate on their end.
Please let us know if you'd like assistance identifying the best option for your setup. We'll be happy to help. Thank you! 😊
0
0