Adding a New Domain or Subdomain - Revision history

Lchristopherson at 17:26, 12 May 2022

2022-05-12T17:26:34Z

← Older revision		Revision as of 17:26, 12 May 2022
Line 33:		Line 33:
	<pre>		<pre>
	server {		server {
	listen 80; ~~<code><span style="color:green">~~# This is the port that Nginx will be listening on~~</span></code>~~		listen 80; # This is the port that Nginx will be listening on
	listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.		listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

Lchristopherson at 17:20, 12 May 2022

2022-05-12T17:20:27Z

← Older revision		Revision as of 17:20, 12 May 2022
Line 33:		Line 33:
	<pre>		<pre>
	server {		server {
	listen 80; <code style="color:green"># This is the port that Nginx will be listening on</code>		listen 80; <code><span style="color:green"># This is the port that Nginx will be listening on</span></code>
	listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.		listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

Lchristopherson at 17:19, 12 May 2022

2022-05-12T17:19:41Z

← Older revision		Revision as of 17:19, 12 May 2022
Line 33:		Line 33:
	<pre>		<pre>
	server {		server {
	listen 80; <~~span~~ style="color:green"># This is the port that Nginx will be listening on</~~span~~>		listen 80; <code style="color:green"># This is the port that Nginx will be listening on</code>
	listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.		listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

Lchristopherson at 17:16, 12 May 2022

2022-05-12T17:16:20Z

← Older revision		Revision as of 17:16, 12 May 2022
Line 31:		Line 31:
	Firstly, navigate to the sites-available directory by running the command <code>cd /etc/nginx/sites-available</code>. This directory holds all of the [[Nginx]] website server blocks. These server blocks are what actually lets the website run on the internet. Once in the ''sites-available'' directory you will have access to view/edit all of the other website server blocks. To create a new server block for your domain, run the command <code>sudo touch ./example.org</code> to create the file, then <code>sudo nano ./example.org</code> to edit the file. Alternatively, you may just run the ladder command to create and edit the file. The server blocks have very specific formatting for everything to run correctly. The following is a basic server block that has been commented to increase understanding.		Firstly, navigate to the sites-available directory by running the command <code>cd /etc/nginx/sites-available</code>. This directory holds all of the [[Nginx]] website server blocks. These server blocks are what actually lets the website run on the internet. Once in the ''sites-available'' directory you will have access to view/edit all of the other website server blocks. To create a new server block for your domain, run the command <code>sudo touch ./example.org</code> to create the file, then <code>sudo nano ./example.org</code> to edit the file. Alternatively, you may just run the ladder command to create and edit the file. The server blocks have very specific formatting for everything to run correctly. The following is a basic server block that has been commented to increase understanding.

	<~~nowiki~~>		<pre>
	server {		server {
	listen 80; <style="color:green"># This is the port that Nginx will be listening on		listen 80; <span style="color:green"># This is the port that Nginx will be listening on</span>
	listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.		listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

Line 70:		Line 70:
	}		}
	}		}
	</~~nowiki~~>		</pre>

	==== Enabling the Server Block ====		==== Enabling the Server Block ====

Lchristopherson at 17:14, 12 May 2022

2022-05-12T17:14:06Z

← Older revision		Revision as of 17:14, 12 May 2022
Line 31:		Line 31:
	Firstly, navigate to the sites-available directory by running the command <code>cd /etc/nginx/sites-available</code>. This directory holds all of the [[Nginx]] website server blocks. These server blocks are what actually lets the website run on the internet. Once in the ''sites-available'' directory you will have access to view/edit all of the other website server blocks. To create a new server block for your domain, run the command <code>sudo touch ./example.org</code> to create the file, then <code>sudo nano ./example.org</code> to edit the file. Alternatively, you may just run the ladder command to create and edit the file. The server blocks have very specific formatting for everything to run correctly. The following is a basic server block that has been commented to increase understanding.		Firstly, navigate to the sites-available directory by running the command <code>cd /etc/nginx/sites-available</code>. This directory holds all of the [[Nginx]] website server blocks. These server blocks are what actually lets the website run on the internet. Once in the ''sites-available'' directory you will have access to view/edit all of the other website server blocks. To create a new server block for your domain, run the command <code>sudo touch ./example.org</code> to create the file, then <code>sudo nano ./example.org</code> to edit the file. Alternatively, you may just run the ladder command to create and edit the file. The server blocks have very specific formatting for everything to run correctly. The following is a basic server block that has been commented to increase understanding.

	<~~pre~~>		<nowiki>
	server {		server {
	listen 80;<~~/pre> <pre~~ style="color:green"># This is the port that Nginx will be listening on~~</pre><pre>~~		listen 80; <style="color:green"># This is the port that Nginx will be listening on
	listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.		listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

Line 70:		Line 70:
	}		}
	}		}
	</~~pre~~>		</nowiki>

	==== Enabling the Server Block ====		==== Enabling the Server Block ====

Lchristopherson at 17:12, 12 May 2022

2022-05-12T17:12:40Z

← Older revision		Revision as of 17:12, 12 May 2022
Line 33:		Line 33:
	<pre>		<pre>
	server {		server {
	listen 80; <pre style="color:green"># This is the port that Nginx will be listening on</pre>		listen 80;</pre> <pre style="color:green"># This is the port that Nginx will be listening on</pre><pre>
	listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.		listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

Lchristopherson at 17:12, 12 May 2022

2022-05-12T17:12:06Z

← Older revision		Revision as of 17:12, 12 May 2022
Line 33:		Line 33:
	<pre>		<pre>
	server {		server {
	listen 80; # This is the port that Nginx will be listening on		listen 80; <pre style="color:green"># This is the port that Nginx will be listening on</pre>
	listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.		listen [::]:80; # ex. 80 = HTTP, while 443 = HTTPS. We will never use 443.

Lchristopherson at 17:09, 12 May 2022

2022-05-12T17:09:38Z

← Older revision		Revision as of 17:09, 12 May 2022
Line 16:		Line 16:
	==== Configuring the Domain ====		==== Configuring the Domain ====
	[[File:Namecheap 2.png\|thumb\|365x365px]]		[[File:Namecheap 2.png\|thumb\|365x365px]]
	Before beginning any work on the webserver we need to make sure that the domain is ready to be used ~~in unison with~~ the ~~webserver~~. This will most likely be done by [[Bradley Chamberlain]], but there is a chance that you will sometime have to do this or he will forget how to do it, that is why I am documenting the procedure anyways.		Before beginning any work on the webserver we need to make sure that the domain is ready to be used, you need to add the A record for it. This will most likely be done by [[Bradley Chamberlain]], but there is a chance that you will sometime have to do this or he will forget how to do it, that is why I am documenting the procedure anyways.

	To start, you will log into [https://www.namecheap.com/ Namecheap] with the account that owns the domain. Once logged in you will see all of the domains that you own listed. Select "''Manage''" on the domain that you will be using. It will take you to this screen, select "''Advanced DNS''".		To start, you will log into [https://www.namecheap.com/ Namecheap] with the account that owns the domain. Once logged in you will see all of the domains that you own listed. Select "''Manage''" on the domain that you will be using. It will take you to this screen, select "''Advanced DNS''".

Lchristopherson at 16:58, 12 May 2022

2022-05-12T16:58:05Z

@@ Line 84: / Line 84: @@
       phpinfo();
 ?>
-</pre>
+</pre>Save and Exit the file by using "''Ctrl + O''", and "''Ctrl + X''". Now navigate to the website in the web browser by using the link: example.org/info.php. This will display all of the sensitive information regarding our webserver, make sure that once you see the page pop up, immediately delete the file from the webserver by running, <code>sudo rm ./info.php</code>.
 == New Sub-Domain in Nginx ==

Lchristopherson at 16:38, 12 May 2022

2022-05-12T16:38:34Z

← Older revision		Revision as of 16:38, 12 May 2022
Line 79:		Line 79:
	==== Testing Working Configuration ====		==== Testing Working Configuration ====
	To check that your sever block is fully functional, you need to create an actual page for the website to run. First, navigate to the websites root directory by running <code>cd /var/www/example.org</code>. This is where all of the files that the website runs on are located. Run the command <code>sudo nano ./info.php</code>to create and edit the information file. Once in the file, paste this code:		To check that your sever block is fully functional, you need to create an actual page for the website to run. First, navigate to the websites root directory by running <code>cd /var/www/example.org</code>. This is where all of the files that the website runs on are located. Run the command <code>sudo nano ./info.php</code>to create and edit the information file. Once in the file, paste this code:

			<pre>
			<?php
			phpinfo();
			?>
			</pre>

	== New Sub-Domain in Nginx ==		== New Sub-Domain in Nginx ==