Month: December 2015

Enable GZIP compression on Apache

The instructions and code below will work on Apache. If they are not working there is another way that may work for you. If the above code did not seem to work, remove it from your .htaccess file and try this one instead…

After installing Magento, you have to take care of the “Indexers are invalid” problems.

To reindex in magento 2, go to the CLI and then the root folder of your magento installation and run the below command :

php bin/magento indexer:reindex

This will re-index all components of Magento

* Will find a way to make a automatic Cron job!

Be sure to do the following only if you don’t see the /admin/ or the CSS

I had to go to my apache configuration (/etc/apache2/apache2.conf) and change this:

< Directory /var/www/>
Options Indexes FollowSymLinks
AllowOverride none
Require all granted
< /Directory>

To:

< Directory /var/www/>
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
< /Directory>

et voilà!

Magento is working now,…! what a pain to install!

The biggest problem was to install the PHPmyAdmin Intl Component!

* Also, I had to upgrade MySQL5.4 to MySQL version 5.6.28
* Will upgrade to version 7.x.x soon,,, maybe!

Notice that in Webmin when you try to stop MySQL Database Server, not working anymore

Manual commands

START: systemctl start mysqld
STOP: systemctl stop mysqld
Restart: systemctl restart mysqld
Status: systemctl status mysqld
Enable at Start: systemctl enable mysqld

Don’t worry Webmin is aware about this situation, maybe in the next upgrade we will have a fix for that!

Running Webmin 1.770
CentOS7 all patched
Apache version 2.4.6
Latest PHPmyAdmin
MySQL version 5.6.28

Preparing Your Server for Magento

Have fun!!!!!

The following sections discuss how to download and install prerequisite software and install Magento CE or EE on a system running:

• Ubuntu 10 or later, or CentOS 6
• Apache 2.x
• nginx 1.7.x
• PHP 5.4 and required extensions
• MySQL database

SELinux Prerequisite

Security Enhanced Linux (SELinux) enables CentOS and Ubuntu administrators greater access control over their servers. If you’re using SELinux and Apache must initiate a connection to another host, you must run the commands discussed in this section.

If Apache and the database server are on the same host, you can skip this section and continue with Opening Ports In Your Firewall.

To enable Apache to initiate a connection to another host with SELinux enabled:

1. To determine if SELinux is enabled, use the following command:

   getenforce

   Enforcing displays to confirm that SELinux is running.

2. Enter one of the following commands:
   • CentOS

     setsebool -P httpd_can_network_connect=1

   • Ubuntu

     setsebool -P apache2_can_network_connect=1

Opening Ports In Your Firewall

Depending on your security requirements, you might find it necessary to open port 80 and other ports in your firewall. Because of the sensitive nature of networking security, Magento strongly recommends you consult with your IT department before proceeding. Following are some suggested references:

Creating phpinfo.php

phpinfo.php displays a large amount of information about PHP and its extensions. Add the following code anywhere in your web server’s docroot:

<?php
// Show all information, defaults to INFO_ALL
phpinfo();

To view the results, enter the following URL in your browser’s location or address field:

http://web-server-ip-or-host/phpinfo.php

Installing phpmyadmin

phpmyadmin is an easy-to-use, free database administration utility. You can use it to check and manipulate the contents of your database. You must log in to phpmyadmin as the MySQL database administrative user.

For more information about phpmyadmin, see the phpmyadmin home page.

For more detailed information about installation, see the phpmyadmin installation documentation.

To install phpmyadmin on CentOS:

1. Download the epel RPM for the version of CentOS you’re using. A sample follows.

   cd /tmp
   wget http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
   rpm -ivh epel-release-6-8.noarch.rpm

2. Install phpmyadmin as follows:

   yum -y install phpmyadmin

3. Authorize access to phpmyadmin from your machine’s IP address.
   1. Open the following file for editing:

      vim /etc/httpd/conf.d/phpMyAdmin.conf

   2. Replace the following IP address with your IP address

      #Require ip 127.0.0.1

      For example,

      Require ip 192.51.100.101

   3. Replace the following IP with your IP address

      #Allow from 127.0.0.1

      For example,

      Allow from 192.51.100.101

