1

How can I use HTTPS with *.domain.com AND domain.com?

view story
linux-howto

http://serverfault.com – I've been looking for a solution to the following problem for a few days now. I have domain.com for which I have bought and installed a wildcard certificate so now I can provide secure access to www.domain.com or whatever.domain.com. This works. However, even though the application thar runs on these subdomains makes sure no one gets to visit an URL that doesn't contain at least www as the subdomain, you can still delete the www part. Once you do that no serverside redirects will help if you are on https because the browser will not fulfil the request because the wildcard ssl certificate will (HowTos)

taskli's picture
Submitted by taskli on 10/19/2012

Stories similar to How can I use HTTPS with *.domain.com AND domain.com?

I have a issue with Plesk to set the right path for a subdomain for a subdomain of a domain alias.

The structure I have:

domain.nl (Head domain)

*.domain.nl (wilcard subdomain) (points to: '/public_html/s') domain.com (alias for domain.nl)

It's not really possible to create a wildcard subdomain for the 'domain.com(alias of domain.nl) like I did for the '.domain.nl' wildcard subdomain.

SSL installation 36 weeks 2 days ago

Hello I have a few questions regarding installation of SSL.

The domain for the cpanel account I want to use ssl for is domain.com but I have rewrites to www.domain.com in my .htaccess file.

From what I've read I should get a certificate for www.domain.com then, is this correct?

Should I generate the signing request in WHM or cpanel?

We recently bought a wildcard certificate and installed it for a domain. It works fine for the main domain but seems to not work at all for any sub domains.

Whats happening is we can access the sub domains fine on HTTP, but whenever we try HTTPS for the same sub domain url we are redirected back to the main domain.

Sorry, if this is very vendor specific but I purchased an inexpensive SSL Cert from GoDaddy. Right now everything on production is hosted off of www.domain.com. When specifying the common name would a wildcard (ie *.domain.com) cover the case of a lack of a third-level domain such as domain.com? Just to be sure, I made it for www.domain.com rather than a wildcard.

I read through some guides on this and I believe it is possible to have apache respond to a subdomain through ssl. I have domain.com responding on 80 and I do not need domain.com responding on 443.

Q1: Does a DNS rule for *.domain.com match multi-level domain names?

DNS for a subdomain 41 weeks 5 days ago

I have: - two DNS servers: 1.1.1.1 and 2.2.2.2 - domain name: domain.com pointed to 1.1.1.1

I want to point sub domain: sub.domain.com to 2.2.2.2 (obviously www.sub.domain.com too)

on 1.1.1.1 I've create a DNS A record pointing sub.domain.com to 2.2.2.2

accessing sub.domain.com now lead to 2.2.2.2 successfully

the problem is the DNS records on 2.2.2.2 such as CNAME www do not work means access

How to install wildcard SSL? 45 weeks 3 days ago

I know this kind of questions been asked here many times and I read through every single one of them and still do not understand how to do this at all.

I basically have a VPS server with a hosting account that has 1 dedicated IP.

I have a subdomain that has an SSL certificate that is working nicely. The web address for it is, lets say, like this: sd1.mydomain.com (sd1=sub-domain 1). Now I want to add a second subdomain, but it doesn't need to have the certificate encrypting the data. Thus, I want: sd2.mydomain.com

I adjusted my sites-enabled directory to have two config files, one for each subdomain.