Upgrading WordPress Core Manually

  1. First create a full backup of your website. This is very important in case you make a mistake.
  2. Download the newest WordPress ZIP file from wordpress.org.
  3. Unzip the file into a directory on your local machine or in a separate directory on your website.
  4. Deactivate all of the plugins on your WordPress site.
  5. Go to your website root directory and delete your ‘wp-includes’ and ‘wp-admin’ directories. You can do this via sFTP or via SSH.
  6. Upload (or copy over) the new wp-includes and wp-admin directories from the new version of WordPress you unzipped to your website root directory to replace the directories you just deleted.
  7. Don’t delete your wp-content directory or any of the files in that directory. Copy over the files from the wp-content directory in the new version of WordPress to your existing wp-content directory. You will overwrite any existing files with the same name. All of your other files in wp-content will remain in place.
  8. Copy all files from the root (‘/’) directory of the new version of WordPress that you unzipped into your website root directory (or the root directory of your WordPress installation). You will overwrite any existing files and new files will also be copied across. Your wp-config.php file will not be affected because WordPress is never distributed with a wp-config.php file.
  9. Examine the wp-config-sample.php which is distributed with WordPress to see if any new settings have been added that you may want to use or modify.
  10. If you are upgrading manually after a failed auto-update, remove the .maintenance file from your WordPress root directory. This will remove the ‘failed update’ message from your site.
  11. Visit your main WordPress admin page at /wp-admin/ where you may be asked to sign-in again. You may also have to upgrade your database and will be prompted if this is needed. If you can’t sign-in, try clearing your cookies.
  12. Re-enable your plugins which you disabled earlier.
  13. Clear your browser cache to ensure you can see all changes. If you are using a front-end cache like ‘varnish’ you should also clear that to ensure that your customers can see the newest changes on your site.
    Your upgrade is now complete and you should be running the newest version of WordPress.

Ref: https://www.wordfence.com/learn/how-to-manually-upgrade-wordpress-themes-and-plugins/

Share

Install Netxtcloud on Debian 10

Install Apache, MariaDB and PHP

NextCloud runs on the webserver, written in PHP and uses MariaDB to store their data. So you will need to install Apache, MariaDB, PHP and other required packages on your system. You can install all of them by running the following command:

apt-get install apache2 libapache2-mod-php mariadb-server php-xml php-cli php-cgi php-mysql php-mbstring php-gd php-curl php-zip wget unzip -y

Once all the packages are installed, open the php.ini file and tweak some recommended settings:

nano /etc/php/7.3/apache2/php.ini

Change the following settings:

memory_limit = 512M
upload_max_filesize = 1024M
post_max_size = 1024M
max_execution_time = 300
date.timezone = Asia/Dhaka

Save and close the file when you are finished. Then, start the Apache and MariaDB service and enable them to start after system reboot with the following command: Continue reading “Install Netxtcloud on Debian 10” »

Share

Install a Sectigo Domain Validation SSL certificate in Zimbra

We usually get the below four files from Sectigo in the certificate bundle. The file name may vary depending on the certificate type

  1. yourdomain.com.crt – main certificate
  2. AAACertificateServices.crt – Root Certificate
  3. USERTrustRSAAAACA.crt – Intermediate Certificate – 1
  4. SectigoRSADomainValidationSecureServerCA.crt – Intermediate Certificate – 2

Step 1: We shall create two files as below.

commercial_ca.crt (includes root certificate and two intermediate certificates)
commercial.crt (includes main certificate, root certificate and two intermediate certificates)

Step 2: Login to Zimbra server, move to directory /opt/zimbra/ssl/zimbra/commercial and create two files as below.

root@mail:~# cd /opt/zimbra/ssl/zimbra/commercial/
root@mail:/opt/zimbra/ssl/zimbra/commercial# touch commercial_ca.crt
root@mail:/opt/zimbra/ssl/zimbra/commercial# touch commercial.crt

Continue reading “Install a Sectigo Domain Validation SSL certificate in Zimbra” »

Share

Configuring SMTPS in Virtualmin

Under System Settings > Server Templates (and under the dropdown menu “Edit template section”) > Mail client auto-configuration. In the section Thunderbird auto-configuration XML, under the heading outgoingServer, I changed the port from $SMTP_PORT to $SMTPS_Port and selected XMLtemplate below as opposed to Automatically generated. My XML template is therefore as follows:

<?xml version="1.0" encoding="UTF-8"?>