4. Save your changes to /etc/httpd/conf.d/phpMyAdmin.conf and exit the text editor.
5. Restart Apache.

   service httpd restart

6. To use phpmyadmin, enter the following command in your browser’s address or location field:

   http://host-or-ip-address/phpmyadmin

7. When prompted, log in using your MySQL database root or administrative user’s user name and password.

Creating a Magento Database Instance

This section discusses how to create a new database instance for Magento. Although a new database instance is recommended, you can optionally install Magento into an existing database instance. If you choose to do that, skip this section and continue with Installing Optional Sample Data.

Note: Before you continue, review the information about MySQL discussed in Prerequisites.

To create a new database instance:

1. Log in to your database server as any user.
2. Enter the following commands in the order shown to create a database instance named magento:

   mysql -u root -p 
   #Enter the remaining commands at the mysql> prompt.
   
   create database magento;
   GRANT ALL ON magento.* TO magento@localhost IDENTIFIED BY 'magento';

3. For MySQL versions between 5.0.2 and 5.1.6, you must enter this command:

   GRANT SUPER ON *.* TO 'magento'@'localhost';

4. After you’re done, enter exit
5. Test the database instance.

   mysql -u magento -p

   Messages similar to the following display to confirm you successfully created the database instance. If errors display, repeat the preceding commands.

   Welcome to the MySQL monitor.  Commands end with ; or \g.
   Your MySQL connection id is 20
   Server version: 5.1.67 Source distribution
   
   Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved.
   
   Oracle is a registered trademark of Oracle Corporation and/or its
   affiliates. Other names may be trademarks of their respective
   owners.
   
   Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

Extracting the Magento Installation Archive

Extract the Magento installation archive on your web server’s docroot.

The path on Ubuntu is typically /var/www

The path on CentOS is typically /var/www/html

Examples follow:

• Ubuntu

  cd /var/www
  cp /path/magento-install-archive .
  tar -zxf magento-install-archive-name

• CentOS

  cd /var/www/html
  cp /path/magento-install-archive-name .
  tar -zxf magento-install-archive

To optionally install Magento sample data, continue with the next section.

To install Magento without sample data, continue with Setting File and Directory Ownership and Privileges.

Installing Optional Sample Data

Magento provides sample data you can optionally install to give you an idea of what products look like in the Admin Panel and in your web store. You can use this sample data to learn how Magento works and to experiment with custom themes.

You must install sample data on the file system and in the database before you install Magento.

To skip sample data installation, continue with Setting File and Directory Ownership and Privileges.

To install Magento sample data:

1. Download the sample data from one of the locations discussed in Getting Magento CE or EE.
2. If necessary, transfer the sample data to your Magento server.
3. On your Magento server, extract the sample data archive to a directory other than your Magento installation directory.
4. Make note of the path to the sample data’s media subdirectory.
5. Change to the [your Magento install dir]/media directory.

   #Ubuntu example
   cd /var/www/magento/media
   
   #CentOS example
   cd /var/www/html/magento/media

