Admin at 22:03, 25 March 2017

2017-03-25T22:03:30Z

← Older revision		Revision as of 22:03, 25 March 2017
Line 95:		Line 95:

	</pre>		</pre>


			[[Category:Apache]]
			[[Category:Nginx]]
			[[Category:Linux]]
			[[Category:Unix]]
			[[Category:Networking]]
			[[Category:Server]]
			[[Category:HTTPS]]

Admin: /* Configuring Apache */

2015-07-01T08:32:33Z

Configuring Apache

← Older revision		Revision as of 08:32, 1 July 2015
Line 62:		Line 62:
	=Configuring Apache=		=Configuring Apache=

	Edit the file <code>/etc/apache2/ports.conf</code> to configure Apache to listen only locally on port 8080:		Edit the file <code>/etc/apache2/ports.conf</code> and change:

			<pre>
			Listen 80
			</pre>

			to configure Apache to listen only locally on port 8080:

	<pre>		<pre>

Admin: Created page with "This page describes how to set up nginx as a reverse proxy server for an apache server. =Why= The reason you would want to use nginx as a reverse proxy for apache is, it allows..."

2015-07-01T08:31:04Z

Created page with "This page describes how to set up nginx as a reverse proxy server for an apache server. =Why= The reason you would want to use nginx as a reverse proxy for apache is, it allows..."

New page

This page describes how to set up nginx as a reverse proxy server for an apache server.

=Why=

The reason you would want to use nginx as a reverse proxy for apache is, it allows you to continue using nginx as the front-facing server for the site, handling all public requests. Requests that don't match the conditions of the proxy are simply treated as usual. When a request does meet the proxy conditions, it is routed to a different local port, where Apache is listening.

Apache is set up to listen only for requests from the local host, meaning our Apache instance will not be publicly visible. Only a local process forwarding traffic to the correct port will be able to connect to the Apache process.

Note that much of this follows the [https://www.digitalocean.com/community/tutorials/how-to-configure-nginx-as-a-reverse-proxy-for-apache digital ocean tutorial here].

=Install=

==nginx==

I'll assume you've already got nginx installed and set up for your site. This should be as simple as <code>sudo apt-get install nginx</code>.

==apache==

I'll assume that you have apache 2 installed. If you don't, try a <code>sudo apt-get install apache2</code>.

=Configuring=

==Configuring nginx==

Now install your proxy "site":

<pre>
$ vim /etc/nginx/sites-available/example.conf
</pre>

Here, we can add nginx directives that specify the conditions for the reverse proxy. For example, if we wanted nginx to forward requests for PHP files to Apache, we would add this block:

<pre>
server {

.............blah blah blah..................

location ~ \.php$ {

proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header Host $host;
proxy_pass http://127.0.0.1:8080/;

}

location ~ /\.ht {
deny all;
}
}
</pre>

This sends any requests for php files to localhost (127.0.0.1) port 8080. This is the port we'll configure Apache to listen to. The second part is to protect any .htaccess files.

Now enable the new site:

<pre>
sudo ln -s /etc/nginx/sites-available/example.conf /etc/nginx/sites-enabled/example.conf
</pre>

=Configuring Apache=

Edit the file <code>/etc/apache2/ports.conf</code> to configure Apache to listen only locally on port 8080:

<pre>
NameVirtualHost 127.0.0.1:8080
Listen 127.0.0.1:8080
</pre>

Now edit the site configuration file,

<pre>
vim /etc/apache2/sites-available/example
</pre>

add a line that looks like:

<pre>

<VirtualHost 127.0.0.1:8080>

<Directory "/path/to/wiki">
Options none
AllowOverride None
Require all granted
</Directory>
</VirtualHost>

</pre>

Nginx Apache - Revision history

Admin at 22:03, 25 March 2017

Admin: /* Configuring Apache */

Admin: Created page with "This page describes how to set up nginx as a reverse proxy server for an apache server. =Why= The reason you would want to use nginx as a reverse proxy for apache is, it allows..."