<clientConfig version="1.1">
<emailProvider id="$SMTP_DOMAIN">
<domain>$SMTP_DOMAIN</domain>
<displayName>$OWNER Email</displayName>
<displayShortName>$OWNER</displayShortName>
<incomingServer type="imap">
<hostname>$IMAP_HOST</hostname>
<port>$IMAP_PORT</port>
<socketType>$IMAP_TYPE</socketType>
<authentication>$IMAP_ENC</authentication>
<username>$SMTP_LOGIN</username>
</incomingServer>
<outgoingServer type="smtp">
<hostname>$SMTP_HOST</hostname>
<port>$SMTPS_PORT</port>
<socketType>$SMTP_TYPE</socketType>
<authentication>$SMTP_ENC</authentication>
<username>$SMTP_LOGIN</username>
</outgoingServer>
</emailProvider>
</clientConfig>

If the variable $SMTPS_Port doesn’t work for you, you can try manually entering port 465.

Src: https://serverfault.com/questions/605090/configuring-smtps-in-virtualmin

Share

Mapping drives with Windows Explorer in Nextcloud

To map a drive using the Microsoft Windows Explorer:

  1. Open Windows Explorer on your MS Windows computer.
  2. Right-click on Computer entry and select Map network drive… from the drop-down menu.
  3. Choose a local network drive to which you want to map Nextcloud.
  4. Specify the address to your Nextcloud instance, followed by /remote.php/dav/files/USERNAME/.
    or example:
https://example.com/nextcloud/remote.php/dav/files/USERNAME/

Src: https://docs.nextcloud.com/server/latest/user_manual/en/files/access_webdav.html

Share

Reset user password of Discourse

Discourse is an excellent platform- super fast, super organized and super fresh looking. It has quite standarized and additional security options in the application UI. However, found a freat issue of updating any user of this platform as Admin (I was havign difficulties of self user password reset options, as the mail gateway was somewhat not working). 

So here goes the trick-

ssh into your server

cd /var/discourse
./launcher enter app
 rails c 
u = User.find_by_email('email@test.com') 
u.password='zKRR6vTZKvJAB84V9jdgeydS' 
u.save!
ctrl+d to exit
Share

Install OnlyOffice Document Server on Ubuntu 16

Step 1: Install ONLYOFFICE Document Server

Please note that OnlyOffice document server requires at least 2GB of RAM. An additional 2GB of swap space is recommended. OnlyOffice document server depends on PostgreSQL, Node.js, Redis Server, RabbitMQ server and Nginx. The following steps are tested on a Ubuntu 16.04 server but should also be applicable to other Debian-based Linux distributions.

Install PostgreSQL from Ubuntu repository

sudo apt install postgresql

Then create the onlyoffice database.

sudo -u postgres psql -c "CREATE DATABASE onlyoffice;"

Create the onlyoffice user.

sudo -u postgres psql -c "CREATE USER onlyoffice WITH password 'onlyoffice';"

Grant permission. Continue reading “Install OnlyOffice Document Server on Ubuntu 16” »

Share

How to Install and Configure GitLab on Ubuntu 16.04

GitLab is an open source GIT repository manager based on Rails and developed by GitLab Inc. It is a web-based GIT repository manager that allows your team to work on code, track bugs and feature requests and to test and deploy applications. GitLab provides features like a wiki, issue tracking, code reviews, activity feeds and merge management. It is capable of hosting multiple projects.

GitLab is available in four editions:

  • Gitlab CE (Community Edition) – self-hosted, free and support from the Community forum.
  • Gitlab EE (Enterprise Edition) – self-hosted, paid app, comes with additional features.
  • GitLab.com – SaaS, free.
  • GitLab.io – Private GitLab instance managed by GitLab Inc.

In this tutorial, I will show you step-by-step how to install GitLab CE (Community Edition) on your own Ubuntu 16.04 Xenial Xerus server. In this tutorial, I will be using the ‘omnibus’ package provided by GitLab for easy installation.

What we will do:

  • Install Packages
  • Install GitLab
  • Configure GitLab URL
  • Generate SSL Let’s encrypt and DHPARAM Certificate
  • Enable Nginx HTTPS for GitLab
  • Configure UFW Firewall
  • Perform the GitLab Installation
  • Testing

Prerequisites

  • Ubuntu 16.04 Server – 64bit
  • Min RAM 2GB
  • Root Privileges

Step 1 – Install required Ubuntu Packages
The first step is to install the packages needed for the GitLab installation. Please log in to the server as root user and upddate the Ubuntu repository.

ssh root@GitLabServer
apt-get update

Now install the packages including curl for downloading the GitLab repository, ca-certificates, and postfix for the SMTP configuration. Install all packages with the apt command below.

sudo apt install curl openssh-server ca-certificates postfix

During postfix installation, you will be prompted about the configuration, select ‘Internet Site’. and then enter the server domain name that shall be used for sending an email. Continue reading “How to Install and Configure GitLab on Ubuntu 16.04” »

Share