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'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 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 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:
127.0.0.1 localhost 127.0.1.1 vince-XPS-8300 127.0.0.1 auburntree 127.0.0.1 example
i purchased a VDS and a domain name from godaddy 2 weeks ago. I pointed my domain name to my server and i guess work just fine. but when i googled my domain name i found a damain which is pointing to my website. how can a stop this domain from pointing to my IP?
i have dns problem as i think idont know how to solve it or how did it happen iam using this site from more than 8 month i registered it in godaddy as my main domain name register and iam hostingit on my ressler account with many other domains but last night i found that the domain is pointing to my server but it show godaddy parking page i cheeke the name serv its pointing to me i do this repport in dns test i found it is also pointing to go daddy how can that happen and how can i solve it to show my web site again:
(Background) Looking for some advise on domain pointing currently I have a UK server hosting my billing system which is replicated each evening over to my US server
I want to sub domain my primary domain to uk.yourdomain.com & us.yourdomain.com
As redundancy I would also like uk.yourdomain.com to point to the US server should the UK one fail - giving me redundancy, I figure in the next few months I can do this on our AU - creating au.yourdomain.com and replicating our billing system to that datacenter too.
(question) - can this been setup and configured from server level, ie on my primary server WHM dns zones OR should this be created on a registrar level?
I have a domain incl. hosting (fanferwalde.com) and three extra domain names, fanferwalde.nl , fanfalingasate.com , fanfalingasate.nl (all three without hosting) who I want to point to fanferwalde.com.
Before I bought the extra domains I asked the provider if I could point the extra domains to the “head” domain (fanferwalde.com). Yes, that was possible they said so I bought the extra domains. I asked the provider to help with the configuration to point them to the head domain but they refused, I must do it by myself…………………….. There is no possibility they do it when I pay extra for it so I feel pressed to take also a hosting for the extra domains; then I can make a redirect on each index page.
All domain names have an own DNS control panel. I have full access to this.
The first picture is the DNS from the head domain.
The second picture is the DNS from one of the extra domains I want to point to the head domain.
What must I put where so the website from fanferwalde.com will appear when I write fanferwalde.nl in the browser? THANKS in advance!!!
I have a server running IIS that I have a primary website hosted on, let's call it...foo.com
So foo.com is hosted and setup through IIS, resolving fine. Now, I have created a site on a different server (not on the same network) to run a subdomain called 'local.foo.com'. How do I get IIS to point all traffic for local.foo.com to the IP of the server hosting the subdomain?
I tried adding a hostname to the primary domain in IIS through "Properties" > "Web Site" > "Advanced" but I am stilling getting the Invalid Request Bad Host Name error.
I'm designing a site, www.streetsmartscooters.com, to (obviously) sell scooters. Just yesterday I saw on my Google Analytics that people were getting to my site by searching for X-treme X-10, a particular brand and model of scooter.
I typed the keywords into Google to see what my rankings were, and I was on the fourth page. But the green URL in the search listing showed up as mamafocka.com.
When you go to mamafocka.com, it's all the same information as my website, and changes I make through my FTP login update immediately. If you go to streetsmartscooters.com, you can click on the "Electric Scooters" link on the left nav and it will keep you on mamafocka, but give you the exact same page as on streetsmartscooters (I set that particular link to be relative in the includes file).
My site is hosted on a Windows 2003 virtual server from GoDaddy. SelfSeo.com says that mamafocka.com and streetsmartscooters.com both have the same IP - 18.104.22.168. I just signed up for a dedicated IP address tonight from GoDaddy, but I'm not sure how long it takes to propagate.
Will getting a dedicated IP fix this problem, or have I wasted 6 bux? Is there any way to block that domain name from pointing to my site? It doesn't look to my novice eyes like this is a redirect.
Also, I installed FreeFind on the site earlier this week, I believe. Could somebody have messed with something through that?