Help on shared ssl

R

rene

Verified User
Joined
Oct 15, 2009
Messages
7
How do I set domain to use shared ssl and what would the url be?

On other servers I can access shared ssl from a url similar to:
https://www.securedomain.com/~sharedsecurity.com/index.php but what is the equivalent on a DirectAdmin server?

Also, can I share the SSL of another domain or do I need to install a server SSL (how?)

On site-helper it looks like I need to assign a dedicated IP even to a domain using shared SSL - did I misunderstand that? It seems pretty odd to me:confused:

Thanks :)
 
SSL is ip based not name based. It does require seperate ip per host.
 
You do NOT need a dedicated IP if you're using shared SSL.

What you need to do is manually create a domain or subdomain on it's own IP#, then create subdirectories under it and then create FTP users each to the specific subdirectory.

The user uses FTP to upload to that subdirectory, and then links to the page representing that subdirectory.

Jeff
 
Thanks for answers! Although I'm not sure I understand correctly.
Example: Say on www.nonssl.com we run a simple shop system for the user. (user does not have ftp access - it is just an online service).
We have an SSL on www.ssl.com. Now, the shop on www.nonssl.com should use the shared SSL of www.ssl.com during checkout.
Do I actually setup the system on a subfolder on www.ssl.com and just have a symlink on www.nonssl.com?

On an old Ensim server I just send https traffic via www.ssl.com/~nonssl.com/ and it shares the ssl on ssl.com (= no dedicated IP for nonssl.com). All files are still placed on nonssl.com. But I am not sure if it can be setup the same way on my directadmin server.

Sorry if I don't explain this well.
 
No, DirectAdmin doesn't work exactly this way. However there are similarities.

If you look at what I wrote earlier in this thread, with DirectAdmin your URL for use of the shared Certificate would be something like:

https://www.ssl.example.com/nonssl.example.com/

To do this you create first the account ssl.example.com, and then inside it create a subdirectory at private_html/nonssl.example.com. You then create an FTP user for that specific subdirectory, and that's the FTP account your user uses to load his/her code to run using the shared certificate.

If I'm not clear enough, then hopefully someone else will respond to the thread.

Jeff
 
Great stuff - thanks for your suggestions. I will have some play with it to see what I can get working.
 
You must log in or register to reply here.
Back
Top