Updating the Webserver - Revision history

Lchristopherson at 15:19, 21 April 2022

2022-04-21T15:19:05Z

← Older revision		Revision as of 15:19, 21 April 2022
Line 2:		Line 2:

	== About ==		== About ==
	Our Nginx web server runs on Ubuntu 20.04 [[Three Letter Acronym (TLA)\|LTS]] as of now. Most of this documentation was written during the update from 18.04 [[Three Letter Acronym (TLA)\|LTS]] to 20.04 [[Three Letter Acronym (TLA)\|LTS]], so take everything from this page with a grain of salt, as things in your upgrade may differ. A lot of this is written as a project plan, which may in turn help you create a project plan for yourself.		Our [[Nginx]] web server runs on Ubuntu 20.04 [[Three Letter Acronym (TLA)\|LTS]] as of now. Most of this documentation was written during the update from 18.04 [[Three Letter Acronym (TLA)\|LTS]] to 20.04 [[Three Letter Acronym (TLA)\|LTS]], so take everything from this page with a grain of salt, as things in your upgrade may differ. A lot of this is written as a project plan, which may in turn help you create a project plan for yourself.

	== Links ==		== Links ==
Line 17:		Line 17:
	# Update MySQL		# Update MySQL
	# Update Wordpress		# Update Wordpress
	# Update Nginx		# Update [[Nginx]]
	# Update Hesk		# Update Hesk
	# Review Certbot Certificates		# Review Certbot Certificates
