Nginx - Revision history

AGindiri: /* Addendum : 02/07/2023 */

2023-02-09T21:00:43Z

Addendum : 02/07/2023

@@ Line 11: / Line 11: @@
 If you've just installed a new operating system, you'll want to update your local package index by running <code>sudo apt-get update</code>, and then add the Universe repository by running <code>sudo apt-add-repository universe</code>.
 ==Installing nginx==
@@ Line 148: / Line 153: @@
 - Tyler & Luke

AGindiri: Added an addendum

2023-02-07T21:30:52Z

Added an addendum

← Older revision		Revision as of 21:30, 7 February 2023
Line 148:		Line 148:

	- Tyler & Luke		- Tyler & Luke


			== Addendum : 02/07/2023 ==
			Our team created a LEMP stack on a vm in order to troubleshoot a webserver issue.

			We used a source from [https://www.digitalocean.com/community/tutorials/how-to-install-linux-nginx-mysql-php-lemp-stack-ubuntu-18-04 Digital Ocean] to follow the entire process with similar prerequisites, but we had an issue with connecting our website page to the internet. The solution was to create a HOST file in our DNS server and tying our domain to a static ip address.

Lchristopherson at 19:24, 30 May 2022

2022-05-30T19:24:51Z

@@ Line 48: / Line 48: @@
 ==Installing PHP==
-Again, installing PHP is very similar to two sections preceding this one. Start off by installing the <code>php-fpm</code> and <code>php-mysql</code> packages by running <code>sudo apt-get install php-fpm php-mysql</code>. After it installs, you'll want to edit <code>php.ini</code> by running <code>sudo vim /etc/php/7.2/fpm/php.ini</code>.
+Again, installing PHP is very similar to two sections preceding this one. Start off by installing the <code>php-fpm</code> and <code>php-mysql</code> packages by running <code>sudo apt-get install php-fpm php-mysql</code>. After it installs, you'll want to edit <code>php.ini</code> by running <code>sudo vim /etc/php/7.4/fpm/php.ini</code>.
+.
@@ Line 60: / Line 60: @@
+.
-Once the file saves, run <code>sudo systemctl restart php7.2-fpm</code> to restart PHP.
+Once the file saves, run <code>sudo systemctl restart php7.4-fpm</code> to restart PHP.
 ==Configuring nginx==
@@ Line 139: / Line 139: @@
 sudo route add default gw x.x.x.1 ens32 (where x.x.x are the network address of our subnet)
 ==Conclusion==
@@ Line 184: / Line 147: @@
 Thank you,
-- Tyler
+- Tyler & Luke

Lchristopherson: Hyperlink STFW to TLA

2022-05-09T19:01:29Z

Hyperlink STFW to TLA

← Older revision		Revision as of 19:01, 9 May 2022
Line 178:		Line 178:

	==Conclusion==		==Conclusion==
	By now, your nginx server should be up and fully operational. As always, if you're having any issues please STFW before you ask people for advice!		By now, your nginx server should be up and fully operational. As always, if you're having any issues please [[Three Letter Acronym (TLA)\|STFW]] before you ask people for advice!

	<br>		<br>

Lchristopherson at 15:35, 31 March 2022

2022-03-31T15:35:42Z

← Older revision		Revision as of 15:35, 31 March 2022
Line 1:		Line 1:
			[[Category:Webserver]]
	==About==		==About==
	Nginx (pronounced engine-x) is web server which can also be used proxy, load balancer, mail proxy and HTTP cache. It's also a modern alternative to something like Apache, IIS, or Caddy.		Nginx (pronounced engine-x) is web server which can also be used proxy, load balancer, mail proxy and HTTP cache. It's also a modern alternative to something like Apache, IIS, or Caddy.

Lchristopherson: /* Subdomains */

2022-01-20T17:50:04Z

Subdomains

← Older revision		Revision as of 17:50, 20 January 2022
Line 147:		Line 147:

	===What needs to be changed===		===What needs to be changed===
	The only important things that need to be changed are the <code>root</code> and <code>server_name</code> variables. Press <code>i</code> to start editing the file in Vim, and then find where the variables are located. Change the <code>root</code> variable to an updated path where the contents for the subdomain can be found. Generally, good practice for this is to create a new folder in the primary domains path with the name of the subdomain. So, if we were trying to create <code>subdomain.example.ms</code>, we'd create a new folder by running the command <code>sudo mkdir /var/www/example.ms/subdomain</code>. Then, we'd modify our <code>root</code> variable to look something like this:<pre>		The only important things that need to be changed are the <code>root</code> and <code>server_name</code> variables. Press <code>i</code> to start editing the file in Vim, and then find where the variables are located. Change the <code>root</code> variable to an updated path where the contents for the subdomain can be found. Generally, good practice for this is to create a new folder in the primary domains path with the name of the subdomain. So, if we were trying to create <code>subdomain.example.ms</code>, we'd create a new folder by running the command <code>sudo mkdir /var/www/example.ms/subdomain</code> '''''OR''''' <code>sudo mkdir /var/www/subdomain.example.ms</code>. Then, we'd modify our <code>root</code> variable to look something like this:<pre>
	# before		# before
	root /var/www/example.ms;		root /var/www/example.ms;

	# after		# after
	root /var/www/example.ms/subdomain;		root /var/www/example.ms/subdomain;<br>root /var/www/subdomain.example.ms;
	</pre>The <code>server_name</code> variable is just as simple. Just add the subdomain prefix to the beginning of your domain:		</pre>The <code>server_name</code> variable is just as simple. Just add the subdomain prefix to the beginning of your domain:
	# before		# before
Line 159:		Line 159:
	# after		# after
	server_name subdomain.example.ms;		server_name subdomain.example.ms;
	Once you've made the proper changes, save and quit the file by pressing <code>escape</code> and typing <code>:wq</code>. Then, run <code>cd ../sites-enabled && sudo ln -s /etc/nginx/sites-available/subdomain.example.ms ./</code> and restart nginx by running <code>sudo systemctl restart nginx</code>.		Once you've made the proper changes, save and quit the file by pressing <code>escape</code> and typing <code>:wq</code>. Then, run <code>cd ../sites-enabled && sudo ln -s /etc/nginx/sites-available/subdomain.example.ms ./</code> and restart nginx by running <code>sudo systemctl restart nginx</code>.<br><br>Make sure to check functionality by typing <code>systemctl status nginx</code>.

			'''NOTE:''' ''If you're not able to connect to the subdomain, make sure that you have chamberlain add an A record in namecheap :\|.''

	==Adding other domains (that aren't subdomains)==		==Adding other domains (that aren't subdomains)==

Lchristopherson: /* Adding HTTPS to a domain with LetsEncrypt (certbot) */

2022-01-20T17:45:11Z

Adding HTTPS to a domain with LetsEncrypt (certbot)

← Older revision		Revision as of 17:45, 20 January 2022
Line 127:		Line 127:
	If everything worked properly, you should see a PHP information page with a bunch of library authors and enabled modules. If it doesn't, research!		If everything worked properly, you should see a PHP information page with a bunch of library authors and enabled modules. If it doesn't, research!

	== Troubleshooting ==		==Troubleshooting==
	Over time we have run into a few quirks with this server that we listed here....		Over time we have run into a few quirks with this server that we listed here....

	=== Resetting the IP address ===		===Resetting the IP address===
	Unfortunately we have found that from time to time on server reboots the server forgets the IP address for the webserver. Here is what you need to do to fix it.		Unfortunately we have found that from time to time on server reboots the server forgets the IP address for the webserver. Here is what you need to do to fix it.

Line 171:		Line 171:

	'''Note:''' '''It could possibly take up to 24-72 hours for it to be enabled, although at the time of writing the changes propagated almost immediately.'''		'''Note:''' '''It could possibly take up to 24-72 hours for it to be enabled, although at the time of writing the changes propagated almost immediately.'''

	'''Extra Note:''' '''All certbot certificates should autorenew every 90 days.'''		'''Extra Note:''' '''All certbot certificates should autorenew every 90 days.'''

Lchristopherson: /* Adding HTTPS to a domain with LetsEncrypt (certbot) */

2022-01-20T17:44:48Z

Adding HTTPS to a domain with LetsEncrypt (certbot)

← Older revision		Revision as of 17:44, 20 January 2022
Line 171:		Line 171:

	'''Note:''' '''It could possibly take up to 24-72 hours for it to be enabled, although at the time of writing the changes propagated almost immediately.'''		'''Note:''' '''It could possibly take up to 24-72 hours for it to be enabled, although at the time of writing the changes propagated almost immediately.'''
			'''Extra Note:''' '''All certbot certificates should autorenew every 90 days.'''

	==Conclusion==		==Conclusion==

Lchristopherson: /* Verifying Functionality */

2022-01-20T17:42:17Z

Verifying Functionality

← Older revision		Revision as of 17:42, 20 January 2022
Line 123:		Line 123:
	</pre>... and then save and quit the file by pressing <code>escape</code> and typing <code>:wq</code>. Now, go to <code><nowiki>http://example.ms/info.php</nowiki></code>. If you didn't configure the nameservers for your domain to point to your new nginx server, then just replace the domain name with the IP of the server (refer to the <code>ifconfig</code> part of the [[Nginx#Installing nginx\|Installing nginx]] section if you don't know how.)		</pre>... and then save and quit the file by pressing <code>escape</code> and typing <code>:wq</code>. Now, go to <code><nowiki>http://example.ms/info.php</nowiki></code>. If you didn't configure the nameservers for your domain to point to your new nginx server, then just replace the domain name with the IP of the server (refer to the <code>ifconfig</code> part of the [[Nginx#Installing nginx\|Installing nginx]] section if you don't know how.)

	.		<br>

	If everything worked properly, you should see a PHP information page with a bunch of library authors and enabled modules. If it doesn't, research!		If everything worked properly, you should see a PHP information page with a bunch of library authors and enabled modules. If it doesn't, research!

Lchristopherson: /* Subdomains */

2022-01-20T17:41:49Z

Subdomains

← Older revision		Revision as of 17:41, 20 January 2022
Line 142:		Line 142:
	Adding subdomains is really easy and doesn't require a lot of effort. You'll just need to remember the general process from the [[Nginx#Configuring nginx\|Configuring nginx]] section.		Adding subdomains is really easy and doesn't require a lot of effort. You'll just need to remember the general process from the [[Nginx#Configuring nginx\|Configuring nginx]] section.

	.		<br>

	To start, navigate to the <code>sites-available</code> directory by running <code>cd /etc/nginx/sites-available</code>. Then, you can either copy a pre-existing configuration by running <code>sudo cp example.ms subdomain.example.ms</code> or creating a new file by running <code>sudo vim subdomain.example.ms</code>. If you copied it, edit the file by running <code>sudo vim subdomain.example.ms</code>.		To start, navigate to the <code>sites-available</code> directory by running <code>cd /etc/nginx/sites-available</code>. Then, you can either copy a pre-existing configuration by running <code>sudo cp example.ms subdomain.example.ms</code> or creating a new file by running <code>sudo vim subdomain.example.ms</code>. If you copied it, edit the file by running <code>sudo vim subdomain.example.ms</code>.