Where Domain Document Root Settings Are In CPanel?
Feb 11, 2008
I've done some manual change of document root in httpd.conf for a user. I know that now, I don't need to to manual change since user can set there own folder!
Now, If I rebuild Apache, he will re-do all the configuration to the original one. Where can I find the settings for domain document root so I can change it and EasyApache will rebuild the httpd.conf correctly?
I don't want to remove the domain since I'll lost all email account!
I am running a LAMP server, working to get everything configured and as secure as I can make it. I have been trying to decide weather to change the document root to a different directory, or if it would be better/worse or more/less secure to chown and chmod the current directory.
Any input would be helpful, I just don't want to overlook some small detail as this is my first time handling a server on my own.
Basic question: does it matter where I set the document root for apache on a Linux system? I've googled this but haven't found a good answer.
This is for a VPS server running the Ubuntu (Debian) server os that I'm configuring. I'd prefer to simply create a new directory off the root and set that as the document root in the apache config file. Would this present any kind of security issue?
If that's no good, what's the best choice -- stick to the default?
After this I did a reboot of the apache server using the CMD httpd -k restart. I even tried restarting using the apachemonitor and rebooted the whole server. But apache still loads the files from c:/Apache24/htdocs
I can't find any more entries with htdocs to change. What am I missing?
i am relatively new to Plesk, i ordered a vserver with Plesk a couple of months ago and spend a lot of time setting everything up and developing several new websites. I am used to developping new websites on a hidden adress (sth like domain.com/dev/ instead of the top level) and then switch the document root to point to the hidden directory when all is done. This practice has served me and my clients well for the last 10 years.
Using the Plesk features like built-in applications seemed like a good idea at the time but wanting to switch the new websites live i have now found out that Plesk won't let me do this since..It is impossible to change document root because there are web applications installed on this website.
I had read somewhere on the interweb that the v12 would let me do this so i just spent the better part of today updating to v12 .. but alas no luck, the limitation is still there. Is there a way to remove this limitation ?
I've got an odd issue here. I have a client who insists on hosting his website with register.com because he knows how to use their editing interface. But, for our purposes, he needed a store set up on my server. So I logged into his register.com account and created an A record for his domain, store.got-harmonica.com and pointed it to my server. I didn't modify the existing records in any way. Now, however, got-harmonica.com (the main site) isn't loading..it just sits and waits and waits. store.got-harmonica.com loads beautifully on my server. Is register.com's webhosting down right now or is it something I've done?
I am trying to change the default php settings under domain (upload_max_filesize & post_max_size) but nothing happens. I am running PHP 5.5 in FastCGI. I also changed it to Centos default PHP (5.4.16) but nothing happens again. It only works when PHP runs as Apache module. The problem is on FastCGI Application.
My server: Centos 7, Plesk 12 Check the screenshot for installed components.
I have a server that I have a few domains on, and I have a question about the root domain. I initially picked any old domain, so now all of my name servers are pointing to this one random domain. I have since purchased a few more premium domains, and am wondering if I should change the nameservers to be the more premium domains? Does this matter? Should I have my "main site" be the root domain? Just trying to understand what the implications could be for me.
I am just wondering whether my idea will work for the google search engine.
Basically, I have my official VPS root (home/admin/public_html/) and this is where my main website will be hosted. However, since my VPS will be used for additional website, I will direct additional domains to it.
My second site hosted on this VPS may have a document root of (home/admin/public_html/advertising/). And my domain will then be setup to have that as its document root.
However, when google searches for my second site (e.g. advertising.com) will it go 'below' the domain root? For example, will it also creep the files under /public_html/ for this domain, even though the domains root is /public_html/advertising/?
edit: Or do people host multiple sites differently? Is this an appropriate method?
I'm using the migrate tool to clone our production server to a backup server.
I'm using the following command
Code: cd /opt/psa/bin/ ./migrate --migrate-server -host x.x.x.x -password mypwd
I've noticed that the per-domain PHP settings (like open_basedir and include_path) are not transmit to the backup server. Is that the expected behavior ? I would have prefer the migrate tool to include all settings....
OSMicrosoft Windows Server 2008 R2 Service Pack 1 Panel version11.5.30 Update #47
We have a few hosting plans setup with different "allowances" for each.The website permissions allow basic html and PHP.In Windows Advanced: The website settings allow for html, php, asp and asp.net
When we change a Basic Hosting plan to Windows Advanced using "Change Plan", it will reassign the subscription/domain to use the new plan, but it will not add-on the extra features in Hosting Settings.
I would like to do do following using basic authentication:
1. non authenticated users have access to the index page: [URL] ..... 2. there are other pages, e.g: [URL] .... but these would require basic auth 3. if users are not authenticated they would be redirected to [URL] .... otherwise authenticated users would have access to [URL] .... or anything else under that domain
I want to add a subdomain foo.bar.com to a master domain bar.com in the subscription bar.com. Normally this works but if I set the hosting type of the master domain to forward, I cannot add subdomains anymore. If I have already added a subdomain, I cannot change the hosting type of the master domain. Also it is not possible to add a second domain to the subscription anymore.
We have more than 10 domains on the same webspace, sharing the same document root. When we try to add a new domain on the same web space (sharing the same document root) Plesk takes a long time to create it (about 10 minutes). While domain creation, all the other domains sharing the same document root and web space get an authentication error. When Plesk finishes, all domains work again.