Custom subdomain over https (SSL) on custom port

Hello guys,

Here is what I want to achieve:

Say I have a CRM system installed on a server. It runs on port 8073 through http, but it also might run on port 8074 through https.

I have a self signed certificate/key generated for it.

CRM's www directory is in different place than all the rest of websites, say, in a custom added Linux user's home directory.

I have only one shared IP.

What I would like to have is:
1. A subdomain crm. being created automatically for each domain which would point to https://xxx.xxx.xxx.xxx:8074 and would use same certificate/key for each domain
OR
2. Some virtual host configuration which would use only one domain, say, https://crm.domain.com:8074 and wouldn't get overwritten by DA.

What would be the best and cleanest way to achieve this with DA?

Thank you!

Note that you can only use one Certificate for each IP#/port# pair, so you'll need to reissue your self-signed Certificate, with multiple Subject Alternate Names, adding one each time you add a domain (no, I don't know how to do that; that's what man pages are for ). You can more easily use a Self Signed Certificate created for an IP#, using the login to identify the user.

However, to avoid confusion and look professional, why not buy an inexpensive commercial Certificate? You can do this even if you've already got another Certificate on the same IP#, since the port# is not the same. (I can create the Certificate and install it for you for a total of $45 for a one-year Certificate, $35 each additional year on a multi-year certificate.)

You will need to use a domain name for this Certificate, but again, you can use the same domain name you're using already, even if it already has a secure Certificate, since it's answering on a different port.

Jeff

ReverseProxy through SSL in Apache

Dear Jeff,

Thank you for your response. I'll definitely buy at least one certificate, just I got stuck with this problem: http://www.openerp.com/forum/topic34332.html

All this proxy+SSL stuff is still not very clear to me, so it is possible I'm asking silly questions that no one can be bothered to answer, but at the moment I think that self-signed certificate works fine. It's just the OpenERP v.6.1 port for https which I can't get working. It seems like it just doesn't exist in v.6.1 which would be hard to believe.

I hoped someone will put me on a right path, but since I can't get any responses, I think I'll have to make a close investigation on how these things work and solve the problem myself. It's not a bad thing overall, just it's taking much more time.

I also might try to use Nginx exceptionally for OpenERP in parallel to Apache as I've seen people got it working with Nginx. Just I don't want to screw an existing Apache setup.

As for now I'm just looking at different examples for different systems and they looks similar to mine one with one exception - they have their https port working.

I don't know anything about OpenERP, so I can't help you there. Hopefully you can get a response on their forum, here: http://www.openerp.com/forum/

Jeff