Skip to main content

Changed primary domains document root and it shows correctly on cPanel yet the site still loads old document root

jenkinsmi
Hey guys we've been working to change the main document root for our website... 1: We changed the main domain root in the files within: cpanel/userdata/servername, in both the main file and SSL files, and then deleted the two cache files. 2: We also changed the main document root within the server itself on both https and http, in a file like this e.g. "/etc/apache2/conf.d/userdata/std/2_4/SERVERNAME/MAINDOMAIN.com/*.conf" And also in "/etc/apache2/conf.d/userdata/ssl/2_4/SERVERNAME/MAINDOMAIN.com/*.conf" 3: We then also changed the main document root within the main server config file however the bit above should overwrite that. cPanel now says the correct document root, we've cleared cache on cloudflare... however when you put the url in it still loads as if it's still pointing at the old document root. Any ideas guys? We're completely stumped!

Comments

11 comments

Date Votes
  • cPRex Jurassic Moderator
    Hey there! You should not need to do anything inside /etc/apache2/conf.d/userdata/std/2_4/SERVERNAME/MAINDOMAIN.com/*.conf as those are include files that would not be related to the document root configuration. However, if you have custom includes that were set up manually at some point, you would also need to update those. Can you follow the details here and let me know if you get better results?
    0
  • jenkinsmi
    Hey cPRex thanks for helping Sadly changing the document root in those two files, and then running those scripts and commands does not work. On cPanel it says it's pointing to the right folder, but the result is still when loading the site it loads from the old domain root, proved by doing a die("here"); in the old directories index.php which shows up. Any ideas?
    0
  • cPRex Jurassic Moderator
    I don't really have any other ideas on that one - we've been using the same process to update the document root for many years and it's always performed well. It might be best to open a ticket with our team so we can investigate that on our side. If you do open a ticket, please post the number here so I can follow along and make sure this thread stays updated.
    0
  • HostNoc
    HI Please try to change that document root in your main apache configuration file for that domain. and then try
    0
  • cPRex Jurassic Moderator
    @HostNoc - users should not be editing the main Apache configuration file on the machine as those changes will get overwritten. I suppose this could work as a temporary test, but it would not be a long-term solution to the issues the user is experiencing.
    0
  • Ben Taylor

    Hi,

    I just transferred an account and am experiencing this issue with the main domain. I can see the way you change the doc root has changed since we last done this maybe a year ago?

    In domains it is pointing to the correct document root(Like it was in the old account) but on the domain it points to the old wordpress website. 

    Now I can see that changing the main domain document root needs to be done partly in WHM and then creating a parked domain or something? but we changed the document root before you guys changed the way it must be done. So how can I get the correct document root showing when everything looks correct?

    0
  • cPRex Jurassic Moderator

    Ben Taylor - so you're saying that in cPanel >> Domains it looks fine, but when you visit the site it is pulling the old content?  If that's the case, are you sure that the domain's DNS has propagated to the new system since the transfer happened? 

    0
  • Ben Taylor

    @cPRex Yes. Doc root is correct, but old content as in doc root from one year ago(ish) is showing. I changed doc root last year. It has been fine until the transfer today. Every other domain has propagated ok, it is just the main domain that has the issue. 

    It was a wordpress install, but upgraded to Laravel last year. I deleted the wordpress database tonight to see what would happen as we no longer need the DB and got a wordpress error

    Very strange!?

    0
  • cPRex Jurassic Moderator

    It might be best to create a ticket on this issue so it can be investigated directly on the server.

    0
  • Ben Taylor

    Hmm I have only just installed cPAnel. I have paid for a licence, but it says my server is not licenced.

    I am trying to find out how you activate the licence but cannot. Any idea how I activate the licence?

    0
  • cPRex Jurassic Moderator

    It's likely happened by now automatically since it has been 8 hours, but you can run this command to force an update of the license check:

    /usr/local/cpanel/cpkeyclt
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post