I'm having trouble getting the custom domain I bought from GoDaddy to work with the Django app I have hosted on Heroku's free dyno. The Heroku app is accessible from the custom domain, however, I keep getting a privacy error from chrome. See below:
My Heroku dashboard confirms that I have added my custom domain. I have tried doing this through both the CLI and GUI, with no different results.
My DNS settings on my domain in GoDaddy are configured as follows. Someone had mentioned the CNAME setting should be the .herokudns domain generated by the addition of the custom domain in the Heroku dashboard, but when I make that change the website is not accessible at all. The Heroku app is named:
desolate-basin-60228 and can be accessible at https://desolate-basin-60228.herokuapp.com/
and in GoDaddy I have confirmed that my forwarding is set to http (not https as I don't need a security cert. for this site):
I also thought that it may be an issue with my Django settings.py file. So I adjusted any line with mention of https. This did not have any effect.
Does anyone have any thoughts on what I'm missing here?
Based on this Heroku help center resource, if your site needs SSL support, then it's not possible to set up a GoDaddy domain with Heroku. That could explain why you're having trouble.
However, there may be a few workarounds:
https://domainpromo.com/1831/godaddy-heroku-setup
https://medium.com/#successengineer/how-to-setup-heroku-with-godaddy-d8e936d10849
Related
I have a domain hosted through Google. I'm using Google Workspace for a lot of my day-to-day operations (e.g. Drive, Gmail, etc). I'm using AWS as my infrastructure and business logic for my application. I'm having trouble making my site support TLS. If you visit it now, you get this on chrome and I can't seem to make HTTPS requests work.
I have my domain pointing to AWS via Custom Name Server.
My route 53 has the NS type records listed under the hosted zone
I've tried to request a Certificate from AWS to make it work.
My problem is I don't know how to tell Google about it. How do you let Google know about the certificate so I can make my site HTTPS?
I believe approaching Google is not going to solve your issue as in the above case Google is only responsible to host your domain . So DNS setup is only responsible to route requests to your site and not making your site more secured.
I also found that you are exposing your site as http rather than https and thats why your site is unsecured.
Is your site is running on a web server or is it hosted on S3 as static web site ?
Note: you cant enable https on S3 static website.
The workaround to above problem is below :
Route53 has A record to pointing to ALB (configured with ACM) distributing traffic to Ec2 instances running your web application.
If anyone is still looking. I wanted to keep it cheap with a simple S3 static website. If you want to maintain the S3 part, make a CloudFront distribution (if you haven't already.
Inside the CloudFront under the main settings, use a Certificate you made from Certificate Manager.
Then head over to Route53 (even if the domain is hosted via Google) and route the "A" name record to the CloudFront. NOTE: make sure the "Alternate Domain" name is filled in or else it won't see it.
Let it update for about a minute or two and it will show https
I'm trying to connect my Heroku App via a custom GoDaddy subdomain. The subdomain is "subdomain" (for the sake of example). What I'm doing is, copying the DNS Target from Heroku and adding it in GoDaddy as a CNAME such that it is pointing to the DNS Target given by Heroku. Nonetheless, I'm getting the following error when going to www.subdomain.mysite.org
I have previously created subdomains and connected them to GoDaddy with the DNS Target that Heroku provides. Don't know what I'm doing wrong. I tried to refresh the DNS but it's not working.
Good Afternoon,
I have followed a few tutorials on this topic and I have researched to see what I may be missing, but so far I haven't come up with anything. I'm sure it's a simple fix I just need a bit of help.
So I have the domain brandonkjones.dev that I purchased through Google Domains and I am trying to forward it to a static page hosted on S3. I created the hosted zone in Route 52 with the name brandonkjones.dev.
and I changed the Google Domain name servers to match those generated by the hosted zone.
I also added the additional records to forward the subdomain www to the root domain.
and Finally, I added the CNAME entry to the custom resource records on Google.
I'm sure this tutorial left off a step and I'm missing something because the original tutorial didn't even mention adding the CNAM resource within Google. Any help is greatly appreciated.
I had this same issue, tried with multiple browsers and triple checked that I'd done all the Route 53 and Google Domains steps correctly to no avail. Then I opened my terminal and tried:
curl http://my-domain.dev
and it returned my index.html that I uploaded to my S3 bucket, meaning I'd done everything correctly, but my browser wouldn't let me access the website over HTTP. In my devtools network tab, I could see that even if I explicitly typed in http://my-domain.dev it would do a 307 internal redirect to https://my-domain.dev. This is a security feature that browsers have to keep users from navigating to insecure sites over http.
Since the tutorials I followed for setting up S3 static hosting with a custom domain registered on Google Domains did not setup any SSL certificates for enabling HTTPS, the only way I could access my website was over HTTP. One way to fix this issue is to turn off HSTS as outlined here. Or, you could use something like AWS CloudFront to serve your S3 site over https, which you'll probably want to do if you want other people to access your site without this issue.
I own my domain mydomain.com through Google Domains. I'm creating a React application deployed through Amplify CLI. On the console, I tried to set up a custom domain for my Amplify app at https://us-east-2.console.aws.amazon.com/amplify/home?region=us-east-2#/d2xxxxxxxxxxtf/settings/domains so when someone visits admin.mydomain.com, they'd be redirected to my app. I copied the CNAME record over to Google Domains DNS management per this guide, but after AWS verified that I own the domain and supposedly configured everything, I still can't access my app at the subdomain. Whenever I point my browser to admin.mydomain.com, I'm redirected to https://www.admin.mydomain.app. The console seems to have automatically set up this redirect, and I see ERR_CONNECTION_REFUSED at the endpoint it brings me to, because there's nothing hosted there. How do I avoid this redirect?
While I was writing this, I took another look at the Amplify Console (Dec 2019), and found, under App Settings, at the bottom, Rewrites and Redirects, where I found the 302 redirect rule to the www subdomain, removed it, and got this working.
I have a django application that I launched with heroku. I have a challenge of adding my custom domain to change the www.example.heroku.com to www.example.com. I got my domain with hostgator and I have changed the cname to point to www.example.com.herokudns.com. but after 48 hours I am unable to use www.example.com and I contacted my domain provider which is hostgator but I was told I needed nameserver which is not provided by heroku. I am confused at this point as this is my first time of trying a custom domain with an heroku application
Heroku doesn't use nameservers. All you can do is point the CNAME in hostgator to your heroku app which is something along the lines of :
myapp.herokuapp.com
Double check that it is the right app domain.
You also need to add your custom domain to the heroku project through the heroku dashboard: https://devcenter.heroku.com/articles/custom-domains