I'm trying to get my naked domain work. Currently, it's showing this
NET::ERR_CERT_COMMON_NAME_INVALID
I read this answer, and the ones in it. The answers are leading me to believe that if I am using GoDaddy and Heroku, I simply cannot use my naked domain. Forwarding from naked domain to full domain only work on HTTP websites. I mean, who still uses HTTP?
What's the easiest way to solve this? Port my domain from GoDaddy to another host that supports ANAME? Is there an option that does not require a large amount of work?
Related
GH-pages tells me the domain is not eligible for HTTPS at this time. I am wondering how do I enable this with a Godaddy purchased domain? My site is connected and running properly, but I cannot get HTTPS to work. I have also checked that there are no mixed-asset types in my index.html
I figured out that in the DNS records that are automatically configured with the GoDaddy domain, you must remove that A Record that has the value of park.
Recently I have installed ssl certificate on my website. After the ssl certificates have been installed ,I found that my subdomain is not working properly. I will address my subdomain as 'xxxx'and main domain as 'primary'. The main domain works well with http as well as https. Now the subdomain works well with http, but with https://xxxx.primary.com delivers me the main site content and not the content of subdomain. I'm using apache server, linux operating system.
Can anyone please help to solve this issue?
Thanks in advance.
This is how SSL protocol works with the browsers. Whenever browsers receive HTTPS request for domain name, it first checks with the server then delivers the site's content. If a website on server has enabled SSL accessed with HTTPS, browser will try to make secure connection and send request to the server.
In your case, your main website is working properly with HTTP as well as HTTPS and delivers proper content, but your sub-domain is not showing proper content for HTTPS. In order to deliver proper content you should consult with your development team. You can better host your sub-domain on another server or you can protect your sub-domain with valid separate SSL certificate.
Suggestion: If you own multiple sub-domains then it is advisable to use Wildcard SSL, that can protect unlimited number of sub-domains with single certificates. Please note, this unlimited does secure first level (blog.domain.com), doesn't second-third-fourth-etc. level (news.blog.domain.com, 1.news.blog.domain.com or abc.1.news.blog.domain.com).
This appears to be a cPanel problem. The good folks at name.com use cPanel. Hosting at name.com for my site is a problem in that when someone accesses my site with https the SSL certificate from another site is sent by the server. cPanel docs seem to imply what I'm describing is a known problem. http requests are fine. Short of implementing SSL for my site, are there recommended ways to set up my site?
This issue is coming because you dont have private SSL for your domain, so install a SSL for domain.
You can get a free SSL from these 2 site:
https://www.startssl.com/
https://letsencrypt.org/
and request your hosting provider to install a SSL after that your website will on both http:// and https://
My main site https://example.com has an SSL cert, no problem.
Now, I have developped a related application, that is hosted on a completely different server, and under : app.example.com. It has a dedicated IP.
The app uses websockets and needs SSL to function properly acros all devices. But I'm having trouble finding out how to register a new certificate for a subdomain... What's the strategy here? Should I have a wildcard cert on the main server, and somehow redirect from there? In that case, the app server wouldn't have access to the cert, and I wouldn't be able to create my secure socket connection, right?
The certificate has to be installed where the server which provides content using this certificate. This means
That the certificate for the subdomain has to be used on all servers which serve the subdomain, i.e. your websocket server.
And nowhere else, i.e. it is not needed at the main domain just to provide a redirect from the main domain away.
You are free to use any certificate which matches the subdomain, that is it can be a wildcard certificate but can also be specific for only this domain.
You can go for a wild card certificate and bind it to all the URL's who share the same domain. But keep in mind, the wildcard certificates (irrespective of any brands) supports unlimited first level sub domains .
Wild card certificates can be installed on any server where the FQDN is hosted. In situations where the the sub domains are hosted on multiple servers, the wildcard certificate will work for all of them.
I have two domain names pointing to one Heroku app. One domain name is always used over https. I have a wildcard certificate for that domain. That, combined with the fact that I can only have 1 SSL certificate installed on a Heroku app, leaves me to force the other domain name to http. I have installed the SslEnforcer gem to take care of this for me. However, since Heroku now gives me default Piggyback SSL on my app, when I try to access my non-secure domain over https, it first hits the Piggyback SSL certificate, which yields a security error, since I'n not on the *.herokuapp.com domain. It never got to the SslEnforcer redirect.
So it seems that I desperately need to disable or remove the default Piggyback SSL. Is there a way to do so? Or is there another solution anyone can think of?