Server :: SSL Certificates And Virtual Hosts On Apache
Jan 9, 2011
I run couple of sites on a virtual hosting environment and I am in need of adding additional SSL for a different domain name. From what I read on some forum topics indicate that SSL cert requires different IP address. meaning one cert for each IP. Is this true? If so, then I'm having some difficulties understanding the benefits of running virtual host if a server can't host multiple secured site through single IP. Any way to run multiple ssl site within virtual host environment. I'm hoping for a possible workaround.
apache virtual host to limit the concurrent connections of virtual hosts? Taking into account the host of each virtual user's home directory can also have more than one subdirectory, which should be restricted to a subdirectory. Is beyond the control of the operation of these sites in a subdirectory. Best local restrictions or limitations to the overall situation.
What is the (officially) proper way to configure Apache so that a given IP address can have two or more virtual host names, each going to different distinct configurations (e.g. with different DocumentRoot, Alias, etc), and also do this for the IP address so that it goes to a designated configuration rather than defaulting to the first or a random host name?
Apache documentation does not appear to address this. If so, it has it hidden in a non-obvious place.
First of all I've looked at "similar threads" without finding an answer. I'm setting up Name-based VH using an IP as the base. The OS is CentOS 5.4
My config looks like:
NameVirtualHost 12.345.678.90:80 # # NOTE: NameVirtualHost cannot be used without a port specifier # (e.g. :80) if mod_ssl is being used, due to the nature of the # SSL protocol.
[Code]...
The names are of course not in DNS so to access the server from my local Windows machine I had to use the hosts file: 12.345.678.90 dev1 Entering dev1 in my browser *does* take me to the server but it takes me to default VH (DocumentRoot /var/www/html). What am I overlooking?
I have just setup two Apache virtual hosts and I was wondering how I could link them to different domains so that they could be accessed from another machine.
This really has me baffled! I'm running Apache 2.2 on Windows Server 2003 (I know, my first blunder). I can edit existing virtual hosts without a problem, for example, I can change this existing vhost to point to a different document root and it works fine:
But the moment I try to add a new virtual host, it doesn't get recognized! When I try to browse to it in a browser, I get a "Server not found: Firefox can't find the server at newsubdomain.mellemallc.net."
I am trying to run two web servers (Virtual Hosts) on a single Linux Centos 5.5 box with a single IP address 192.168.0.182. I did all the pre-installation requirements such yum install mysql, yum install mysqladmin, service httpd start, service mysqld start etc etc.In /var/www/html directory, I have two folder called server1 and server2. These two folders have the necessary web server php script files and folders. I opened the browser and managed to install the script on one web server successfully. When I put the IP address 192.168.0.182 on the browser address bar, the page loads without any problem. Now I would like to be able to install the other web server script and I don't know how to?Here is my httpd configuration;
How to best manage both http and https pages on the same apache-server without conflicts. For example, if i have both 000-default.conf and 000-default-ssl.conf pointing to mydomain.com, and don't want users who visit mydomain.com without specifically type the https-prefix to be redirected to the https-page - how to handle users using browserplugins such as https-everywhere etc?
Another option would be to create a subdomain ssl.mudomain.com and have users who want to reach the ssl site to have to type ssl. I have tested several things with https everywhere enabled in my own browser, and it seems really hard to make this working the way i want, in one way or another i always end up getting redirected to the ssl-site automatically.
The reason i need this to work is because i run one site that i don't care much about SSL, that is the "official" part of that site, and i also host some things for friends and family on the SSL-part. This would not have been a problem if it wasn't that i use self-signed certificates for my ssl-site and the major user become afraid when a certificate-warning pops up in their browser and therefor leave the site.
I'm wondering if this is even possible before I start the learning curve with Ubuntu and apache virtual hosts.
I have a static external IP address that resolves to the various domain names I will be using. I have a web server inside my network with a private IP address and any http request to the firewall is forwarded to the webserver on the appropriate port. This setup works well when using the same web page/configuration for all of the domains.
Will it be possible to use named virtual hosts in this configuration, or will the NAT'ing interfere?
I am trying to configure Apache to handle virtual hosts. For this I un-commented the line in httpd.conf that say
Include /etc/httpd/extra/httpd-vhosts.conf Then I included the following in httpd-vhosts.conf: <VirtualHost *:80> <Directory /var/www/git.localhost/gitorious/public> Options FollowSymLinks AllowOverride None Order allow, deny Allow from All .....
I'm having trouble implementing SSL on a AvantFax login screen. I've created the the certificates and keys and have them stored in /etc/apache2/ssl and I'm sort of stuck now. I've been following a guide but any changes to the conf files leads to errors. The system I'm using is Debian 5.0
I currently have an Apache Web Server running on Ubuntu 10.4 and I use a DynDNS service to make them accessible to the outside world via a domain and/or subdomain.
This works fine from access outside of the network and all subdomains resolve to the correct directory.
The problem I am having is with accessing a subdomain over my internal network.
I can access the Web Server using the server's IP address: http://192.168.1.123/ but this always takes me to the same virtual host and I don't know how to distinguish between different virtual hosts (different subdomains).
Ideally I would like to access the same subdomains using http://<subdomain>/ where <subdomain> is the same as the subdomain attached to the external domain name.
I have Apache up and running and have a few virtual sites enabled. All these sites belong to the same user and group and the directory root for each site is in /home/{same-user}/www/{site-name}/htdocs/
I use Samba to connect from Windows to these directories and by default, files and directories are saved as the {same-user} and {same-group}. My question is, would it cause a problem if I changed the user and group in the virtual server directives in /etc/apache2/sites-available/site.conf files, giving apache permission to write to these files and directories. In the past I have changed the user and group to www-data (the default) but this seems inefficient an cumbersome compared to what I intend to do.
I use the server mostly for development, although at times I have a small site or two available to the public. Before I do this I want to be sure I'm not leaving a gaping security hole by changing these things. If this is all wrong, what is the standard way of running virtual hosts from apache and what is the standard document root for virtual sites?
I don't know if this should be a followup to my prior topic [URL] ....
Each of the pieces I've installed all have an "Alias" directive in the conf file to link the directory where they live to be present on my server. For instance, DotClear lives in /usr/share/dotclear/web/ and there is a directive
Code: Select allAlias /dotclear /usr/share/dotclear/web that directs http://myserver/dotclear to that site.
Now, I've set up VirtualHost entries for my DotClear and Owncloud with their own hostnames.
The problem is when I go to [URL] ...., I get to my mythweb site.
This is not so good. So, for the sites that have their own hostnames, I removed the "Alias ..." directive. Of course, now I can't get to the hosts by going to the primary site which is probably fine, but I also still get my mythweb since that doesn't have it's own virtualhost entry.
This doesn't seem like correct behavior. Is there a better place to put the "Alias ..." directive so that it only works from one site and not all of them?
I am also thinking I should just link the directories into /var/www/html, but I'm not sure that's a better solution.
I run a dedicated opensuse 11.1 server with apache (2.2.10-2.9.1) installed. This box has been running for nearly 2 years hosting several low traffic websites. I must admit that I did not give lots of love/attention to the machine over that period. It ran rock solid. The different websites each have their own associated user account and are stored in their own /home/name/public_html/ folder. It was setup through Webmin. Each domain name is also linked to a unique IP (the box has multiple available IPs), however this is configured at my domain provider. All in all a very simple and straightforward setup that never let me down most of the past decade.
Recently the sites on the machine were no longer responding. This happens each other year or so since I write my logfiles to a separate partition. Was df -h and indeed, partition was full. Removed logfiles manually, and while I was at it I decided it was time to run an online update (yast2 / online update that is). Rebooted machine after yast telling me to do so. Sites are no longer working. Can no longer login to webmin. Only thing what works is the 'root' webpage (/srv/www/htdocs folder), which makes me rather clueless as the other sites are just not responding at all, not even a timeout or error message.While I know that deleting logfiles manually is quite stupid, I've done it fore and not really ended up in trouble.
Hence my questions: does this sound familiar to anyone and do you mind to give me a clue about where exactly I should start to look. It's been ages since I actually administrated apache, so I might overlook the obvious. Long story short: any tips are very welcome about what I should check first, what config files might have been changedith the update, etc ...
I'm having an issue with setting up the virtual hosts on my web server. I have 2 virtual hosts (example1.com, example2.com). example1.com works but example2.com is sent to the index file of example1.com. I did some searching on google and it seems the problem might be with my /etc/hosts file.
First virtual host that the second is also directed to...in sites-available/sites-enabled (note port 80 is blocked by my isp so I use 8080)
Code:
Second virtual host file
Code:
And my hosts file
Code:
# The following lines are desirable for IPv6 capable hosts
Also I'm using a dyndns.org...would that make a difference?
I'm trying to set up a 2nd SSL cert on a different domain on a server, each domain has its own IP address, the problem is the Web developer that configured the first domain specified ssl keys for the primary domain in both the vhost config in httpd.conf AND in the ssl.conf config files. If I attempt to remove the keys form ssl.conf the server will not start up. and with them there It will not start up if I specify keys for the secondary domain.
i use virtual hosts to develop several web applications. These are located in my home folder under /home/user/projects/project After a fresh installation, i always get a 403 forbidden error. After googling and reading on this forum, several solutions are mentioned for this problem. But i can hardly believe putting using a chmod 755 on my home folder is a correct solution. What is the correct way of doing things in this situation?
I run a web server on Fedora 12, principally using Apache, MySQL, and PHP. I host a variety of sites, one of which is a family website that contains semi-sensitive personal data for several hundred extended family members, who all have access to the database-driven site.
Until now, I have been using a self-signed SSL certificate to encrypt the data as it is read and written back and forth from my database. Family members have simply had to put up with clicking past certificate warnings as they enter the site, as most browsers flag self-signed certificates as bad. It hasn't really been that much of a bother, but I'd love to do it more professionally. I have looked into buying SSL certificates, but it's a site I host for free and would rather find a cheap or free alternative if possible.
So I'm just fishing for ideas to work with. What are some alternatives to using SSL certificates for moderately strong website encryption? So far, I run only one host on the domain, but may eventually need encryption that would support multiple hosts. Or does anybody know a way to make self-signed certificates work on most popular browsers without being flagged as suspicious?
I have been searching and reconfiguring for 6 days now and have lost several clumps of hair.. PROBLEM: I want 2+ virtual hosts on my ubuntu server (1 ip) BUT - Only the first "alphabetically" listed sites-enabled shows.
000-default [URL]
Individually they all work (if i a2dissite for each leaving 1)
[Code]....
it seems i have tried everything that everyone else is having issues with but nothing seems to fix mine. Possibilities:
1) EC2 2) Permissions on the files - I changed everything to the apache2 user "www-data" - no dice. 3) I am a dope...lets hope its that and one of you kind people point me to my issue.
I have a CentOS 5.5 Server and I'm hosting 3 different Name-based Virtual Hosts. Using Joomla 1.5 for the site. Each VHost has it's own subdirectory under /var/www so I have .var/www/vhost1, /var/www/vhost2 etc.
It works perfectly, but I'm getting a lot of unwelcome spiders and bad bots trawling for MP3 files because there are a few MP3 files on one the sites. I've added all the Bad Bots to my .htaccess file and now I need to know if I should make only ONE .htaccess and put it under /var/www OR create a different .htaccess file for each vhost (this would be an ideal solution, but I'm not sure if it can be done).
Ok I have 5 virtual hosts on one IP but only 1 domain (forwardconference.org) will be sending emails out to people....confirmations and such. The other sites may send out some emails...like back to my personal email address not hosted on this server. That works. But to people on like aol or yahoo or hotmail....it doesnt
Problem is, most people are not getting the emails. Mailq reports them being deffered for some reason. I'm having our ISP setup a PTR to forwardconference.org....does this mean all my emails from either of the sites....even if I put a different FROM: address in the php mail script...will come from [URL]? Or should I just setup my server as its own SMTP server?
I have several websites available via both HTTP and HTTPS, with images served from a separate virtual host. This breaks in IE because the images are loaded by the CSS, and because they're in a separate Virtual Host, I have to use absolute paths in the CSS.
Example:
[URL]
Renders in IE like this:
[URL]
The issue being that the wiki.archserver.org is being served via SSL, but the header logo is served by img.archserver.org and the CSS uses the absolute path [URL] to load the logo. So, the only solutions I can see are:
1) Change the CSS to always use SSL. This will slow down the site, increase load on the server and is generally a poor-practise as a "solution"
2) Maintain 2 copies of the CSS, serving a HTTP version to HTTP requests, and HTTPS version to HTTP. This creates a management overhead which is less than desirable.
3) Create an Alias in Apache to send requests for [URL] to [URL] internally then rewriting the CSS to use relative paths.
4) Screw IE; it works in Firefox, Chrome and every other browser AFAIK. The sites are for a Linux project anyway.
I am upgrading my server and I have a lot of sites. Since I cannot take my server down for a few days, maybe a week until I manage to migrate all the sites to the new machine, I figured I could migrate them one by one. After migrating one, I would somehow tunnel the requests of that name virtual host to my internal machine. When everything is migrated, I would then switch the machines, update ip's and stuff and everything will work just fine.
However I cannot seem to find a way to do this tunneling. is this at all possible? If not, what alternatives do I have?
I created LAMP server with a wordpress site. I created a sites-available file for the wordpress file pointing to the wordpress directory. Within my server it goes to the site properly. However I also made this server a DNS server, had another test pc use it as a DNS server and it only got the default apache page unless I added /wordpress to the url which makes it point to the directory within /var/www/ that it belongs, but then the wordpress links don't work and this is not what I want it to do anyway. I do not understand why it is working properly internally but not externally. It makes me think maybe the sites-available file is not allowing outside access appropriate permission to use it or something. Can somebody please point me in the right direction I have been working on this for weeks and I am starting to get really frustrated with it. Tell me what config files can help you figure out my issue. Also I eliminated the default index.html file so it wouldn't use it, then placed the index.php file from wordpress in /var/www/ root but in that configuration it doesn't load anything by default but will still work if you point to /wordpress. I believe I have to make some change to my apache2 configs to allow outside PCs to be pointed to the right root directory for the virtual host like is being done internally, I just don't know where to start.
Is there some way that I can use apache/iptables to serve both of my servers through the same basic domain? I'm not talking about VirtualHosts either, I don't believe ( despite the fact that's all I can find anything to read about on Google when searching for this ).
Anyway, the problem is that I have a TorrentFlux php torrent-client that I run so I can add stuff to the download when I'm not around. I don't want to put this on my regular webpage server because there's just not enough diskspace in that machine. On the other hand, I don't want to replace that server all-together because the other machine is my desktop and would not make a reliable host.
So my idea was that there could be some way to have the apache2 server on my dedicated server redirect a subdirectory in its webroot to the webroot of my desktop's TorrentFlux server, but over standard HTTP ports so that it is more like the server is serving up the content of my desktop server through its HTTP service, instead of simply redirecting.
The reason I want to do this is because so far I have to use the TorrentFlux server on a nonstandard port so my dedicated server can still host its own things on port 80, but I've been running into several situations where the browsers I want to use do not support the nonstandard port such as with some instances of IE or the browser on my BlackBerry.
Anyway, I'm not looking for a step by step or anything ( though it couldn't hurt ) but I just need some ideas on what I could search for to get some better ideas. There's probably some term for what I want to do I'm not even aware of that would help me greatly.
Runnining Ubuntu 7.04 and apache 2.2.4 along with shorewall 4.0 as my routing/firewall software.
I have set up a SSL site for my default Apache server. But I want to set up multiple SSL sites for multiple IP based as well as Name based Virtual hosts. Is there a way where in I can include definitions for SSL certificates and keys within the Virtual Host directive in the httpd.conf, so that I can specify separate key and cert file for every Virtual Host.
I'm trying to set up my web server (nginx) as a catchall virtual host, as per an example that can be seen here: [URL].. (It's the Wildcard Subdomains in a Parent Folder example). Now, here's my issue. I use Wordpress on the coburndomain.org domain. I have pretty URLs enabled, that make my Wordpress articles look like this:[URL].. At the moment, nginx is reporting 500 Errors, saying that index.php is not a directory. What I want to do is make a rewrite rule that allows me to use the above URL example with nginx.
I followed this tutorial to do so: [URl].. , but I'm not sure how to apply it to my setup. Here's my configuration files from Debian Squeeze with Nginx onboard:
