However, I plan on running multiple website (not linked whatsoever) on the server. I have LXAdmin and HyperVM. Is it possible to get additional files, such as:
/home/site2/public_html/
then etc..
/home/site3/public_html/
Is this possible? Because, would each need its own IP for the DNS?
And I think everything is working. When openingen 127.0.0.1 I see the apache message that the server is running and when executing phpinfo() it displays the PHP info.
My problem is that I'm trying to change the document root.
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 installed a centos4.7 with ISPCONFIG2 control panel, but any account I create it points to the documentroot of apache.
I am running my server behind a router.
On the /etc/httpd/conf/vhosts/Vhosts_ispconfig.conf the document roots are : Document Root /var/www/web11/web for xxx1.com Document Root /var/www/web10/web for xxx2.net
but when i type ant site, it goes to : Document Root /var/www/
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.
I bought a new plesk and created new domains. For some odd reason, all the domains are looking at the default document root.
/var/www/vhosts/default/htdocs/ Rather than going to the domains document root /var/www/vhosts/domain.com/conf
I checked the /var/www/vhosts/domain.com/conf/httpd.include, the document root and all are fine.
I also tried creating vhost.conf and assigning the document root there. /usr/local/psa/admin/sbin/websrvmng --reconfigure-vhost --vhost-name=domain.com -v
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?
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!
There is a bug in the current Plesk version 12, which was encountered on many of our Plesk 12 server until now. I do have Plesk 12.0.18 Update #23 with CentOS 6.
When a customer changes for example the document root of a domain nginx does not recognize it and the administrator of the server do have to restart nginx manually.
This issue is serious because CSS, JS and images are not working on such a page where a customer changed the document root. Nginx is throwing 404 error until nginx is restarted manually.
Other customers do have the same issue: [URL] .....
Is it possible to change to root password to a VPS from inside HyperVM? I currently have 4 VPS's setup and I need to change the password for one of the VPses. Can I do this from inside HyperVM without having to go to SSH?
I have read that although chained root ssl certificates can be more difficult to install they are actually more secure since the root certificate cannot be compromised, only the intermediary.
Is this true? It looks like both google and amazon both use chained SGC certs.
I have a client who specializes in providing training for high-end CAD/CAM applications. They have training modules (currently in .ppt format mostly) that they want to store securely on the server and give out access only to approved customers. Additionally, they want to ensure that these training modules never fall into the hands of their competitors- that is, no downloads.
Does anyone have experience with this kind of thing? Based on their requirements, a few possible solutions come to mind:
1.) Put the training modules in a subdomain that is password protected. Additionally, encrypt the traffic with SSL etc. However, this doesn't solve the problem of users being able to download the files and do what they want with them. Also, it isn't possible to view .ppt files online in a browser, as far as I know.
2.) Use a solution similar to what Lynda.com has. They have an entire online library of training videos that are available 24x7, but customers can only view it, not download it. I think they use some solutions from Adobe to make this possible.
I am trying to configure Apache 2.2 on Linux Mint 17 ( derived from Ubuntu 14 LTS).
I am wanting to create a variety of localhost sites all for development. One of those is built on Laravel 4. I have followed every tutorial I can find yet, for some reason which I do not understand ALL my sites route back to the Laravel root document when called from the browser. Just don't get it.
Here is my hosts file:
Code:
127.0.0.1 localhost 127.0.1.1 vince-XPS-8300 127.0.0.1 auburntree 127.0.0.1 example