I have purchased a domain name through google domains (e.g. example.com). Separately I have created a website at a third party (wix). I am now trying to connect my domain name to the wix hosted site.
Setting up regular http was trivial: I copied the 2 custom name servers from wix to the DNS name server entries in google domains and then example.com immediately began routing to the wix site.
What are the next steps to setup https so that my domain securely routes to wix?
The help page for google domains states that I can go to Certificate Authority to obtain an SSL certificate, but then where does the certificate information go? In google domains or in wix? If the cert info goes in wix, do I have to change any settings on the google domains side?
Note: I am tyring to avoid doing redirect because I want the website url to always show "example.com", I don't want the address changed by redirect to "example.wix.com" while the user is browsing.
Thank you in advance for your consideration and response.
Eventually https began to redirect properly to wix as well. I was not able to discover the root cause, perhaps it was just a timing issue with DNS.
Related
I purchased a domain with Google and I would like to associate it with a Heroku app. What is the step-by-step process to achieve that?
I recently connected my app to a custom domain. Although my domain is purchased from AWS route53. I think the approach generally is the same.
First of all, you can check out this page written by Heroku. https://devcenter.heroku.com/articles/custom-domains
I believe the tutorial given by Heroku works. However, I am tired of all those CLI that make things unvisable XD. Luckily, we can configure it from the Heroku website instead of the CLI.
Here is my approach:
First open your app in the Heroku web page, then click the "Settings" button
https://dashboard.heroku.com/apps/{your app name}
Scroll down until you see the "Domains" section, Then click "Add domain"
https://dashboard.heroku.com/apps/{your app name}/settings
Input the domain name you purchased from google (eg. www.example.com)
After adding your domain, Heroku will give you the DNS target.
From your google domain DNS management page, you should be able to add a new record for your hosted zone.
Finally, add a new record with simple routing policy, type CNAME, and value equals to the DNS target provided by Heroku.
It is really simple if you follow these steps correctly. Due to my reputation level, I cannot upload photos. Feel free to contact me if you want some image to guide you how to locate the buttons :)
It’s only 3 steps:
1. Heroku, in your app > Settings > Add your domain:
Add www.[foo.com] (Note: www is KEY!) to your app
Copy the [DNS Target] it gives you
2.Google Domains > DNS > Resource records > Custom Records > Manage Custom Records:
www, CNAME, [DNS Target]
Now you’re basically set up. If someone goes to https://www.[foo.com] in a few minutes, they’ll see your Heroku app hosted at [DNS Target]. But if they go to any other permutation (http, non-www) they’ll get a 404 error. To solve this, we’ll set up permanent redirects to the main version in the next step.
Google Domains > Website > Add a Forwarding Address:
From Field: [foo.com]
To Field: https://www.[foo.com]
Permanent Redirect (301)
Forward Path (so that [foo.com]/about forwards to https://www.[foo.com]/about)
SSL Enabled
Boom. Wait a couple of minutes for DNS to catch up, and you’re done.
heroku certs:auto:refresh
In Terminal refresh the SSL cert settings on Heroku, and check the Heroku Dashboard to confirm everything’s working.
Confirm all the below permutations forward to your site correctly:
https:
https://www.[foo.com]
https://[foo.com]
http:
http://www.[foo.com]
http://[foo.com]
paths:
https://www.[foo.com]/about
http://[foo.com]/about
PS: So does this work for the naked domain like [foo.com] instead of www.[foo.com]? No! Google Domains does not support ALIAS domains, and therefore in combination with Heroku does not support forwarding to the naked (aka. root aka. apex) domain. Sorry! This surprised me too :( Source 1: Heroku Docs | Source 2: StackOverflow. Your only alternative here is to transfer your domain (which costs money) to something like Cloudflare.
A working answer with these explanations is taken from https://nikodunk.com/heroku-ssl-google-domains-2019/
Just to add to Fergus's answer, if you are seeing the warning "cant add cname records as root domain" add www to the host name input.
I have purchased a Domain name from BigRock. Is it possible to redirect this domain to my free hosted website on pythonanywhere.com with a sub-domain? for ex: myxyz.pythonanywhere.com
I am using a free plan of pythonanywhere.com which gives us a sub-domain with "pythonanywhere" as a parent domain.
Suppose, the Domain I've purchased is "myabc.com". I want to redirect all the requests on this URL (myabc.com) to my free hosted website (i.e. myxyz.pythonanywhere.com)
Edit: I tried the Domain Forwarding feature of BigRock. I entered "http://myxyz.pythonanywhere.com" in the redirection URL. In a couple of hours when I went to myabc.com, It was showing "myxyz.pythonanywhere.com refused to connect". which might be indicating that redirection was successful but Pythonanywhere is somehow blocking the redirection.
I believe it is possible. BigRock should have a domain manager where you can add your pythonanywhere domain.
I recently purchased a domain name with namecheap.com, and added a CNAME record from my Heroku app where I am running the application. I am sure that I added the correct domain name to my Heroku app, and the correct DNS target to my CNAME on Namecheap web settings.
Previously it was working, but this morning I purchased an SSL certificate on Namecheap, and my domain just points to a Namecheap page saying "This domain is registered with Namecheap".
I followed all the steps to properly activate the SSL certificate, and it even says it's activated on Namecheap on the domain I want. Also what's strange is the the Heroku domains appear to have good ACM status.
So on the surface everything seems to be all right, but when you go to my domain my app doesn't show up.
Any idea as to why this is? Also if you have any more information you want to know feel free to ask.
I figured it out. I had to delete the default records on the domain. Initially namecheap sets a reroute, and CNAME for their parking lot page.
These need to be removed so that they don't interfere with the domain routing that you want.
I've created a new application in google developers console, my app is using the Google Calendar API and I want to be able to get push notifications on changes in the calendar. I've added and verified my domain in Web Master Tools, when I try to add the domain in the push notifications section in the console I get an error:
Error
You do not have access to the following domain: ***
I tried to do that with another application (with different google account), and I encounter the same problem, It seems like google are having a problem because it's not the first time I'm doing it and it should be pretty simple, any suggestions?
In order to add a domain to the "Push notifications" you must verify your domain in webmaster tools with a "https://" prefix, otherwise it won't work because push notifications in Google works only with "https://", that's why you need to verify it in webmaster tools with "https://" so Google can verify you have an SSL.
This will be helpful incase if you are using subdomains.
https://support.google.com/webmasters/answer/35163?hl=en&ref_topic=4564314&vid=1-635796479292102918-3720802661
When you verify that you own a domain (such as example.com using DNS verification, you've proven that you have control of the domain, all its subdomains, and all sites in those subdomains.
Similarly, if you have verified http://www.example.com (using any verification method), and then add http://www.example.com/test, you will be automatically verified as an owner of http://www.example.com/test. You'll remain a verified owner of the subdirectory even if you later delete http://www.example.com from your Search Console account.
I'm currently using a fake development domain instead of localhost on my local machine, as I have multiple websites that I want to manage locally.
Google reCAPTCHA is not recognising my domains, and is giving me this error: ERROR: Invalid domain for site key
What can I do to solve this?
You need to add the fake domain as an entry in your reCAPTCHA whitelist. This can be found in the reCAPTCHA admin panel for the current reCAPTCHA you are using.
For example, if your fake development domain is mysite.myfakedomain you would add mysite.myfakedomain to the whitelist.
Note: The changes may take a few minutes to take place.