Nginx - Revision history

Admin at 21:14, 23 February 2018

2018-02-23T21:14:49Z

← Older revision		Revision as of 21:14, 23 February 2018
Line 461:		Line 461:

	Note that these can be defined in addition to any other servers listening on the same ports (80 and 443). They cannot and should not, however, listen on the same port as the app they're directing to (3000 in this case). One app at a time...		Note that these can be defined in addition to any other servers listening on the same ports (80 and 443). They cannot and should not, however, listen on the same port as the app they're directing to (3000 in this case). One app at a time...

			=Note=

			Question: is it possible for nginx to intercept requests for particular files, and serve as a kind of proxy server? (Maybe that answers my question - maybe you need a proxy server.)

			=Flags=

	[[Category:Web]]		[[Category:Web]]

2017-03-26T04:37:17Z

Using HTTPS/SSL with Nginx

← Older revision		Revision as of 04:37, 26 March 2017
Line 368:		Line 368:
	=Using HTTPS/SSL with Nginx=		=Using HTTPS/SSL with Nginx=

	'''WARNING: OUTDATED INFORMATION. USE LETS ENCRYPT.'''		'''!!!!!!!!!!!!!!!!!!!!!!! WARNING: OUTDATED INFORMATION. USE LETS ENCRYPT. !!!!!!!!!!!!!!!!!!!!!! '''

	This is a three step procedure.		This is a three step procedure.

2017-03-26T04:37:00Z

Using HTTPS/SSL with Nginx

← Older revision		Revision as of 04:37, 26 March 2017
Line 367:		Line 367:

	=Using HTTPS/SSL with Nginx=		=Using HTTPS/SSL with Nginx=

			'''WARNING: OUTDATED INFORMATION. USE LETS ENCRYPT.'''

	This is a three step procedure.		This is a three step procedure.
Line 400:		Line 402:
	==Using Certificates with Nginx HTTPS/SSL==		==Using Certificates with Nginx HTTPS/SSL==

	https://sslhelpdesk.com/index.php?/Knowledgebase/Article/View/304/28/ssl-certificate-installation-for-nginx-server		See [https://sslhelpdesk.com/index.php?/Knowledgebase/Article/View/304/28/ssl-certificate-installation-for-nginx-server] and [https://stackoverflow.com/questions/30986980/the-plain-http-request-was-sent-to-https-portnginx]

	https://stackoverflow.com/questions/30986980/the-plain-http-request-was-sent-to-https-portnginx


	=HTTPS Most Of The Things=		=HTTPS Most Of The Things=

2017-03-26T04:35:53Z

Enable site

← Older revision		Revision as of 04:35, 26 March 2017
Line 226:		Line 226:
	$ cd /etc/nginx/sites-enabled		$ cd /etc/nginx/sites-enabled

	$ sudo ln -fs ../sites-available/~~doxuments~~.com		$ sudo ln -fs ../sites-available/domain.com

	$ sudo ln -fs ../sites-available/~~doxcompany~~.com		$ sudo ln -fs ../sites-available/domain2.com

	</pre>		</pre>

2017-03-26T04:35:40Z

Nginx

← Older revision		Revision as of 04:35, 26 March 2017
Line 181:		Line 181:
	==Nginx==		==Nginx==

	I change the domain records so that I have two domains, ~~doxuments~~.com and ~~doxcompany~~.com, pointing to the same server - one single IP address.		I change the domain records so that I have two domains, domain.com and domain2.com, pointing to the same server - one single IP address.

	<pre>		<pre>
	$ cd /etc/nginx/sites-available/		$ cd /etc/nginx/sites-available/

	$ cat ~~doxcompany~~.com		$ cat domain.com
	server {		server {
	listen 80;		listen 80;
	listen [::]:80;		listen [::]:80;

	root /www/~~doxcompany~~.com/htdocs;		root /www/domain.com/htdocs;
	index index.html index.htm;		index index.html index.htm;

	server_name ~~doxcompany~~.com;		server_name domain.com;

	location / {		location / {
Line 201:		Line 201:
	}		}

	$ cat ~~doxuments~~.com		$ cat domain2.com
	server {		server {
	listen 80;		listen 80;
	listen [::]:80;		listen [::]:80;

	root /www/~~doxuments~~.com/htdocs;		root /www/domain2.com/htdocs;
	index index.html index.htm;		index index.html index.htm;

	server_name ~~doxuments~~.com;		server_name domain2.com;

	location / {		location / {
Line 217:		Line 217:
	</pre>		</pre>

	~~doxcompany~~.com points to <code>/www/~~doxcompany~~.com/htdocs</code> and ~~doxuments~~.com points to <code>/www/~~doxuments~~.com/htdocs</code>. Couldn't be simpler.		domain.com points to <code>/www/domain.com/htdocs</code> and domain2.com points to <code>/www/omain2.com/htdocs</code>. Couldn't be simpler.

	==Enable site==		==Enable site==

2017-03-26T04:34:55Z

Set Permissions

← Older revision		Revision as of 04:34, 26 March 2017
Line 169:		Line 169:
	==Set Permissions==		==Set Permissions==

	I have two sites, served by a single instance of nginx out of two directories, <code>/www/~~doxuments~~.com</code> and <code>/www/~~doxcompany~~.com</code>. The permissions on these folders are set following [https://www.digitalocean.com/community/tutorials/how-to-set-up-nginx-virtual-hosts-server-blocks-on-ubuntu-12-04-lts--3]:		I have two sites, served by a single instance of nginx out of two directories, <code>/www/domain.com</code> and <code>/www/domain2.com</code>. The permissions on these folders are set following [https://www.digitalocean.com/community/tutorials/how-to-set-up-nginx-virtual-hosts-server-blocks-on-ubuntu-12-04-lts--3]:

	<pre>		<pre>
	$ sudo chown -R www-data:www-data ~~doxcompany~~.com/ ~~doxuments~~.com/		$ sudo chown -R www-data:www-data domain.com/ domain2.com/

	$ sudo chmod 755 ~~doxcompany~~.com/ ~~doxuments~~.com/		$ sudo chmod 755 domain.com/ domain2.com/
	</pre>		</pre>

2017-03-26T04:33:49Z

← Older revision		Revision as of 04:33, 26 March 2017
Line 5:		Line 5:
	Also see [[Gunicorn]] page for running Python apps on top of nginx.		Also see [[Gunicorn]] page for running Python apps on top of nginx.

	You can also run nginx with Apache. I did this because, as much as I hate Apache, MediaWiki and Wordpress integrate better with it. So I set up nginx as a reverse proxy, so that any requests sent to nginx that are for the wiki or for wordpress are sent through to apache. [[Nginx Apache]] page has details.		You can also run nginx with Apache. I did this because, as much as I hate Apache, all things [[PHP]] ([[MediaWiki]] and [[Wordpress]] and [[Mysqlaadmin]]) integrate better with it. So I set up nginx as a reverse proxy, so that any requests sent to nginx that are for the wiki or for wordpress are sent through to apache. [[Nginx Apache]] page has details.

	=Installing=		=Installing=

2017-03-26T04:32:40Z

Redirecting Subdomains to Ports: Gitea

2017-03-25T22:02:43Z

2017-03-22T08:06:29Z

HTTPS Most Of The Things

← Older revision		Revision as of 08:06, 22 March 2017
Line 426:		Line 426:
	<pre>		<pre>
	server {		server {
	listen 80 default;		listen 80 default;
	server_name www.domain.com domain.com		server_name www.domain.com domain.com
	access_log off;		access_log off;