6. As a user with privileges to write to the Magento installation directories (typically the web server user), copy the sample data’s media directory and subdirectories to your Magento installation directory.
   For example, to copy Magento sample data from /home/username to /var/www/magento, enter

   cp -R /home/username/media/* .

7. Magento CE 1.9 and Magento EE 1.14 only. You must also copy the sample data’s skin directory to [your Magento install dir]/skin as follows:
   For example, to copy Magento skin files from /home/username/skin to /var/www/magento/skin, enter

   cd [your Magento install dir]/skin
   cp -R /home/username/skin/* .

8. Import the CE or EE sample data into your MySQL database as follows:

   mysql -u root -p magento-db-instance-name < path-to-sample-data-extract-dir/sample-data-filename.sql

   EE 1.14 example

   mysql -u root -p magento < /home/username/magento_sample_data_for_1.14.0.0.sql

Setting File and Directory Ownership and Privileges

Magento recommends the following ownership and privilege settings for files and directories in the Magento installation directory:

• The Magento installation directory and all subdirectories are owned by the web server user.
  This enables the web server to change files in these subdirectories but other users cannot access them (except a higher-level user such as root).
• All directories have 700 permissions (drwx------).
  700 permissions give full control (that is, read/write/execute) to the owner and no permissions to anyone else.
• All files have 600 permissions (-rw-------).
  600 permissions mean the owner can read and write but other users have no permissions.

Note: The way you set permissions and ownership depends on whether Magento is running on a dedicated or hosted system:

• Hosted: A Magento server located on a hosting provider. A hosted system typically does not enable you to elevate to root. The web server typically runs as an ordinary user. Magento assumes you log in as this user to start and stop the web server and that you already own all the files and directories in the Magento installation directory. You can use chmod to change permissions on files and directories.
• Dedicated: A Magento server you control and operate. Unlike a hosted system, you can elevate to root and, as root, you can use the chown and chmod commands to set ownership and privileges in the Magento installation directory.

To set privileges and ownership:

1. Log in to your Magento server.
2. Change to your Magento installation directory:

   #Ubuntu example
   cd /var/www/magento
   
   #CentOS example
   cd /var/www/html/magento

3. Dedicated Magento server only. Enter the following command to set ownership of the Magento installation directory and all its subdirectories:

   chown -R web-server-user-name .

   For example, on Ubuntu where Apache usually runs as www-data, enter

   chown -R www-data .

4. Enter the following commands to set directory permissions to 700 and file permissions to 600:

   find . -type d -exec chmod 700 {} \;
   find . -type f -exec chmod 600 {} \;

Installing Magento CE or EE

This section discusses how to run the Magento installer, using Magento EE as an example. The Magento CE installer has exactly the same options; only the appearance is different.

To install Magento CE or EE:

1. Complete all of the tasks discussed earlier in this article.
2. Enter the following URL in your web browser’s address or location field:

   web-server-ip-or-host:port/magento-path/magento

   For example, if your web server is http://www.example.com, listens on port 80, and Magento is installed in the web server docroot’s magento subdirectory, enter

   http://www.example.com/magento

   Select the check box that indicates you agree to the terms and conditions, and click Continue.

3. On the Localization page, enter the following information.
   

   Option	Meaning
   Locale	From the list, click the option that best matches the locale in which your Magento server resides.
   Time Zone	From the list, click the option that best matches the time zone in which your Magento server resides.
   Default currency	From the list, click the default currency to use on your Magento web store.

   The following figure shows an example of configuring Magento for US English in the US Central time zone and using the US Dollar as the default currency.

   

4. Click Continue.
   The Configuration page displays. Each of its three sections is discussed in the following step.
5. In the Configuration page, enter the following information:
   1. In the Database Configuration section, enter the following information.
      

      Option	Meaning
      Database Type	From the list, click MySQL.
      Host	Enter the database server’s fully qualified host name or IP address. Use the default setting of localhost if your database server is on the same host as your web server.
      Database Name	Enter the name of the Magento database instance in which you want to install the Magento database tables.
      User Name	Enter the user name of the Magento database instance owner.
      User Password	Enter the Magento database owner’s password.
      Tables Prefix	(Optional.) Use only if you’re installing the Magento database tables in a database instance that has Magento tables in it already. In that case, enter a prefix to identify the Magento tables for this installation.Some customers have more than one Magento instance running on a server with all tables in the same database. This option enables those customers to share the database server with more than one Magento installation.

      A sample follows.

      

      1. In the Web Access Options section, enter the following information.
         

         Option	Meaning
         Base URL	Enter the base URL to use to access the Magento Admin Panel and your Magento web store.
         Admin Path	Enter the path to access the Admin Panel. This path is appended to Base URL. For example, if Base URL is http://www.example.com and Admin Path is admin, the Admin Panel’s URL is http://www.example.com/admin—provided you configured your web server for server rewrites.
         Enable Charts	Select the check box to display charts on the Admin Panel.
         Skip Base URL Validation Before the Next Step	Clearing this check box validates your server’s base URL by performing an HTTP GET. Clear this check box unless your web server’s base URL is not verifiable; for example, in a development or test environment.
         Use Web Server (Apache) Rewrites	Select this check box to enable the use of the Apache mod_rewrite module. You can select this check box only if you configured Apache to use server rewrites.
         Use Secure URLs (SSL)	Select this check box only if your web server supports SSL.

         A sample follows.

         

      2. In the Session Storage Options section, click one of the following options:
         • File to store user session data on the file system in the [your Magento install dir]/var/session directory.
           File-based session storage is appropriate unless the Magento file system access is slow or you have a clustered database.
         • Database to store user session data in the database.
           Choose database storage if you have a clustered database; otherwise, there might not be much benefit over file-based storage.
      3. Click Continue.
         Important: If errors display, you must resolve them before continuing.
      4. In the Create Admin Account page, enter the following information.
         

         Option	Meaning
         First Name	Enter the first name of the user you want to identify as the Magento web store owner.
         Last Name	Enter the user’s last name.
         Email	Enter the user’s email address.
         Username	Enter the Magento Admin Panel administrator’s user name. (You can create additional Magento administrators later.)
         Password	Enter the user’s password.
         Confirm Password	Enter the user’s password again for verification.
         Encryption Key	If you have one, enter a key to encrypt sensitive data (such as passwords and personally identifiable customer information) in the Magento database. If you don’t have one, Magento generates one for you. The encryption key is stored in [your Magento install dir]/app/etc/local.xml.

         A sample follows.

         

      5. Click Continue.
         The following page displays to indicate a successful installation.

Verifying that Magento CE or Magento EE Installed Successfully

To make sure Magento installed properly, you should log in to the Admin Panel to verify the Magento version.

You can also import products into Magento or perform other tasks that verify you can write to the database.

1. In a web browser’s location or address field, enter the URL to the Admin Panel. An example follows:

   http://www.example.com/magento/admin

   (The Admin Panel URL is a combination of the Base URL and Admin Path fields you entered when you installed Magento.

2. Log in to the Admin Panel as an administrator.
3. Scroll to the bottom of the page; the version should display as 1.14 (Magento EE) or 1.9.0.0 (Magento CE).
   The following figure shows an example.
   

Congratulations! You successfully installed Magento!

Setting Up Cron Jobs

Several Magento features require at least one cron job, which schedules activities to occur in the future. A partial list of these activities follows:

• Catalog price rules
• Newsletters
• Generating Google sitemaps
• Customer Alerts/Notifications (product price change, product back in stock)
• Reindexing (Magento EE 1.13 only)
• Private sales (Magento EE only)
• Automatic updating of currency rates
• Magento EE 1.14.1 and later, Magento CE 1.9.1 and later All Magento e-mails (including order confirmation and transactional)

Magento recommends running cron every minute for EE and every five minutes for CE.

UNIX systems schedule tasks to be performed by particular users using a crontab, which is a file that contains instructions to the cron daemon that tell the daemon in effect to “run this command at this time on this date”. Each user has its own crontab, and commands in any given crontab are executed as the user who owns the crontab.

For Magento, this user is the web server. To determine your web server’s user, enter the following command:

ps -o "user group command" -C httpd,apache2

In CentOS, the Apache user is typically apache; in Ubuntu, it’s typically www-data.

To create a cron job as the user who runs Apache, the following commands in the order shown:

1. Create or edit a crontab for the Apache user:

   crontab -u apache-user-name -e

2. A text editor displays. (You might need to choose a text editor first.)
   In the editor, enter the following:

   * * * * * /bin/sh /[your Magento install dir]/cron.sh

   For example, for CentOS,

   * * * * *  /bin/sh /var/www/html/magento/cron.sh

3. Save your changes to the crontab and exit the editor.

Setting Magento File System Permissions and Ownership After Installation

Setting Privileges and Ownership After You Install Magento

If you have installed Magento, you can set file system privileges and ownership as follows:

• For a dedicated Magento server, you set ownership of files and directory as the web server user. You set privileges as 500 (directories) and 400 (files).
• For a hosted Magento server on which the web server runs as the logged-in user name, you set privileges as as 500 (directories) and 400 (files).

Following is an explanation of the privileges:

• 500 permissions for directories (dr-x------) gives the web server user read and execute privileges to prevent the accidental deletion or modification of files in the directory. Other users have no access to Magento directories.
• 400 permissions for files (-r--------) prevent any user (even the web server user) from overwriting files.
  This prevents attacks that depend on overwriting existing files with malicious content.
• 700 permissions (drwx------) for the media/ and var/ directories give full control (that is, read/write/execute) to the owner and no permissions to anyone else.
• 600 permissions (-rw-------) for files in the media/ and var/ directories enable the web server user to write to them and to overwrite them.

To set up ownership and permissions on a dedicated Magento server:

1. Dedicated Magento server only. As a user with root privileges, find the web server user:
   • Apache:
     • Ubuntu: grep User /etc/apache2/apache2.conf
     • CentOS: grep User /etc/httpd/conf/httpd.conf
       Note: The preceding paths are samples only. The paths to these .conf files on your system might be different. You can use the command whereis nginx to find the location of the configuration files.

     Typically, the Apache web server user on CentOS is apache and the Apache web server user on Ubuntu is www-data.

   • nginx: Open the nginx configuration file, typically /etc/nginx/nginx.conf. The user directive specifies the user name. It might run as the Apache user if Apache is installed on the same system.
2. Change to the Magento installation directory.
   On CentOS, this is typically /var/www/html/magento. On Ubuntu, it is typically /var/www/magento.
3. Dedicated Magento server only. As a user with root privileges, enter the following command to set ownership of the Magento installation directory and all its subdirectories:

   chown -R web-server-user-name .

   For example, on Ubuntu where Apache usually runs as www-data, enter

   chown -R www-data .

4. Enter the following commands to set permissions:

   find . -type f -exec chmod 400 {} \;
   find . -type d -exec chmod 500 {} \; 
   find var/ -type f -exec chmod 600 {} \; 
   find media/ -type f -exec chmod 600 {} \;
   find var/ -type d -exec chmod 700 {} \; 
   find media/ -type d -exec chmod 700 {} \;
   chmod 700 includes
   chmod 600 includes/config.php

Securing Magento Extensions

If you set permissions and ownership as discussed in this article, you must change permissions temporarily to be able to use the Magento Connect Manager in the Admin Panel. (System > Magento Connect > Magento Connect Manager). You can still install extensions manually, however; that is beyond the scope of this article.

You can confirm the issue when you access Magento Connect Manager in the Admin Panel. The following error displays on the Extensions tab page:

Warning: Your Magento folder does not have sufficient write permissions.

To use Magento Connect Manager, you must:

1. Temporarily set 700/600 permissions on your Magento installation directory and subdirectories.
2. Install the extension.
   Magento Connect Manager typically installs extensions with 777 (world-writable) permissions.
3. Set permissions back to their recommended values.

In addition, if you have a dedicated Magento server, you should check ownership of files and directories and reset them if necessary. Often, Magento Connect Manager installs extensions with user and group ownership both set to the web server user.

Temporarily Resetting Permissions on Your Magento Installation Directory

To temporarily set file and directory permissions so you can use Magento Connect Manager:

1. Change to the Magento installation directory.
   On CentOS, this is typically /var/www/html/magento. On Ubuntu, it is typically /var/www/magento.
2. Enter the following commands:

   find . -type d -exec chmod 700 {} \;
   find . -type f -exec chmod 600 {} \;

3. Install your extension using the Magento Connect Manager.

Restoring the Recommended Permissions

Enter the commands discussed in this section to return permissions and ownership to their recommended values after you have installed extensions.

To restore Magento installation directory permissions:

1. Change to the Magento installation directory.
   On CentOS, this is typically /var/www/html/magento. On Ubuntu, it is typically /var/www/magento.
2. Dedicated Magento server only. As a user with root privileges, enter the following command to set ownership of the Magento installation directory and all its subdirectories:

   chown -R web-server-user-name .

   For example, on Ubuntu where Apache usually runs as www-data, enter

   chown -R www-data .

3. Enter the following commands to set permissions:

   find . -type f -exec chmod 400 {} \;
   find . -type d -exec chmod 500 {} \; 
   find var/ -type f -exec chmod 600 {} \; 
   find media/ -type f -exec chmod 600 {} \;
   find var/ -type d -exec chmod 700 {} \; 
   find media/ -type d -exec chmod 700 {} \;

Applying Magento Support Patches

Magento Support typically provides a shell script to patch various Magento issues. When you run the shell script, file and directory permissions are typically not changed; however, the files provided with the patch are owned by the user who applied the patch. If you have a dedicated Magento server, this is typically root; therefore, after applying the patch, you must change file ownership.

If you are required to apply a patch provided by Magento Support, use the following process:

1. Get the patch from Magento Support.
2. Follow the instructions provided with the patch.
   Typically, you run a shell script as either a user with root privileges or as the owner of the Magento installation directory.
3. If you ran the patch as the owner of the Magento installation directory, you’re done. File permissions aren’t usually changed; however, you should check and reapply file and directory privileges if necessary.
4. If you ran the patch as a user with root privileges, use the following steps to reset file ownership:
5. Dedicated Magento server only. Find the web server user:
   • Apache:
     • Ubuntu: grep User /etc/apache2/apache2.conf
     • CentOS: grep User /etc/httpd/conf/httpd.conf

     Typically, the Apache web server user on CentOS is apache and the Apache web server user on Ubuntu is www-data.

   • nginx: Open the nginx configuration file, typically /etc/nginx/nginx.conf. The user directive specifies the user name. It might run as the Apache user if Apache is installed on the same system.
6. As a user with root privileges, enter the following command from the Magento installation directory:
   chown -R web-server-user-name . For example, on Ubuntu where Apache usually runs as www-data, enter chown -R www-data.

During the installation, errors like the following display:
Path "/var/www/html/magento/app/etc" must be writable.

Allow HTTPD to send email SELinux

*****  Plugin httpd_can_sendmail (91.4 confidence) suggests   ****************

If you want to allow httpd to send mail
Then you must setup SELinux to allow this
Do
setsebool -P httpd_can_sendmail=1

*****  Plugin catchall (9.59 confidence) suggests   **************************

If you believe that sendmail.postfix should be allowed open access on the main.cf file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep sendmail /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Installing Config Security Firewall (CSF) on CentOS 7 and Webmin

ConfigServer Security & Firewall (CSF) is a stateful packet inspection firewall (SPI), login/intrusion detection, and security application for Linux servers. It is a very popular security suite, but isn’t officially supported yet on CentOS 7.

CentOS 7 uses firewalld rather than iptables. A quick internet search will show that many faithful CentOS users find firewalld far too complicated for their needs and are reverting back to iptables. Iptables was the standard firewall for CentOS 5 and 6.

This guide shows you how to disable firewalld, install IP tables, CSF dependencies, and CSF.

Install CSF

Stop and disable firewalld.

   systemctl disable firewalld
   systemctl stop firewalld

Install iptables.

 yum -y install iptables-services

Create files needed by iptables.

  touch /etc/sysconfig/iptables
  touch /etc/sysconfig/iptables6

Start iptables.

  systemctl start iptables
  systemctl start ip6tables

Enable iptables at boot.

  systemctl enable iptables
  systemctl enable ip6tables

Install the CSF dependencies.

  yum -y install wget perl unzip net-tools perl-libwww-perl perl-LWP-Protocol-https perl-GDGraph -y

Download and launch the CSF installer.

  cd /opt
  wget https://download.configserver.com/csf.tgz
  tar -xzf csf.tgz
  cd csf
  sh install.sh

Remove the installation files.

 rm -rf /opt/csf
 rm /opt/csf.tgz 

(Optional) Webmin integration

If you use Webmin, then you can install the CSF Webmin module.

Login to Webmin and navigate to the following page.

Webmin > Webmin Configuration > Webmin Modules >

Click “From local file” and insert the following.

  /usr/local/csf/csfwebmin.tgz > 

Install the module & enjoy!

My WordPress website will not load outside my local network!

Server Specifications (HP PROLIANT DL380-G6 DUAL XEON)
CentOS 7
MySQL
PHP
Apache
WordPress

All latest version but….
* You should stick to MySQL version 5.5.44 for now! (25-12-2015)

Solutions

1. Check your wp-config.php file that reside in the root of your WordPress directory

You have to look for this code section

/**#@+
* Authentication Unique Keys and Salts.
*
* Change these to different unique phrases!
* You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
*
* @since 2.6.0
*/
define(‘AUTH_KEY’,         ‘@z]6-zHz-}c:i?+Dq14vez%2be~V93_Ig{X9c-|O.t9Ab?^+k;-m)bZ=qNvZ1,x$’);
define(‘SECURE_AUTH_KEY’,  ‘ <;Sq]#!~a0xC|kqzVRuPG@DIJRnk:1FT(1qB[1v[bi/h >t@^/{ Lav24)BEO&[‘);
define(‘LOGGED_IN_KEY’,    ‘A+;~!`7,W ,wE>=Kn4.BzCbdx34O_JMkOI)b2%Ez$RzT)O:2[b|+19mrh)IAWOGo’);
define(‘NONCE_KEY’,        ‘s[L2u1&rpt8C)]bZqf7]`zof>fAswRg0y|qZZ)vcDX*/j-Ez[|PW}:eO-8AlHJ8k’);
define(‘AUTH_SALT’,        ‘KW8wra;81,>O:k4Z8(2+(YZEDX>K/vF@KdYeS0a*Mom)*<g6e+1lf -n@_w>bFyn’);
define(‘SECURE_AUTH_SALT’, ‘e5if.r^`P?KK;nkv<h[[FbH^w&5nc]>Dy(Dx#z3sYg(-9![{spcQMrVX8IlK:Xwx’);
define(‘LOGGED_IN_SALT’,   ‘F:|V^sHC+qO`=cselr|}&K<lS6:Tnd/A}&r8g<7?qj!AL1-8Q/pd(4;P3sKM=Q/Q’);
define(‘NONCE_SALT’,       ‘?-C_Ny0>E5Z;9Gj$&nJ{mr<8xkA{%FxyL~-K-f7>^WK$83C<hu;-J3-mt+J7>N{d’);

*This have to be added with your credential

define(‘WP_HOME’,’http://domain.xxx/wordpress’);
define(‘WP_SITEURL’,’http://domain.xxx/wordpress’);
/**#@-*/

2. From my personal experience and many try and fail I manually added this

define(‘WP_SITEURL’,’http://xxx.xxx.xxx.xxx/wordpress-directory’);
define(‘WP_HOME’,’http://xxx.xxx.xxx.xxx/wordpress-directory’);

• Replace http://xxx.xxx.xxx.xxx/ with your IP or Domain name
• Also make sure that your ISP is not blocking Port:80
• Also notice that when your IP will change you will have to change it too!

Restart Apache

systemctl restart httpd.service

3. Make sure that the directory is Chown by Apache if you are using Webmin

>others>file manager>

go to …

/var/www/html/ + the name of your installed wordpress directory

Ex:
/var/www/html/wordpress/

And now select the (wordpress)

Go to tools/Chown Selected/

Chown your WordPress directory name to : apache:apache

* This will fix the plugin update problem and also the image upload to your posts or pages of wordpress

Et voilà!

Other details generated by CentOS 7 (SELinux)

*****  Plugin httpd_write_content (92.2 confidence) suggests   ***************

If you want to allow httpd to have write access on the wordpress directory
Then you need to change the label on '/var/www/html/wordpress'
Do
# semanage fcontext -a -t httpd_sys_rw_content_t '/var/www/html/wordpress'
# restorecon -v '/var/www/html/wordpress'

*****  Plugin catchall_boolean (7.83 confidence) suggests   ******************

If you want to allow httpd to unified
Then you must tell SELinux about this by enabling the 'httpd_unified' boolean.
You can read 'None' man page for more details.
Do
setsebool -P httpd_unified 1

*****  Plugin catchall (1.41 confidence) suggests   **************************

If you believe that httpd should be allowed write access on the wordpress directory by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep httpd /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

H A P P Y   H O L I D A Y ‘ S