Apache :: Why All Virtual Hosts Route Back To Same Document
Oct 7, 2014
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:
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 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 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 126.96.36.199(Server IP) I get index1.html. If I go to example.com which points to 188.8.131.52 I get index2.html. If I go to example3.com which points to 184.108.40.206 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 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.
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 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!
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?
I have a managed box with rackspace (green) On this I am running a couple of distance learning sites e.g howtofish.com (moodle on apache) and video streaming (lighttpd). This is all working fine.
I'm now looking at moving our "normal" website (drupal on apache) to a managed server with rackspace. (call this blue)
The 2 different parts will be running on 2 different machines, but I'd like to be able to move sites/applications between them if needs be due to load/work/failure
For example if the normal website server goes down, temporarily move that on to the distance learning/media server or vice versa. Or if after a while we get more traffic on the distance learning server than the website, move the media server over to the normal website server.
Hope that makes sense - I'm not looking at a proper cluster here, but 2 servers I can juggle things between if needs be.
The way I'm thinking of doing it is having both machines with the same setup (apache port 80 and lighttpd port 81 for streaming) And use Vhosts on both machines setup for all the sites. i.e. green.flyfishing.com and blue.flyishing.com each have vhosts setup for flyfishing.com, howtofish.com and fishingvideo.com.
This way, whichever server the dns for flyfishing.com points to goes there, and the same for other services.
Then do a nightly backup of the mysql databases to the other server and keep files rsynced.
Then if a server goes down or I want to move x from green to blue I just load the backup of green database for the relevant application on the blue server and point the dns entry for the app to blue.
I'm using Apache 2.4.4 as a part of WAMPSERVER 2.4 under Windows Server 2008 to host a business web application. I recently added a tool that involves users accessing the application from their mobile devices connected through our wifi network.
The issue occurs when a user is connected via our external address(x.x.x.x:8080). This issue does not occur if connected through our local address(192.168.x.x:8080).
First, the user makes a POST request to our server. The server handles the request and redirects the user to a GET version of the same page. Standard stuff.
However, if the user leaves the network while this process is occurring, the entire server will stop sending back responses. Localhost, x.x.x.x:8080, and 192.168.x.x:8080 all fail to receive responses until the Apache service is restarted.
If that isn't bizarre enough, my access.log continues to be filled with requests and my apache_error.log doesn't report any issues and even reports when the server is being restarted.
At first, I thought this might be a routing problem since it only occurs when connected though our external address and it isn't typical as far as I know for ALL Apache childs to become unresponsive. However, not being able to access the application through even localhost made me rethink that. So, I'm thinking it's a Windows or Apache issue, but that's as far as I've gotten.
This makes our application nearly unusable because it's a system for punching in and out of work, so it's likely people will be trying to punch out while leaving the building and network, causing this issue.