I am using a Hostinger VPS and Hestia CP. I can create LetsEncrypt SSL from the control panel which successfully applies to https://example.com.
It also works perfectly when I go to www.example.com in Google Chrome, Opera, and Microsoft Edge.
However, www.example.com gives "SSL_ERROR_BAD_CERT_DOMAIN" on Firefox and Internet Explorer.
www.example.com actually redirects to https://example.com address anyway but for some reason, Firefox and IE don't redirect the website before the error.
So I am assuming that it leaves me with two options. Either use the SSL certificate for both www and non-www domains or find a solution to redirect the website before the error. Couldn't figure out which way is better and how to do them tho.
If you create a new domain, it is important to also add www. subdomain to alias column. So, f.e. like on the screenshot bellow.
The next what you will do is (re)generating SSL. Now, when you generate it after the entering the alias(es), the SSL cert. will be generated also with them.
Related
I have a DNS linked to Sites using CNAME from www in my DNS settings below. So when i type www.website.com it redirects me properly but when I type website.com nothing happens. I am thinking about editing # to add something to redirect to the www but I am not sure how to do that. Cold you please help me out?
Depends on the web server your utilizing, but what your looking for is url redirects. You can put in different urls and have the redirect to the primary. So you would place your domain.com in here to redirect to your binded url which is the www.domain.com. should also be able to use it to redirect http to https, though this is usually less of an issue with browsers and servers today.
I have a domain https://www.example.com (HTTPS) which is now pointing to another IP (for this example thats 1.2.3.4).
1.2.3.4 also has other domains within IIS's directory for that particular site.
When i navigate to www.example.com all is fine but as soon as i add https to it i get a cert error.
How could i avoid the cert error from showing up? I have a rule set for canonical to point to the correct address?
Its not surprising that http://www.example.com does not produce a cert error as there is no certificate involved with that call. When you get the certificate error, you could look deeper into the error message that it provides. I'm guessing there is a mismatch between www.example.com and the certificate.
I've got the following problem. We have a SSL-certificate for a domain with a prepended 'www', like 'www.test.com'.
I've integrated that certificate with Plesk for this domain and it works fine, when somebody goes directly to 'www.test.com'. But when I enter only 'http://test.com', he won't recognize the certificate and shows a warning. How can I prevent this? Do I need an extra certificate (hope not) or can I redirect the domain within Plesk directly. A PHP-header isn't enough, because the redirection would take place after the browser tries to establish the ssl-connection.
And because the Plesk admin panel runs on this same domain, we have the same problem with 'http://test.com:8443' …
So basically:
'https://www.test.com' - fine
'https://test.com' - not working
'https://www.test.com:8443' - fine
'https://test.com:8443' - not working
Any suggestions would be nice, thanks a lot,
Carl
Try adding a this rule to .htaccess in the public root. It should redirect from test.com to www.test.com for SSL connections:
RewriteRule ^/(.*):SSL$ https://www.test.com/$1 [R,L]
Learn more about htaccess redirects
Typically, the certificate needs to be purchased for specific subdomain. Some Certificate Issuers do offer a cert for the .test.com domain that includes all subdomains (including test.com and www.test.com). If you're unsure, you should contact your certificate issuer directly.
Well first what plesk version with which OS you have, It's Linux or windows if Windows to Add reWrite URL in IIS setting on under particular.
If you have Linux with plesk any version because it's not matter either you have plesk or cpanel.
with Linux
Add ReWrite module in .htaccess for domain purpose only not for access plesk panel with specific port 8443
8443 port only configured with plesk shared license.
Use follow to avoid Trusted message
https://www.test.com - fine
https://test.com' - not working
in this case use URL rewrite redirection as above said steps.
=============================
Check Cname Entry in particular domain DNS record.
I hope this helps.
I'm a beginner in .htaccess and I need help. We have this website with its store module in https. We also have a parked domain pointing to this website. The problem is, when I type "https://www.parked_domain_name.com/store/" in the address bar, I get an SSL error. However, when I type "http://www.parked_domain_name.com/store/" on the address bar, it redirects to "https://www.parked_domain_name.com/store/" without getting any SSL errors. How can I view the store w/o SSL errors when I type "https://www.parked_domain_name.com/store/" in the address bar?
In general, you can only have HTTPS running on a single domain name for a site.
There are exceptions, for example a certificate for *.example.org would let you run HTTPS on both www.example.org and web.example.org subdomains. Also, some certificate providers will issue certificates for a fixed list of several domain names.
But in common usage, one IP address can have only one certificate, and one certificate can have only one domain name.
The behaviour you describe of the http URL redirecting the the https URL without warnings does not sound like it is possible. Perhaps try a few different browsers - they all act a bit differently on this front. How you reached the URL is not relevant. If you access example.org over HTTP and the certificate says anotherdomain.com then you will get SSL warnings.
You're best off running the site only on e.g. https://example.org/ and redirecting any other domains to that one, rather than hosting the site from multiple domains.
I hope this helps.
For some reasons Google custom search result shows https:// for some of my page links. The only solution for now would be to redirect the https:// links to http:// with htaccess for now until i figure out why search results are showing https://
I want the redirect to bypass the SSL cretificate or "Add Exception" page and redirect to http://
You won't be be able to do this with .htaccess because for the client to get the redirect it will have to have already started the SSL session (and therefore shown the add exception page) The only way around this is to buy a real certificate signed by a trusted CA.
You could also sign up for Cloudflare HTTPS. They offer it free of charge right now. You can then enable SSL on the entire site, and redirect to HTTP, or HTTPS. Your choice. This would prevent the warning from being issued.