Line 38:		Line 38:
	** Run the command <code>sudo do-release-upgrade -d</code> – ''‘sudo’'' meaning to run command as admin/root, ''‘do-release-upgrade’'' checks for update and if one is available will start running it, ''‘-d’'' meaning “devel-release” or the latest [[Three Letter Acronym (TLA)\|LTS]]/Development Release. You will be asked a series of Y/N questions to configure the upgrade. Once all of this is completed, Ubuntu is finished upgrading.		** Run the command <code>sudo do-release-upgrade -d</code> – ''‘sudo’'' meaning to run command as admin/root, ''‘do-release-upgrade’'' checks for update and if one is available will start running it, ''‘-d’'' meaning “devel-release” or the latest [[Three Letter Acronym (TLA)\|LTS]]/Development Release. You will be asked a series of Y/N questions to configure the upgrade. Once all of this is completed, Ubuntu is finished upgrading.

	* After Ubuntu is finished updating, check IP, websites, and ~~nginx~~ config files for discrepancies.		* After Ubuntu is finished updating, check IP, websites, and [[Nginx]] config files for discrepancies.
	* Uninstall parsoid before update and reinstall once you are updated, don't replace any files with new ones.		* Uninstall parsoid before update and reinstall once you are updated, don't replace any files with new ones.

	==== Nginx ====		==== Nginx ====
	* To begin you need to verify that Nginx is actually in need of an update by running, ~~“nginx~~ -v” – ‘nginx’ meaning an nginx command, and ‘-v’ meaning check the version. It should be something like 1.18.x IMPORTANT: MARK DOWN YOUR CURRENT VERSION… X.XX.X		* To begin you need to verify that [[Nginx]] is actually in need of an update by running, <code>nginx -v</code> – ''‘nginx’'' meaning an nginx command, and ''‘-v’'' meaning check the version. It should be something like 1.18.x IMPORTANT: MARK DOWN YOUR CURRENT VERSION… X.XX.X
	* If an upgrade is necessary then you will run the command ~~“sudo~~ cp /etc/nginx/nginx.conf /etc/nginx/nginx.conf.X.XX.X.~~backup”~~ – ‘sudo’ meaning to run the command as admin/root, ‘cp’ being the command to copy file1 to a new file2 location, ‘/etc/nginx/nginx.~~conf’~~ is a reference to ~~Nginx’s~~ configuration file, ‘/etc/nginx/nginx.conf.X.XX.X.~~backup’~~ is the backup files name and location.		* If an upgrade is necessary then you will run the command <code>sudo cp /etc/nginx/nginx.conf /etc/nginx/nginx.conf.X.XX.X.backup</code> – ''‘sudo’'' meaning to run the command as admin/root, ''‘cp’'' being the command to copy file1 to a new file2 location, <code>/etc/nginx/nginx.conf</code> is a reference to [[Nginx\|Nginx's]] configuration file, <code>/etc/nginx/nginx.conf.X.XX.X.backup</code> is the backup files name and location.
	* Next you will install the needed dependencies using, ~~“sudo~~ apt-get install software-properties-common python-software-~~properties”~~. Afterward you will add the ~~nginx~~ repository to the machine using ~~“sudo~~ add-apt-repository ppa:nginx/~~stable”~~		* Next you will install the needed dependencies using, <code>sudo apt-get install software-properties-common python-software-properties</code>. Afterward you will add the [[Nginx]] repository to the machine using <code>sudo add-apt-repository ppa:nginx/stable</code>
	* Next update all repositories, ~~“sudo~~ apt-get ~~update”~~		* Next update all repositories, <code>sudo apt-get update</code>
	* Finally install ~~nginx~~ again using ~~“sudo~~ apt-get install ~~nginx”~~ – THIS WILL UPDATE IT AS WELL AS INSTALL IT FRESH… It will ask if you want to keep your old config, select N / no. To complete the install verify the Nginx version using ~~“nginx~~ -v”.		* Finally install [[Nginx]] again using <code>sudo apt-get install nginx</code> – THIS WILL UPDATE IT AS WELL AS INSTALL IT FRESH… It will ask if you want to keep your old config, select Y / yes. To complete the install verify the [[Nginx]] version using <code>nginx -v</code>.
	* Once Nginx completes installing, run ~~“sudo~~ systemctl restart ~~nginx”~~. Check all ~~nginx~~ config files and websites.		* Once [[Nginx]] completes installing, run <code>sudo systemctl restart nginx</code>. Check all [[Nginx]] config files and websites for discrepancies.

	==== MariaDB ====		==== MariaDB ====
	* MARIADB IS USING THE LATEST STABLE VERSION SKIP TO NEXT STEP!		* MARIADB IS USING THE LATEST STABLE VERSION SKIP TO NEXT STEP!
			*Once this update is discovered, add to this wiki...

	==== PHP ====		==== PHP ====
	* Add the PHP repositories to the web server, ~~“sudo~~ apt install software-properties-~~common”~~ followed by ~~“sudo~~ add-apt-repository ppa:ondrej/~~php”~~		* Add the PHP repositories to the web server, <code>sudo apt install software-properties-common</code> followed by <code>sudo add-apt-repository ppa:ondrej/php</code>
	* Update the system packages, ~~“sudo~~ apt-get ~~update”~~		* Update the system packages, <code>sudo apt-get update</code>
	* Install PHP 7.4, ~~“sudo~~ apt install php7.4”. Check the PHP version ~~“sudo~~ php -v”. Install extensions, ~~“sudo~~ apt install php7.4-common php7.4-mysql php7.4-~~fpm”~~ After you install edit, “/etc/php/7.4/fpm/php.~~ini”~~ Find ‘cgi.fix_pathinfo’ ~~and~~ uncomment it and make it equal to 0.		* Install PHP 7.4, <code>sudo apt install php7.4</code>. Check the PHP version <code>sudo php -v</code>. Install extensions, <code>sudo apt install php7.4-common php7.4-mysql php7.4-fpm</code> After you install edit, <code>/etc/php/7.4/fpm/php.ini</code> Find ''‘cgi.fix_pathinfo’,'' uncomment it and make it equal to 0.
	* Run, ~~“sudo~~ systemctl stop php7.2-~~fpm”~~, ~~“sudo~~ systemctl disable php7.2-~~fpm”~~, ~~“sudo~~ systemctl start php7.4-~~fpm”~~, ~~“sudo~~ systemctl enable php7.4-~~fpm”~~ in that order.		* Run, <code>sudo systemctl stop php7.2-fpm</code>, <code>sudo systemctl disable php7.2-fpm</code>, <code>sudo systemctl start php7.4-fpm</code>, <code>sudo systemctl enable php7.4-fpm</code> in that order.
	* Verify PHP by ~~running~~ <?php phpinfo() ?>		* Verify PHP by making a website with the content <?php phpinfo() ?>
	* Check all Websites for functionality.		* Check all Websites for functionality.
	* PS: CHANGE SERVER BLOCK CONFIG TO BE NEW PHP VERSION		* PS: CHANGE SERVER BLOCK CONFIG TO BE NEW PHP VERSION
			**<code>sudo nano /etc/nginx/sites-available/24pin.tech</code> look for the <code>location ~ \.php${</code>line, and change the content from the old version to the new version. ex. x.x->x.y

	==== HESK ====		==== HESK ====
	* BEFORE CONTINUING RUN ANOTHER BACKUP!!!		* '''BEFORE CONTINUING RUN ANOTHER BACKUP!!!'''
	* PuTTY into the web-server and place in the latest ~~hesk~~ install		* [[PuTTY]] into the web-server and place in the latest [[Hesk/Help Desk\|HESK]] install
	* Extract the files and move them into the current HESK directory with the exception of, “hesk_settings.inc.php, head.txt, header.txt, footer.txt” replacing all of the old files.		* Extract the files and move them into the current HESK directory with the exception of, “hesk_settings.inc.php, head.txt, header.txt, footer.txt” replacing all of the old files.
	* Navigate to service.24pin.tech/install, and select Update HESK. Once this is completed delete the install folder from the server.		* Navigate to service.24pin.tech/install, and select Update HESK. Once this is completed delete the install folder from the server.

Lchristopherson at 20:56, 20 April 2022

2022-04-20T20:56:24Z

← Older revision		Revision as of 20:56, 20 April 2022
Line 36:		Line 36:

	* Updating Ubuntu is a fairly easy process and shouldn’t take too much time '''--'''''LOL, I WAS SO WRONG, GL BUDDY'''''--'''. To start we will make sure that we are cross-referencing information from Ubuntu's guide for the command line.		* Updating Ubuntu is a fairly easy process and shouldn’t take too much time '''--'''''LOL, I WAS SO WRONG, GL BUDDY'''''--'''. To start we will make sure that we are cross-referencing information from Ubuntu's guide for the command line.
	** Run the command <code>sudo do-release-upgrade -d</code> – ‘sudo’ meaning to run command as admin/root, ‘do-release-upgrade’ checks for update and if one is available will start running it, ‘-d’ meaning “devel-release” or the latest LTS/Development Release. You will be asked a series of Y/N questions to configure the upgrade. Once all of this is completed, Ubuntu is finished upgrading.		** Run the command <code>sudo do-release-upgrade -d</code> – ''‘sudo’'' meaning to run command as admin/root, ''‘do-release-upgrade’'' checks for update and if one is available will start running it, ''‘-d’'' meaning “devel-release” or the latest [[Three Letter Acronym (TLA)\|LTS]]/Development Release. You will be asked a series of Y/N questions to configure the upgrade. Once all of this is completed, Ubuntu is finished upgrading.

	* After Ubuntu is finished updating, check IP, websites, and nginx config files for discrepancies.		* After Ubuntu is finished updating, check IP, websites, and nginx config files for discrepancies.

Lchristopherson at 20:43, 20 April 2022

2022-04-20T20:43:26Z

← Older revision		Revision as of 20:43, 20 April 2022
Line 36:		Line 36:

	* Updating Ubuntu is a fairly easy process and shouldn’t take too much time '''--'''''LOL, I WAS SO WRONG, GL BUDDY'''''--'''. To start we will make sure that we are cross-referencing information from Ubuntu's guide for the command line.		* Updating Ubuntu is a fairly easy process and shouldn’t take too much time '''--'''''LOL, I WAS SO WRONG, GL BUDDY'''''--'''. To start we will make sure that we are cross-referencing information from Ubuntu's guide for the command line.
	** Run the command ~~“sudo~~ do-release-upgrade -d” – ‘sudo’ meaning to run command as admin/root, ‘do-release-upgrade’ checks for update and if one is available will start running it, ‘-d’ meaning “devel-release” or the latest LTS/Development Release. You will be asked a series of Y/N questions to configure the upgrade. Once all of this is completed, Ubuntu is finished upgrading.		** Run the command <code>sudo do-release-upgrade -d</code> – ‘sudo’ meaning to run command as admin/root, ‘do-release-upgrade’ checks for update and if one is available will start running it, ‘-d’ meaning “devel-release” or the latest LTS/Development Release. You will be asked a series of Y/N questions to configure the upgrade. Once all of this is completed, Ubuntu is finished upgrading.

	* After Ubuntu is finished updating, check IP, websites, and nginx config files for discrepancies.		* After Ubuntu is finished updating, check IP, websites, and nginx config files for discrepancies.

Lchristopherson: formatting

2022-04-20T20:42:48Z

formatting

← Older revision		Revision as of 20:42, 20 April 2022
Line 25:		Line 25:

	== Updating Process ==		== Updating Process ==
	<div style="text-align:center;">'''FIRST email evit.computer and maricopaeducationfoundation.com about the pending shutdown.'''		<div style="text-align:center;">'''FIRST email evit.computer and maricopaeducationfoundation.com about the pending shutdown.'''<br>
	<br>
	'''SQL DATABASES WILL BE BACKED UP WITH OLD VERSION OF THE SERVER.'''</div>		'''SQL DATABASES WILL BE BACKED UP WITH OLD VERSION OF THE SERVER.'''</div>

	=== Backup Server ===		=== Backup Server ===
			The server backup and restore points have been proven to work by the crash on 1/31/22. These are functional and need no more work on the Web-Masters end. Before beginning any updates we will take the working machine point and back it up '''--'''''Take a snapshot'''''--'''. We will put a stasis on work done on the 24PinTech websites and notify our external admins, “evit” and “MEF” that all changes made could possibly be lost. Work orders will be put on hold temporarily and we will stop accepting them until all updates are completed. Once these conditions are met, we can begin work on the server.

	* The server backup and restore points have been proven to work by the crash on 1/31/22. These are functional and need no more work on my end. Before beginning any updates we will take the working machine point and back it up. We will put a stasis on work done on the 24PinTech websites and notify our external admins, “evit” and “MEF” that all changes made will be lost. Work orders will be put on hold temporarily and we will stop accepting them until all updates are completed. Once these conditions are met, we can begin work on the server.		=== Updating/Verifying Functional Updates ===

	# Updating/~~Verifying Functional Updates~~		==== Ubuntu ====
	## Ubuntu
			* Updating Ubuntu is a fairly easy process and shouldn’t take too much time '''--'''''LOL, I WAS SO WRONG, GL BUDDY'''''--'''. To start we will make sure that we are cross-referencing information from Ubuntu's guide for the command line.
			** Run the command “sudo do-release-upgrade -d” – ‘sudo’ meaning to run command as admin/root, ‘do-release-upgrade’ checks for update and if one is available will start running it, ‘-d’ meaning “devel-release” or the latest LTS/Development Release. You will be asked a series of Y/N questions to configure the upgrade. Once all of this is completed, Ubuntu is finished upgrading.

	* Updating Ubuntu is a fairly easy process and shouldn’t take too much time. To start we will make sure that we are cross-referencing information from Ubuntu's guide for the command line. To start you will run the command “sudo do-release-upgrade -d” – ‘sudo’ meaning to run command as admin/root, ‘do-release-upgrade’ checks for update and if one is available will start running it, ‘-d’ meaning “devel-release” or the latest LTS/Development Release. You will be asked a series of Y/N questions to configure the upgrade. Once all of this is completed, Ubuntu is finished upgrading.
	* After Ubuntu is finished updating, check IP, websites, and nginx config files for discrepancies.		* After Ubuntu is finished updating, check IP, websites, and nginx config files for discrepancies.
	* Uninstall parsoid before update and reinstall once you are updated, don't replace any files with new ones.		* Uninstall parsoid before update and reinstall once you are updated, don't replace any files with new ones.

	# Nginx		==== Nginx ====

	* To begin you need to verify that Nginx is actually in need of an update by running, “nginx -v” – ‘nginx’ meaning an nginx command, and ‘-v’ meaning check the version. It should be something like 1.18.x IMPORTANT: MARK DOWN YOUR CURRENT VERSION… X.XX.X		* To begin you need to verify that Nginx is actually in need of an update by running, “nginx -v” – ‘nginx’ meaning an nginx command, and ‘-v’ meaning check the version. It should be something like 1.18.x IMPORTANT: MARK DOWN YOUR CURRENT VERSION… X.XX.X
	* If an upgrade is necessary then you will run the command “sudo cp /etc/nginx/nginx.conf /etc/nginx/nginx.conf.X.XX.X.backup” – ‘sudo’ meaning to run the command as admin/root, ‘cp’ being the command to copy file1 to a new file2 location, ‘/etc/nginx/nginx.conf’ is a reference to Nginx’s configuration file, ‘/etc/nginx/nginx.conf.X.XX.X.backup’ is the backup files name and location.		* If an upgrade is necessary then you will run the command “sudo cp /etc/nginx/nginx.conf /etc/nginx/nginx.conf.X.XX.X.backup” – ‘sudo’ meaning to run the command as admin/root, ‘cp’ being the command to copy file1 to a new file2 location, ‘/etc/nginx/nginx.conf’ is a reference to Nginx’s configuration file, ‘/etc/nginx/nginx.conf.X.XX.X.backup’ is the backup files name and location.
Line 49:		Line 49:
	* Once Nginx completes installing, run “sudo systemctl restart nginx”. Check all nginx config files and websites.		* Once Nginx completes installing, run “sudo systemctl restart nginx”. Check all nginx config files and websites.

	# MariaDB		==== MariaDB ====

	* MARIADB IS USING THE LATEST STABLE VERSION SKIP TO NEXT STEP!		* MARIADB IS USING THE LATEST STABLE VERSION SKIP TO NEXT STEP!

	# PHP		==== PHP ====

	* Add the PHP repositories to the web server, “sudo apt install software-properties-common” followed by “sudo add-apt-repository ppa:ondrej/php”		* Add the PHP repositories to the web server, “sudo apt install software-properties-common” followed by “sudo add-apt-repository ppa:ondrej/php”
	* Update the system packages, “sudo apt-get update”		* Update the system packages, “sudo apt-get update”
Line 63:		Line 61:
	* PS: CHANGE SERVER BLOCK CONFIG TO BE NEW PHP VERSION		* PS: CHANGE SERVER BLOCK CONFIG TO BE NEW PHP VERSION

	# HESK		==== HESK ====

	* BEFORE CONTINUING RUN ANOTHER BACKUP!!!		* BEFORE CONTINUING RUN ANOTHER BACKUP!!!
	* PuTTY into the web-server and place in the latest hesk install		* PuTTY into the web-server and place in the latest hesk install
Line 73:		Line 70:
	* Submit a ticket and verify functionality.		* Submit a ticket and verify functionality.

	# Wordpress		==== Wordpress ====

	* Navigate to all wordpress websites with admin and select Update to version 5.9		* Navigate to all wordpress websites with admin and select Update to version 5.9
	* Let the install complete and check all pages and media for discrepancies.		* Let the install complete and check all pages and media for discrepancies.

	# Review Certbot Certificates		=== Review Certbot Certificates ===

	* Run “sudo certbot certificates” to view all certificates.		* Run “sudo certbot certificates” to view all certificates.
	* Delete unused certificates by running “sudo certbot delete <ID>”		* Delete unused certificates by running “sudo certbot delete <ID>”
Line 85:		Line 80:
	* Navigate to all websites and check for HTTPS.		* Navigate to all websites and check for HTTPS.

	# Backup MySQL		=== Backup MySQL ===
			This step has yet to be completed, maybe '''<u>''you''</u>''' can do this one!
	* Have to work with Nate to determine the best way to do this.

Lchristopherson: format -- One line break

2022-04-20T20:29:57Z

format -- One line break

← Older revision		Revision as of 20:29, 20 April 2022
Line 26:		Line 26:
	== Updating Process ==		== Updating Process ==
	<div style="text-align:center;">'''FIRST email evit.computer and maricopaeducationfoundation.com about the pending shutdown.'''		<div style="text-align:center;">'''FIRST email evit.computer and maricopaeducationfoundation.com about the pending shutdown.'''
	~~<br>~~<br>		<br>
	'''SQL DATABASES WILL BE BACKED UP WITH OLD VERSION OF THE SERVER.'''</div>		'''SQL DATABASES WILL BE BACKED UP WITH OLD VERSION OF THE SERVER.'''</div>

Lchristopherson: format -- Split lines

2022-04-20T20:29:29Z

format -- Split lines

← Older revision		Revision as of 20:29, 20 April 2022
Line 26:		Line 26:
	== Updating Process ==		== Updating Process ==
	<div style="text-align:center;">'''FIRST email evit.computer and maricopaeducationfoundation.com about the pending shutdown.'''		<div style="text-align:center;">'''FIRST email evit.computer and maricopaeducationfoundation.com about the pending shutdown.'''
			<br><br>
	'''SQL DATABASES WILL BE BACKED UP WITH OLD VERSION OF THE SERVER.'''</div>		'''SQL DATABASES WILL BE BACKED UP WITH OLD VERSION OF THE SERVER.'''</div>

Lchristopherson: format -- Align text to center

2022-04-20T20:28:07Z

format -- Align text to center

← Older revision		Revision as of 20:28, 20 April 2022
Line 25:		Line 25:

	== Updating Process ==		== Updating Process ==
	'''FIRST email evit.computer and maricopaeducationfoundation.com about the pending shutdown.'''		<div style="text-align:center;">'''FIRST email evit.computer and maricopaeducationfoundation.com about the pending shutdown.'''

	'''SQL DATABASES WILL BE BACKED UP WITH OLD VERSION OF THE SERVER.'''		'''SQL DATABASES WILL BE BACKED UP WITH OLD VERSION OF THE SERVER.'''</div>

	=== Backup Server ===		=== Backup Server ===

Lchristopherson: Framework of wiki entry

2022-04-20T20:26:14Z

Framework of wiki entry

← Older revision		Revision as of 20:26, 20 April 2022
Line 1:		Line 1:
	[[Category:Webserver]]		[[Category:Webserver]]

			== About ==
			Our Nginx web server runs on Ubuntu 20.04 [[Three Letter Acronym (TLA)\|LTS]] as of now. Most of this documentation was written during the update from 18.04 [[Three Letter Acronym (TLA)\|LTS]] to 20.04 [[Three Letter Acronym (TLA)\|LTS]], so take everything from this page with a grain of salt, as things in your upgrade may differ. A lot of this is written as a project plan, which may in turn help you create a project plan for yourself.

			== Links ==

			* [https://ubuntu.com/blog/how-to-upgrade-from-ubuntu-18-04-lts-to-20-04-lts-today Ubuntu's updating guide]
			* [https://medium.com/@soban1193/upgrading-nginx-to-the-latest-version-on-ubuntu-c0ad9116cf87 Nginx updating guide]

			== Web Server Plans ==

			# Backup the entire server and be sure that the restore points work.
			#* During my update, we had created a new VM in [[VSphere/vCenter\|VSphere]] to push our backups to, in case anything in the updating process had failed, this is not necessary anymore since the discovery of [https://wiki.24pin.tech/VSphere/vCenter#VM_Snapshots VM snapshots]. View documentation on [https://wiki.24pin.tech/VSphere/vCenter#VM_Snapshots snapshots] to learn more.
			# Update Ubuntu
			# Update PHP
			# Update MySQL
			# Update Wordpress
			# Update Nginx
			# Update Hesk
			# Review Certbot Certificates
			# Change 24pintech Wordpress Account Password on all Websites to be advanced PinTech Password.
			# Email evit.computer and maricopaeducationfoundation.com about the pending shutdown.
			# Backup MySQL Databases

			== Updating Process ==
			'''FIRST email evit.computer and maricopaeducationfoundation.com about the pending shutdown.'''

			'''SQL DATABASES WILL BE BACKED UP WITH OLD VERSION OF THE SERVER.'''

			=== Backup Server ===

			* The server backup and restore points have been proven to work by the crash on 1/31/22. These are functional and need no more work on my end. Before beginning any updates we will take the working machine point and back it up. We will put a stasis on work done on the 24PinTech websites and notify our external admins, “evit” and “MEF” that all changes made will be lost. Work orders will be put on hold temporarily and we will stop accepting them until all updates are completed. Once these conditions are met, we can begin work on the server.

			# Updating/Verifying Functional Updates
			## Ubuntu

			* Updating Ubuntu is a fairly easy process and shouldn’t take too much time. To start we will make sure that we are cross-referencing information from Ubuntu's guide for the command line. To start you will run the command “sudo do-release-upgrade -d” – ‘sudo’ meaning to run command as admin/root, ‘do-release-upgrade’ checks for update and if one is available will start running it, ‘-d’ meaning “devel-release” or the latest LTS/Development Release. You will be asked a series of Y/N questions to configure the upgrade. Once all of this is completed, Ubuntu is finished upgrading.
			* After Ubuntu is finished updating, check IP, websites, and nginx config files for discrepancies.
			* Uninstall parsoid before update and reinstall once you are updated, don't replace any files with new ones.

			# Nginx

			* To begin you need to verify that Nginx is actually in need of an update by running, “nginx -v” – ‘nginx’ meaning an nginx command, and ‘-v’ meaning check the version. It should be something like 1.18.x IMPORTANT: MARK DOWN YOUR CURRENT VERSION… X.XX.X
			* If an upgrade is necessary then you will run the command “sudo cp /etc/nginx/nginx.conf /etc/nginx/nginx.conf.X.XX.X.backup” – ‘sudo’ meaning to run the command as admin/root, ‘cp’ being the command to copy file1 to a new file2 location, ‘/etc/nginx/nginx.conf’ is a reference to Nginx’s configuration file, ‘/etc/nginx/nginx.conf.X.XX.X.backup’ is the backup files name and location.
			* Next you will install the needed dependencies using, “sudo apt-get install software-properties-common python-software-properties”. Afterward you will add the nginx repository to the machine using “sudo add-apt-repository ppa:nginx/stable”
			* Next update all repositories, “sudo apt-get update”
			* Finally install nginx again using “sudo apt-get install nginx” – THIS WILL UPDATE IT AS WELL AS INSTALL IT FRESH… It will ask if you want to keep your old config, select N / no. To complete the install verify the Nginx version using “nginx -v”.
			* Once Nginx completes installing, run “sudo systemctl restart nginx”. Check all nginx config files and websites.

			# MariaDB

			* MARIADB IS USING THE LATEST STABLE VERSION SKIP TO NEXT STEP!

			# PHP

			* Add the PHP repositories to the web server, “sudo apt install software-properties-common” followed by “sudo add-apt-repository ppa:ondrej/php”
			* Update the system packages, “sudo apt-get update”
			* Install PHP 7.4, “sudo apt install php7.4”. Check the PHP version “sudo php -v”. Install extensions, “sudo apt install php7.4-common php7.4-mysql php7.4-fpm” After you install edit, “/etc/php/7.4/fpm/php.ini” Find ‘cgi.fix_pathinfo’ and uncomment it and make it equal to 0.
			* Run, “sudo systemctl stop php7.2-fpm”, “sudo systemctl disable php7.2-fpm”, “sudo systemctl start php7.4-fpm”, “sudo systemctl enable php7.4-fpm” in that order.
			* Verify PHP by running <?php phpinfo() ?>
			* Check all Websites for functionality.
			* PS: CHANGE SERVER BLOCK CONFIG TO BE NEW PHP VERSION

			# HESK

			* BEFORE CONTINUING RUN ANOTHER BACKUP!!!
			* PuTTY into the web-server and place in the latest hesk install
			* Extract the files and move them into the current HESK directory with the exception of, “hesk_settings.inc.php, head.txt, header.txt, footer.txt” replacing all of the old files.
			* Navigate to service.24pin.tech/install, and select Update HESK. Once this is completed delete the install folder from the server.
			* Go to service.24pin.tech/admin and log in with the administrator account. If this does not work, reset the password.
			* Check Help desk title, and custom field settings to make sure they display correctly.
			* Submit a ticket and verify functionality.

			# Wordpress

			* Navigate to all wordpress websites with admin and select Update to version 5.9
			* Let the install complete and check all pages and media for discrepancies.

			# Review Certbot Certificates

			* Run “sudo certbot certificates” to view all certificates.
			* Delete unused certificates by running “sudo certbot delete <ID>”
			* Run “sudo certbot certificates” again and verify changes.
			* Navigate to all websites and check for HTTPS.

			# Backup MySQL

			* Have to work with Nate to determine the best way to do this.

Lchristopherson: Created page with "Category:Webserver"

2022-04-12T15:10:28Z

Created page with "Category:Webserver"

New page

[[Category:Webserver]]