I have a little trouble with my Apache configurations. I have two computers with Ubuntu and Apache 2.2 - let's call them Home (192.168.1.2) and Server (192.168.1.3) connected with a router. I am working on Home, connecting to Server via ssh and mounting the web root directory of Server to Home via sshfs -> Server's /var/www becomes Home's /home/username/www. The problem is I can't really setup my Apache virtual hosts. I have a project in Server's /var/www/project, respectively Home's /home/username/www/project, and I want to create a virtual host on Home that lets me view the remote contents.
This is what I am adding to Home's /etc/hosts: 192.168.1.3 project
This is what I am adding to Home's /etc/apache2/sites-available/project:
I am running Apache2.2, PHP5.I have been running with virtual hosts on a Windows 7 environment fine for a couple of years successfully, but have just had to move to a Windows 8 environment.It looks like Apache and PHP have installed and are working fine, but my Virtual hosts are now not being recognised. From what I can tell, it is the Windows 8 hosts file that is having a problem, as it looks as though it is now just setup to Block websites.
If I make the host file just have the one line127.0.0.1 localhost entry, then the very first Virtual Host from my apache config file will come up, but the rest are not found.If I put the usual 127.0.0.1 mywebsite.name aliasname is appears as though my website works momentarily and then is blocked..
I just have a question about an Apache 2.0 error. I am running a web host and I am using VHCS for my web hosting control panel which creates virtual hosts in Apache's config files. Whenever I have a certain number of virtual hosts (200 or more roughly) Apache will start giving me problems with no messages about what went wrong. Some examples of what Apache does is that it will crash when I run "apache2ctl restart" or it just won't run when I start it sometimes. It really annoys me since I'm wondering if it's an Apache memory issue. Any ideas on what to do or how to solve this dilemma?
i bought some webspace and i have uploaded mywebsite.I need to configure my domain atomuss.com to have virtual hosts.How is that done?.I have tried contacting my webmaster and it seems he is making himself unavailable everytime i speak want a word with him. Anybody..
I am messing with Apache at home and have managed to create virtual hosts with no problems, my next step was to produce a self signed SSL cert. which again has worked but it's redirecting my non-SSL virtual host to the host I have set-up for SSL for example:
- www.mysite1.com set-up with SSL and works as designed both http and https - www.mysite2.com I don't want using SSL is working fine through http but if you try https it will then redirect to www.mysite1.com
I have been tearing my hair out over this, I have a small problem, I am trying to set up multiple virtual hosts using ssl on port 443. I have followed instructions and set up IP based hosts with my single network card having two different IP's. but the problem is that the second IP is not recieving any requests from the router as it is using the certificate from the first host and diverting to the result of the first sites authentication process.
any one know how I can do this, the first router forwards all requests to the second more secure router which then forwards to the server which is working fine. I need to get this to work and don't know how. both routers support NAT and ther servers first IP address has been assigned a NAT IP.
I can't include the conf file as the board won't let me until I have posted 5 times....but if you need it I can email it or something
the virtual hosts on port 80 are name based....does this matter?
Ok so I just installed apache 2.2 on windows server 2008.
I would like to set it up so if I go to 99.144.79.25(Server IP) I get index1.html. If I go to example.com which points to 99.144.79.25 I get index2.html. If I go to example3.com which points to 99.144.79.25 I get index3.html.
So kind of like, if the domain folder is not found on my server, give the page index1.html.
In the long run I want to run a bunch of sites with different domains, testing right now though.
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
I just installed a new server and I would like to transfer all virtual-hosts on new Apache installation.
I updated all IP addresses in each .config file and simply uploaded the edited conf files into new /etc/apache2/sites-available folder. I rebooted Apache, but through Webmin I can not see them on Existing virtual hosts list. Why? Do I need to manually re-add all the 30 sites?
I have a task of converting a current Win Server based apache server from multiple IP based virtual hosts to a full name based virtual hosting.I'm famiilar with the steps but I was wondering if there are any gotchas in Windows that I should be aware of. It seems that now matter what I change in the new config it doesn't work or work as expected.
What I want to do is setup virtualhosts for my clients and set the user/group that their files upload as. been on google and im guessing ill need to setup mod_auth?
I'm aware that millions of websites using shared hosting are configured with name based virtual hosting.
I'm just wondering now how name based vhosts could be a disadvantage for hosting our websites?
Currently we have a static IP address for each website, apache configured with vhosts for each of these IP Addresses.
I was thinking about re-configuring to name based vhosts, use up less IP Addresses and only have one or two for domains to point to per server.
Is there anything I should know about name based vhosts?
Currently I know of the following issues:
- I can't setup SSL (I don't think?) without a unique IP, but this doesn't matter to me.
- Apache may be making DNS lookups?
This post may seem a bit silly overall, I doubt there is anything important to note about name based vhosts, but just wanted to know if anyone knew something I should know.
Our current ip based vhost setup works, but it would be nice to drop usage on all of those IP Addresses and we have no need for IP address access from browsers and whatnot.
I seem to be experiencing slower bw throughput in speedtests on my server today on a domain that is on a shared ip as a virtualhost in apache 2.2.x on fedora core 6.
Right now this domain is pushing somewhere around 35Mbits out and 1Mbit in.
When I d/l from this domain I see pausing and overall performance is roughly 1/2 of what it was yesterday (400K/sec versus ~800K yesterday), when the site was only doing about 3Mbits.
However, another domain on this same server that is not on a shared IP, when I test it, I get my usual 100% d/l speed.
My server is not under heavy load, .02, .06, .00 with 95% idle cpu.
I'm just wondering, should sites with high bw use definitely have their own IP, as shared/virtual hosting is known to cause slowness?
I am just getting started with my first Linux VPS account and am having a problem that I hope someone can help me with. I am setting up multiple client accounts that will each have access to Tomcat Manager on their own domain so that war files can be deployed to the home directory of the respective account. I was able to get Tomcat Manager going for each domain, but when I try to upload a war file, I get a permission denied error. However, I don't get this error for the main VPS account.
What is the best way to resolve this? Is there a way to link a client account user to an instance of Tomcat Manager? Or do I have to assign the home directory of the account to a group that is common to the tomcat user (assuming that is what Manager is running under)? Or is there another option that is entirely better?
Just looking for some guidance before I hack up my new account too bad.
As far as I can tell, SSL is working perfectly on my server. Though I am wondering why I am getting errors logged? By the looks of it, I've been getting them every day since I opened my server.
Here's a few: [30/Jun/2008 04:30:46 04877] [warn] Init: (host.mywebsite.com:443) You configured HTTP(80) on the standard HTTPS(443) po$ [30/Jun/2008 04:30:46 04877] [warn] Init: SSL server IP/port conflict: mywebsite.com:443 (/usr/local/apache/conf/httpd.c$ [30/Jun/2008 04:30:46 04877] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!! [30/Jun/2008 04:54:05 04877] [warn] Init: (host.mywebsite.com:443) RSA server certificate is a CA certificate (BasicCons$ [30/Jun/2008 04:54:05 04877] [warn] Init: (mywebsite.com:443) RSA server certificate CommonName (CN) `www.mywebsite.c$ [30/Jun/2008 04:54:05 04877] [warn] Init: (host.mywebsite.com:443) You configured HTTP(80) on the standard HTTPS(443) po$ [30/Jun/2008 04:54:05 04877] [warn] Init: SSL server IP/port conflict: mywebsite.com:443 (/usr/local/apache/conf/httpd.c$ [30/Jun/2008 04:54:05 04877] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!
I have a set up where server 1 holds a mysql DB and a virtual host. server 2 holds many virtual hosts in apache (16) connecting to this DB.
The virtual hosts all hold the same script, but the single VH on server 1 receives about the same amount of visits as all the VHs of server 2.
server 1 is very busy at times, like 100% CPU and a load around 10 for long period of times. server 2 is not very busy, around 30% CPU usage and 0.6 CPU load.
Yet, users on server 2 experience *much slower* response times than the ones on server 1.
The obvious reason could be the network between the two, but I'm not convinced (6 seconds for a query run from server 2 when it brings back 1 row and takes 0.01 second from server 1).
Why so many sleeping processes from server 2, and none or almost none from server 1 ? Is it normal that every query from server 2 is open on a different port ? Should they be grouped by virtual host, or is there one different port for each script running concurrently?
What could be a reason for server 2 having problems to open connections on server 1, and how to solve it?
Right now I'm about to deport more users from server 1 to new virtual hosts on server 2, hoping it will lower the load on the first machine and overall accelerate the response times. I just thought I'd post here first because this all seems very weird to me and i thought someone with an external look might tell me what I'm doing wrong. And also if network would be the problem maybe that's not the clever thing to do to make more users remote.
I have set up IP-Based Virtual Hosts, as I have been requested to set it up for SSL.
I have successfully set up all redirects and routes using the IFCONFIG and ROUTE.
My query is this, I have noticed that each HTTP request actually has to come in through the Virtual IP address (which is assigned to each site) from outside. Else it just displays the default host. Does this mean I have to have a separate phone line and router for each web-site I wish to host?
I current have a VPS hosted with a host who rent racks from Gyron.net at Telstra Londong Hosting Center Datacenter (Docklands) and im very satisfied with the network but im looking to change hosts, so im looking to find hosting companies that also rent racks/network from Gyron.net.
So does anyone knows hosting companies that rent space/racks/network from Gyron.net?
Someone had mentioned a way to use virtual apache configs, this way you wouldn't have to reboot apache each time you add a new domain to your box. Can you tell me what dso I need to use?
Also is there a conversion tool to grab the configs you have now, and migrate them to the external files?
For some reason, the first virtual host i have listed in apache2.conf gets all the traffic of all the other virtual hosts listed below it.
Example: Domain xyz.com is listed as the first virtual host. the second, third, and fourth are 123.com, 987.com, and mno.com, respectively (fictitious domains). However, it seems that everything below xyz.com goes straight to xyz.com.
If i switch the first entry, xyz.com with any of the others, such as mno.com, so that mno.com is the first virtual host entry, everything then forwards to that domain.
I'm using the following vhost script: URL...This used to work on an older version of apache in Windows. Now I'm running Apache 2.4.6 on Ubuntu 12.04.
When I type in, for example, dhae.papertower.dev, it processes some scripts internally and moves me to www.dhae.papertower.dev.. and breaks. When I check my log, I find that it's trying to go to the /var/www/papertower/www directory.
I tried adding www.*.papertower.dev to the ServerAlias, but that didn't do it.
I've run into a wall trying to run apache with multiple websites allowing users to use FTPd to manage files.
I'm running FreeBSD 7.1 on Apache 2.2.x
The issue is that Apache runs as www:www but FTPd writes the files as username:client. When performing some scripts that edit back-end files, this obviously can cause errors.
The data for each directory is stored in /home/username/www
I looked into some apache directives I could use. I tried putting User and Group directives into the vhost configuration for each vhost, but that did not work. I even found the perchild module and it looked like it can do the job but was a bit scared and turned off by the fact that it states it is beta at the top of the page. (I cannot link to it because I do not have enough posts.)
I have a virtual host and I want to allow .htaccess files to be used, but that requires to put allow override yes in the virtual host declairation as its off by default, but I get this error:
Starting httpd: Syntax error on line 16 of /etc/httpd/conf/virtualhosts.conf: AllowOverride not allowed here
This completly ditches my whole virtual hosting idea that I've been planing for a while.
Any other way to allow .htaccess through virtual hosts?
Today I configured a Virtual Host (VH) for one of my customers. VH run on WindowsServer 2003 Apache 2.0.59. I enabled mod_proxy and mod_proxy_http modules and successfully loaded. Here is the VH config:
Code:
<VirtualHost xxx.xxx.xxx.xxx:80> ServerAdmin admin@example.com ServerName www.example.com DocumentRoot C:/Apache2/htdocs/www/example.com DirectoryIndex index.php <Proxy *> Order Deny,Allow Allow from all </Proxy> ProxyRequests Off ProxyPass /cms-test [url] ProxyPassReverse /cms-test [url] ProxyPass /cms-eshop [url] ProxyPassReverse /cms-eshop [url] ErrorLog logs/www.example.com-error.log CustomLog logs/www.example.com-access.log combined </VirtualHost> According stated above proxy should map the content of yyy.yyy.yyy.yyy:80 and send it to client... Apache doesn't do that but redirects client directly to yyy.yyy.yyy.yyy instead, even rewriting URL, what is not proper purpose of proxy. I would expect proxy to retrieve content from yyy.yyy.yyy.yyy:80 and forward it to client without URL rewriting. Rewriting URL and direct aiming of client to source of content is unsuccessfull of course, because the source (yyy.yyy.yyy.yyy:80) trust only to xxx.xxx.xxx.xxx which has a right to request a content.
Could anybody explain why proxy doesn't proxy and redirects instead?
