I am attempting to add ssl to my custom domain for the windows azure websites. I have configured everything properly according to the guides, but for an unknown reason when I attempt to access my website via HTTPS, it returns with a connection denied error. the redirect still works perfectly fine with a standard HTTP request.
for reference (https://www.cryptoalias.io)
short version of method (in case I missed something):
bought a SSL cert from comodo.com
generated a .pfx from the .cer they issued to me (using iis)
uploaded .pfx to azure
verified cname: created custom domain redirect to azure
bound ssl to custom domain
configured A name redirect to the VIP azure issued me. remove cname redirect
attempt to connect to https = nothing, http works.
sorry I realize this is rather short on information, but I'm not sure what more I could provide besides the actual SSL cert.
You need to configure your cert on 2 domains: cryptoalias.io and www.cryptoalias.io. Because if you go to https://cryptoalias.io/ your cert works fine.
Related
We have developed an angular website and we have both personal server and a registered domain extension. We were able to host through public ip using iis but when the domain name was used in throws NET::ERR_CERT_AUTHORITY_INVALID. It also redirects to https by default.
We also tried using xampp too. We don't want to use any cloud servers as our custom domain extension can't be used.
kindly help us to host the website.
As you mentioned the error message: ERR_CERT_AUTHORITY_INVALID.
This issue is related to your certificate. If you do not currently have a certificate, you can choose to create a self-signed certificate, or apply for a certificate from the Authority.
If you already have a certificate and still have this issue, you can check to see if it is expired and try renewing the certificate.
I purchased a standard SSL certificate through Azure, and it forced me to remove the www. prefix. I couldn't do DNS-type domain verification at the time, and imported the certificate got it verified on another means, and got the non-www url working with the new certificate.
However, when trying to bind the www version of the url, the imported certificate does not come up in the list, and the documentation indicates that this is only possible when the domain has been verified using DNS or email verification methods.
I subsequently inserted the required TXT record on the DNS for verification. However, the certificate still does not come up in the list for binding. Is there a way for me to get the verification done again and add www support, or is my only option to lose the money spent on a certificate and buy a new one?
I got hold of Azure support, and they introduced me to App Service Managed Certificates, which are free for Azure Web App use. So I created a new certificate for the www version of the domain and resolved the issue. I wonder if this covers all my web app needs and if I'll ever need to purchase a certificate again for Azure?
This might be a stupid question, and for that I'm sorry, I'm not well-versed in DNS configurations (so perhaps I shouldn't be meddling in this, lol), but anyhow..
I have a web app running in Azure that is currently undergoing a bit of a name change. Therefore, I want to redirect users trying to access my domain to another domain, let's say https://example.com to https://subdomain.anotherexample.com. I own both domains and have certificates for both of them, but I cannot for the life of me understand how (or if its even possible) to redirect users in this way?
I have both URLs configured as A records for the underlying IPv4 adress, and have tried to configure a re-direct in my cPanel to redirect the domain example.com to https://subdomain.anotherexample.com, but if I try to access https://example.com it just complains that the certificate is from another provider (not my Azure certificate, but instead my web hosting certificate used for other sites). Both URLs are set up as custom domains for the same app service in Azure with SNI SSL certificate bindings where example.com is bound to a standard certificate for that specific domain, while subdomain.anotherexample.com is bound to a wildcard certificate for *.anotherexample.com.
I assume there must be something that's not allowed in trying to redirect between two different domains where https is involved because trying to access http://example.com works (i.e. it re-directs to https://subdomain.anotherexample.com). Do I have to write some kind of script server-side that re-directs users manually?
I used to run one of my websites (EyeDentity.Online) from a Windows VM on Azure. I had an SSL Certificate in IIS up to run it and all was well in the world.
Since I moved the Website to the Azure App Service and installed the SSL Certificate in Azure whenever I go to the Website for the first time in a browser session it tells me that the certificate is invalid.
It appears to quote the standard AzureWebsites.NET even though my certificate is bound to my website
How can I get this warning to go away as it may be scaring away users!
Things to check:
You must be on Standard or Premium level to bind to cert
Check SSL bindings section of Custom Domains and SSL blade to make sure you've
bound the domain to the right cert.
The description of the problem sounds like number 2 here. If you haven't changed this, then it will bind by default to the azurewebsites cert and not yours.
Some docs here: https://azure.microsoft.com/en-us/documentation/articles/web-sites-configure-ssl-certificate/
Your cert is for azurewebsites.net and not EyeDentity.Online. You should get a wildcard cert for your domain name:
*.azurewebsites.net should be: *.eyedentity.online
ref: https://azure.microsoft.com/en-us/documentation/articles/web-sites-configure-ssl-certificate/#1-get-an-ssl-certificate
"Before requesting an SSL certificate you must first determine which
domain names will be secured by the certificate. This will determine
what type of certificate you must obtain. If you just need to secure a
single domain name such as contoso.com or www.contoso.com a basic
certificate is sufficient. If you need to secure multiple domain
names, such as contoso.com, www.contoso.com, and mail.contoso.com,
then you can get a wildcard certificate, or a certificate with Subject
Alternate Name (subjectAltName)."
I just bought a SSL Certificate for an parked domain that im going to use for redricting users to my azure web service. The problem is that when i redrict the user to the azure webservice the certificate isn't valid for that page, i guess it's becuase it was issued to my parked domain. But the only reason why i issued it for my parked domain was because it isn't possible to register a SSL certificate for an azure webservice because when you are registering your certificate you have to validate your domain and therefor need access too email adresses that are presented by the SSL manifactor. And the email that the manifactors present are those emails that only Microsoft have acess too.
So, this what i want it to be like (not real adresses):
User visit www.helloworld.net ---> User are connected to www.helloworld.net using a valid SSL Certificate ---> User gets immediately redricted to helloworld.cloudapp.net ---> User are connected to helloworld.cloudapp.net using the same SSL Certificate
Is this possible?
To make this work you shouldn't use redirect, but use CNAME instead.
Resources:
http://blog.smarx.com/posts/custom-domain-names-in-windows-azure
http://blogs.msdn.com/b/benjguin/archive/2012/04/15/how-to-request-buy-a-certificate-and-use-it-in-windows-azure-comment-demander-acheter-un-certificat-et-l-utiliser-dans-windows-azure.aspx