Results 1 to 10 of 10
  1. #1

    installing whmcs in root or sub-directory

    Hi.

    I always have this doubt on which is more advisable, installing directly in root, or into a sub-directory.
    I see many have it installed on a sub as "client area", according to whmcs there is no difference as security, so it comes to "startegy", looks, and usability.

    Will you please tell me your thoughts about this, pro and cons, etc.

    Thank you

  2. #2
    Join Date
    Jun 2009
    Location
    Bristol, UK
    Posts
    232
    The installation path won't impact security, however having scripts ('software') installed on the same account as WHMCS is risky, because that software may have an exploit an attacker could use to break into your WHMCS.

    If you want to do full integration with the WHMCS template system then you'd want to look at installing it in the accounts root directory, main benefit is the domain is the same, so it doesn't go to client.site.com when going to whmcs specific pages.

    If a standard header/footer type integration is all you need then you can go for a subdir install.
    | Galaxy Web Solutions Ltd
    | cPanel, cPanel Reseller, Master Reseller, Shoutcast/Icecast + Shoutcast/Icecast Reseller Solutions
    | Cheltenham based servers housed in our own private rackspace. Server Colocation & VPS also available!
    | GalaxyWebSolutions.com | 0800 520 0107 | 01454 620 217

  3. #3
    Join Date
    Mar 2011
    Posts
    4,124
    It boils down to your personal preference. You could have it under a subdomain and have an SSL in the subdomain alternatively you could have it as a subdirectory and protect your entire website with a SSL
    Kushal || Host4Geeks || Operating Fully Owned Infrastructure out of 4 Global Datacenters US / UK / India
    Reseller Hosting - Pure SSD | Nginx + LSAPI | Let's Encrypt | WHMCS or Blesta | DDoS Protection| 24x7 Support
    Fully Managed SSD VPS - cPanel /WHM | Softaculous | Let's Encrypt | DDoS Protection | Proactive Monitoring | Server Hardening
    Datacenters - Los Angeles, CA | Lenoir, NC | London, UK |Pune, India

  4. #4
    Join Date
    Sep 2002
    Location
    Top Secret
    Posts
    14,135
    Personally, I throw WHMCS in it's own user. Better protection, I can play a good bit with things, and from my own experience it's just better off. To each their own though, just make sure you follow the further security steps, these are critical
    Tom Whiting, WHMCS Guru extraordinaire
    Linux problems? WHMCS Problems? Give me a shout
    Check out my WHMCS Addons

  5. #5
    Thank you all for the replies.
    I have already followed the security stuff.

    So from what I gather if no specific reason/need root is the choice.

    Personally, I throw WHMCS in it's own user.
    I guess by "own user" you too mean account's root, right?

  6. #6
    Most people use the main domain landing for the product and service information and WHMCS is a subdomain for checkout / account management. So in this case domain.com/customers makes sense. As well I recommend this to a subdomain as you will have to purchase an SSL specifically for that sub-domain, opposed to just the main domain..
    Matt Martin
    nurango Telecom
    Secure SIP Solutions
    https://www.nurango.ca

  7. #7
    Join Date
    Nov 2011
    Location
    Nasik, MH,INDIA
    Posts
    862
    Its always good to have WHMCS on the root (Main Domain ) instead of a Sub domain

  8. #8
    Thank you all for the input.

  9. #9
    In stead of main website, it is better to install it on sub domain, for example like manage.yourmainwebsite.com.

  10. #10
    Join Date
    Oct 2004
    Location
    Brisbane, Australia
    Posts
    259
    Quote Originally Posted by dareORdie View Post
    Its always good to have WHMCS on the root (Main Domain ) instead of a Sub domain
    I disagree.

    Ideally your billing system should be running on its own locked down system (separation of concerns, not to mention you don't want a vulnerability in your CMS allowing for sideways escalation into your billing system). Having the billing system on a subdomain allows you to point it to a different machine without the need to proxy requests, and in the case of those lacking the extra infrastructure to run a separate box- the ability to easily migrate to a new machine when it becomes possible without breaking links.

Similar Threads

  1. Replies: 4
    Last Post: 05-08-2012, 09:25 PM
  2. chown all cgi-bin directory to root:root
    By esmailnejad in forum Dedicated Server
    Replies: 3
    Last Post: 01-04-2012, 11:43 AM
  3. Replies: 4
    Last Post: 12-05-2011, 10:32 PM
  4. Installing apps to the subdomain's root?
    By rarename in forum Hosting Software and Control Panels
    Replies: 0
    Last Post: 10-27-2006, 04:26 AM
  5. Installing PHPbb on Root
    By deet in forum Web Design and Content
    Replies: 2
    Last Post: 04-11-2005, 02:50 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •