Moving /admin/ to another vhost - possible?

[Peter M Dodge]

Hello,

 

In an effort to increase security of my WHMCS install with the recent hack, I had the idea of putting the admin area in a seperate virtual host listening on another port (but on the same server).

 

I don't want to trash my live install trying this and I don't have a second license for a testing type environment so I thought I'd ask: is this possible? And if it is, what steps do I have to take to implement this?

[laszlof]

Pretty sure this isnt going to be possible without a second license. Even then, it would not be easy.

 

Also note, if you purchased your license directly from WHMCS, you can email them and get a free "developer" license.

[Peter M Dodge]

Just to clarify I'm thinking of something like:

 

<VirtualHost 1.2.3.4:80>
  ServerName www.example.com
  DocumentRoot /var/www/whmcs-public/
</VirtualHost>

<VirtualHost 1.2.3.4:8080>
  SSLRequire %{SSL_CIPHER_USEKEYSIZE} >= 128
  ServerName admin.example.com
  DocumentRoot /var/www/whmcs-admin/
</VirtualHost> 

[laszlof]

You might be able to link to that directory, but you have to remember that the license ties to the site IP and directory you have it installed into.

[Peter M Dodge]

There's basically two implementation questions for me and whether the license will see that as one contiguous install is one of them. The other would be how to change the link to admin area if at all possible.

[disgruntled]

There's basically two implementation questions for me and whether the license will see that as one contiguous install is one of them. The other would be how to change the link to admin area if at all possible.

 

 

It isnt possible, well technically it is but you would be wasting your time doing it, your would need to ensure that all of the files were linking relative to the whmcs installation, by this i mean that every included file would need to be using the installations loacation of files.

 

If you are hell bent on doing something like this, move the entire installation to the new vhost. then create your website to use the whmcs api, it is documented on usage of the api.

 

In this manner your clients will see your website only, and the management system on your website will be entirely your own but will link into whmcs to make the changes required.

 

Your clients need never know you use whmcs at all if this is more to your liking and the admin situation will be solved as you will just link to the vhost.

 

 

This will require a license reissue but you will still need only one license.

 

Otherwise you will need two licenses. 1 for the initial installation which you will just rip out the admin folder and not have it., and one for the second instalation which will have your admin area and a htaccess lock out on any directory but your admin directory. they can both use the same database.

[disgruntled]

however, i am still very much of the opinion that it is time whmcs made an API only version that is modular in design so you can add or remove what you need as your needs change as invariably they do.

 

The basis for this already exists, whmcs has an API.