I've set up paid dynos for my heroku app. The SSL certificate works on my-app.herokuapp.com but when I go to my custom domain I get your connection is not private.
I'm using godaddy as my domain provider. I have my CNAME set with name: www and value: my-app.herokuapp.com
It works on http but not https.
Your SSL certificate has to be registered to the domain name you're serving from. If it "works" on my-app.herokuapp.com then you need to purchase an SSL cert for your custom domain. https://devcenter.heroku.com/articles/ssl-endpoint#acquire-ssl-certificate
Adding a Heroku instance to a subdomain is done by pointing the subdomain to Heroku's dns instance, not the app.
Example:
Create a CNAME record
Host: subdomain (ex: explore.main-street.com)
Target: herokudns (ex: autumn-sunset-1495.herokudns.com)
Read Heroku's docs here.
Related
I have a domain purchased from Godaddy. Then a Virtual Machine setup on Azure with an web application installed on it.
So thus far I have:
An Azure VM with an application running on it, lets say the ip for the VM is 12.3.456.789
A domain name I purchased from godaddy, e.g mydomain.com, I then created a subdomain for e.g sub.mydomain.com
I then added an SSL certificate to this subdomain which worked fine, after I changed the DNS A record for the subdomain to the ip address of the VM 12.3.456.789, also the application on the VM is accessed on port 4000. So https://sub.mydomain.com:4000
The issue is that when I access my domain via https I get the ERR_SSL_PROTOCOL_ERROR in all browsers but when I access it via http then the application on it loads completely fine.
Any ideas on what I would have done wrong or left out in my setup?
Also if I did not provide enough information do let me know.
commercial SSL certs are always signed to include the TLD
(Top Level Domain -> in your hypothetical case: mydomain.com) !
You should contact godaddy to change the certificate to change the SAN (Subject alternative Name to sub.mydomain.com)
One example:
You order a ssl certificate for the subdomain www for your domain mydomain.com.
mydomain.com is valid by its nature (SAN -> it's the TLD)
Whereas www.mydomain.com is the SUBJECT.
Best H.
To rewrite to rule from https as you are getting ERR_SSL_PROTOCOL_ERROR please check you are correctly provided ssl cerficate SSL Certificate Checker as my SSL provided is DigiCert.
And to make Https ensure in your remote desktop in IIS manager click your virtual machine ->binding -> Https and port as 443 and upload certificate.
In your virtual machine try to add outbound security rule provide service as HTTPS and port as same in 443
Reference: https://learn.microsoft.com/en-us/answers/questions/23397/not-able-to-secure-windows-azure-vm-in-https.html
I have a free account at Netlify.
I have a domain tanguay.info at another provider.
I created a site at Netlify called dpodreact.netlify.app and want it to appear when on types dpodreact.tanguay.info and so added a CNAME on my site.
Visiting dpodreact.tanguay.info gives an HTTPS error.
How can I connect this CNAME subdomain to my Netlify account without hosting my whole domain at Netlify?
Netlify will only auto-provision a certificate if they are the DNS nameservers being used.
You can get a certificate from elsewhere though, (possibly via your current DNS provider), and click on that "Provide your own certificate" button.
I have an http://example.com website on some hosting and I'd like to have https://myapp.herokuapp.com being show as https://subdomain.example.com
I have configured on "example.com" hosting side:
CNAME myapp.herokuapp.com.
I have added to heroku domains:add --app myapp subdomain.example.com
So now I see CNAME like subdomain.example.com when calling for heroku domains -a myapp
But when I'm opening https://subdomain.example.com I see the insecure connection and the certificate is issued for *.herokuapp.com :
Subject:
CN = *.herokuapp.com
O = Heroku, Inc.
L = San Francisco
S = California
C = US
Alternative subject:
DNS Name=*.herokuapp.com
DNS Name=herokuapp.com
So how can I make my heroku subdomain issue a certificate for https://subdomain.example.com ?
Also, there is a problem.
When I type http://subdomain.example.com in Chrome, the http://example.com is loaded.
When I type http://subdomain.example.com in Firefox, the http://subdomain.example.com is loaded and works without any encryption, while it doesn't allow to open http://myapp.herokuapp.com and opens it as https://myapp.herokuapp.com
How can I avoid this behavior in Firefox? The behavior I want when trying to open http://subdomain.example.com is to always force https://subdomain.example.com and not leave to http://subdomain.example.com or redirect to http://example.com
I got the answer of the Heroku support team:
Thank you for reaching out to us. Looking into your issue I found that you have configured your domain incorrectly.
subdomain.example.com. 599 IN CNAME myapp.herokuapp.com
When you add a domain to your app, Heroku generates a unique DNS target for that domain. You need to point your domain to this DNS target at your DNS provider.
=== myapp Custom Domains
Domain Name DNS Record Type DNS Target
─────────────────────── ─────────────── ──────────────────────────────────────────────────
subdomain.example.com.ru CNAME secure-lynx-1rbkrol1o46ccpklg1j5u2ac.herokudns.com
In your case, I see that you have added a subdomain subdomain.example.com to your app. You need to point your subdomain to the Heroku generated DNS target secure-lynx-1rbkrol1o46ccpklg1j5u2ac.herokudns.com of that domain with CNAME record type (CNAME for subdomains and ALIAS/ANAME for root domains) at your DNS provider. This should resolve your issue.
I'm trying to enable SSL on a subdomain from a domain I purchased from Google Domains (Managed with Netlify DNS). The domain is currently pointing to a static react app hosted by Netlify (it has SSL).
The subdomain (api.example.com) pointing to an elastic IP associated with an EC2 instance doesn't seem to be working when I try to access it with HTTPS (api.example.com’s server IP address could not be found.) but works with HTTP.
Does anyone know of a way I could use that SSL certificate I got from Netlify on the subdomain pointing to my aws instance?
I'm using only an A record for the subdomain -> elastic ip. For the purpose of getting everything to work, I've enabled all inbound/outbound ports for all traffic types on my instance security group.
Why I am unable to add domain to azure web app for a domain coming via Cloudflare proxy even though I have configured the URL to resolve to azurewebsites.net URL via CNAME?
Here are the steps to get through Cloudflare proxy:
First you need to turn off proxy in Cloudflare.
Configure the URL to point to azurewebsites.net URL in DNS
Then add the custom domain.
Once the domain is added, enable the proxy again.