Topic: HTTPS Wildcard: Subdomains problem
==== Required information ====
- iRedMail version: 0.8.6
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MYSQL
- Linux/BSD distribution name and version: RHEL 6
- Related log if you're reporting an issue:
====
By default, the combined httpd.conf and ssl.conf contain a Listen 80 and a Listen 443. After adding a real certified wildcard certificate, virtual hosts seem to be only work as before: when connecting with http://, it goes straight to www.domain.com; when connecting with https://, it goes straight to anything.domain.com (it is supposed to be mail.domain.com). Both are on the same IP.
Despite having a wildcard certificate, and going through all the various setups listed here and elsewhere (e.g., you cant do it on a single IP, you can, NameVirtualHost, Virtualhost 80 and 443s, default:443, etc), it seems impossible to have https:// for both subdomains. Putting the key directives in both the Listen 80 configuration and the Listen 443 configuration Apache will either throw an error on restart, or will get the subdomains confused.
The end goal is to have the following available:
http://www.domain.com (main page), https://www.domain.com (main page HTTPS), https://mail.domain.com (webmail, HTTPS)
So far, only can do http://www.domain.com and https://mail.domain.com at best; but the goal is to get www.domain.com also working on both http and https (subdomain2 should be https only).
Should be simple, but not so!
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.