m,
Linux / UNIX: DNS Lookup Command
nslookup (name server lookup)
nslookup viroblock.com.au
Domain Name Servers
$ host -t ns cyberciti.biz
Domain Mail Server
host -t mx cyberciti.biz
Showing posts with label linux. Show all posts
Showing posts with label linux. Show all posts
Friday, January 8, 2021
Thursday, June 25, 2020
Redis installation
Uninstall Redis from ubuntu
A-a. if you use apt-get:
Here --auto-remove option removes the Redis server package and its dependencies.
And the purge option removes the configuration and other Redis related data files.
This successfully uninstalls the Redis from the Ubuntu server.
After uninstalling the package, in the Ubuntu system check if the package is present or not. For this, we use the command, sudo apt-cache policy redis-server
this will show redis-server: Installed: (none)
A-b. If you use make file - Compiled redis manually:
sudo rm -r /var/redis/# Stop a all instance. sudo service redis_version stop sudo service redis_6379 or systemctl stop redis
# Remove the files in sudo rm /usr/local/bin/redis-* # Remove Redis Configuration.
sudo rm -r /etc/redis/rm /etc/redis/redis.conf# Remove existing Redis log files. sudo rm /var/log/redis_*# Remove existing Redis data directory.
sudo rm -r /var/lib/redis/ # Remove existing Redis server init scripts
sudo rm /etc/init.d/redis_* # Remove existing Redis PID files (Only if exists) sudo rm /var/run/redis_* # Restart your Ubuntu server must. sudo reboot now
Install these two preinstall packages first:
sudo apt update -y apt-cache policy redis-server sudo apt install build-essential tcl pkg-config -y
mkdir redis
cd redis # download redis
wget http://download.redis.io/releases/redis-6.0.9.tar.gz
tar xzf redis-6.0.5.tar.gz
cd redis-6.0.9
# Proceed with the make command make cd src && make test
Install the program system wide - install the binaries onto the system - Make a global Alias:
cd src && sudo make install
Start on booting:
sudo systemctl enable redis-server.service
Shutdown:
redis-cli shutdown
Start the server:
redis-server
Clint terminal:
redis-cli
set name foo
get name
But for production environments, you should use a configuration file. In order to start Redis with a configuration file, use the full path of the configuration file as first argument, like in the following example: redis-server /etc/redis.conf
Installing Redis more properly
Create a directory in which to store your Redis config files and your data:
sudo mkdir /etc/redis sudo mkdir /var/redisCopy the init script that you'll find in the Redis distribution under the utils directory into /etc/init.d. We suggest calling it with the name of the port where you are running this instance of Redis. For example:
sudo cp /home/mg/redis/redis-6.0.5/utils/redis_init_script /etc/init.d/redis_6379 sudo cp /home/mg/redis/redis-6.0.5/utils/redis_init_script /etc/init.d/redis_6379Edit the init script.
sudo vi /etc/init.d/redis_6379
Make sure to modify REDISPORT accordingly to the port you are using. Both the pid file path and the configuration file name depend on the port number.
Copy the template configuration file you'll find in the root directory of the Redis distribution into /etc/redis/ using the port number as name, for instance:
sudo cp redis.conf /etc/redis/6379.confCreate a directory inside /var/redis that will work as data and working directory for this Redis instance:
sudo mkdir /var/redis/6379Edit the configuration file, making sure to perform the following changes:
- Set daemonize to yes (by default it is set to no).
- Set the pidfile to
/var/run/redis_6379.pid(modify the port if needed). - Change the port accordingly. In our example it is not needed as the default port is already 6379.
- Set your preferred loglevel.
- Set the logfile to
/var/log/redis_6379.log - Set the dir to /var/redis/6379 (very important step!)
Finally, add the new Redis init script to all the default runlevels using the following command:
sudo update-rc.d redis_6379 defaults
You are done! Now you can try running your instance with:
sudo /etc/init.d/redis_6379 start
sudo /etc/init.d/redis_6379 stop
sudo systemctl restart redis_6379.service
sudo systemctl status redis_6379.service
sudo systemctl disable redis
(Not sure) sudo systemctl enable redis_6379.service
Make sure that everything is working as expected:
- Try pinging your instance with redis-cli.
- Do a test save with redis-cli save and check that the dump file is correctly stored into /var/redis/6379/ (you should find a file called dump.rdb).
- Check that your Redis instance is correctly logging in the log file cat /var/log/redis_6379.log.
- If it's a new machine where you can try it without problems make sure that after a reboot everything is still working.
Note: In the above instructions we skipped many Redis configuration parameters that you would like to change, for instance in order to use AOF persistence instead of RDB persistence, or to setup replication, and so forth. Make sure to read the example redis.conf file (that is heavily commented) and the other documentation you can find in this web site for more information.
Configure Redis for Magento
Configure Redis
# Redis default caching
bin/magento setup:config:set \
--cache-backend=redis \
--cache-backend-redis-server=127.0.0.1 \
--cache-backend-redis-port=6379 \
--cache-backend-redis-db=0
# Redis page caching
bin/magento setup:config:set \
--page-cache=redis \
--page-cache-redis-server=127.0.0.1 \
--page-cache-redis-port=6379 \
--page-cache-redis-db=1
# Redis for session storage
bin/magento setup:config:set --session-save=redis \
--session-save-redis-host=127.0.0.1 \
--session-save-redis-port=6379 \
--session-save-redis-log-level=4 \
--session-save-redis-db=2
NB: L2 cache
Wednesday, June 24, 2020
SSH public/private key
Key in your hand is Private, and DoorLock is called Public key(Lock itself).
Generating Keypair:
ssh-keygen -t rsa -b 4096 -f ~/.ssh/github1 -C "my@mail.com"
-t: rsa algo name
-b: 2048 enctyption bits
-C: Comments
Upload the key to your server
Once an SSH key has been created, the ssh-copy-id command can be used to install it as an authorized key on the server.
First, make user1 owner to the ~/.ssh folder.
mg@node2:~$ sudo mkdir -p /home/user1/.ssh mg@node2:~$ sudo chown fresh:users -R /home/user1/.ssh/ mg@node2:~$ sudo chmod -R 700 /home/user1/.ssh/ mg@node2:~$ ls -al /home/user1
Edit the sshd config:
sudo vi /etc/ssh/sshd_config -> PasswordAuthentication no sudo service sshd restart
From client (git-bash client) system:
$ ssh-copy-id -i /c/Users/Rita/On...ve/P...ming/SSH/xkeyx.pub user1@113.15.51.51
(enter pass if required) After a successful install, it will show the bellow message.
Disable Password authentication, Inside the /etc/ssh/sshd_config file:
sudo vi /etc/ssh/sshd_config -> PasswordAuthentication no sudo service sshd restart
[
(ssh-copy for another user https://measure9.varkel.net/2017/09/ssh-copy-id-key-to-other-user-than-yourself/)
cat ~/.ssh/node2.pub | ssh -i ~/.ssh/node2
mg@192.168.10.115 sudo tee -a /home/life110volts/.ssh/authorized_keys
(or from Windows pc)
scp C:\Users\MyUserName\.ssh/id_rsa.pub example_user@203.0.113.100:~/.ssh/authorized_keys
]
SSH activities
Adding a private key to SSH Agent:
eval "$(ssh-agent -s)" ssh-add ~/.ssh/github1 passcode: d******3
To list the ssh-keys
$ ssh-add –l $ ls -l ~/.ssh
To remove a key from the ssh-agent,
$ ssh-add -d /home/user/.ssh/id_rsa (To remove all) $ ssh-add –D
Keeping the private keys secure is important. It is suggested that the ssh-agent is terminated or locked when it is not needed anymore.
$ eval $(ssh-agent -s -k)
MacOS: Pbcopy < ~/.ssh/id_rsa.pub Windows: clip < ~/.ssh/id_rsa.pub ssh -T git@github.com ssh -T hg@bitbucket.org
Test login
ssh -T -i ~/.ssh/github1 hg@bitbucket.org
Login Directly without a key agent.
ssh -T -i ~/.ssh/github1 hg@bitbucket.org ssh -T -i ~/.ssh/github1 git@github.com
Login with ssh and deploy to a Godaddy instance:
eval "$(ssh-agent -s)" ssh-add ~/.ssh/gokkdy ssh -i ~/.ssh/godkkdy bangkkking@107.1k.k0.1k
After connected to GoDaddy.
cd /home/bsdfsdfng/#mydomains/dudfhool.com eval "$(ssh-agent -s)" ssh-add ~/.ssh/cmdfinc.com ssh -T -i ~/.ssh/cmarinc.com hg@bitbucket.org git pull upstream master
Thursday, June 18, 2020
LAMC stack - U20-Apache-CGI-M (Installing Ubuntu 20LTS) * bearbone server
Technologies: 
Ubuntu 20.04.1 LTS / MySQL 8 /PHP 7.4-(fpm)(mod_security) /Composer 1.7 /Redis-6.0.9 / ElasticSearch7.10
Ubuntu 20.04.1 LTS / MySQL 8 /PHP 7.4-(fpm)(mod_security) /Composer 1.7 /Redis-6.0.9 / ElasticSearch7.10
Apache FastCGI with PHP-FPM is one of the best stacks to host PHP applications. This stack is not as easy as setting up a basic LAMP stack, but it is far better than the basic LAMP stack when it comes to performance. The key ingredient in this stack is FPM which stands for Fast Process Manager. In this stack, Apache will send all the PHP files for processing to FPM. It will then return the rendered output to the browser -
Hello hello how are youHello hello its good to see you!I say hello, to you and all your friend.I say hello, lets meet them together! lets play togetherLets have fun with friends.We are all friends.
Song credit: Sing along to the Hello song from 'Something Special'. Visit http://www.bbc.co.uk/cbeebies to find even more fun games and videos for your pre-schooler in a safe child friendly environment.
Pertition:
swap - 0% to 200% of system memory.
/boot - if needed, 2.5GiB or less.
/opt - only if explicitly needed. Size as req'd
/app - same as opt
/var - only if needed, 5 to 10GiB
/tmp - put it on root, otherwise 512MiB to 2.5GiB
/usr - put it on root, otherwise 35 to 40GiB
/ - (root) 10GiB min (if other parts used), otherwise 65GiB
/home - Whatever is left
----- What I use on my non-work computers -----
/ - 100GiB
/var - only if needed, 10GiB
swap - no more than 100% or 150% of system memory
/boot - if needed, 2.5GiB or less.
/home - Whatever is left
Ubuntu version
lsb_release -a service --status-all
Hostname
sudo hostnamectl hostname hostname --fqdn dnsdomainname sudo vi /etc/hosts 127.0.1.1 www.ejamuna.com node1
vi /etc/hosts
# IPv4 and IPv6 localhost aliases 127.0.0.1 node2.mg.com node2 localhost ::1 node2.mg.com node2 localhost
Securing your Server *
References: Securing Your Server
Update Your System–Frequently
sudo apt update && sudo apt upgrade -y
Adding a Limited User Account
$useradd tommy -m -s /bin/bash -g users -c "my comments" $passwd tommy (change password for the mentioned user)
Change passwd for the root user:
$sudo passwd root
Create an Authentication Key-pair (client pc)
- Upload the public key to your Server.
- Test your keys are working and make a note for the passcodes.
Inside the /etc/ssh/sshd_config file:
Disallow root logins over SSH
PermitRootLogin no
Disable Password authentication
PasswordAuthentication no
sudo service sshd restart
Test: ssh mg@192.168.10.115 password login is denied by public key!
Handy scripts (create ssh for a user)
sudo useradd tommy -m -s /bin/bash -g users -c "my comments" sudo passwd tommysudo mkdir -p /home/tommy/.ssh sudo chown tommy:users -R /home/tommy/.ssh/ sudo chmod -R 700 /home/tommy/.ssh/ ls -al /home/tommy
sudo vi /etc/ssh/sshd_config PasswordAuthentication no sudo service sshd restart # Local pc ssh-keygen -t rsa -b 4096 -f /drives/c/Users/Rita/OneDrive/Programming/SSH/ejamuna_com -C "admin@ejamuna.com" ssh-copy-id -i /drives/c/Users/Rita/OneDrive/Programming/SSH/ejamuna_com.pub mg@192.168.10.13 sudo vi /etc/ssh/sshd_config PasswordAuthentication yes sudo service sshd restart
Installing packages
Update Your System–Frequently
sudo apt update && sudo apt upgrade -y
Install example
Check if the package exists on https://packages.ubuntu.com/
apt install vim apt update
Reinstall
apt-get install --reinstall systemctl
List the full path of the files inside this package
dpkg -L systemctl
Check if any output for systemctl
apt-cache search systemctl
Using Init scripts to manage services on Ubuntu
To start a service: /etc/init.d/ufw start
To stop a service: /etc/init.d/ufw stop
To stop a service: /etc/init.d/ufw restart
To check the status of service: /etc/init.d/ufw status
How To Install Package on Ubuntu
sudo apt-get update -y
sudo apt-get install -y unzip
apt-get install net-tools
MySQL 8 in Ubuntu 20
Uninstall
sudo -i
service mysql stop
killall -KILL mysql mysqld_safe mysqld
apt-get --yes purge mysql-server mysql-client
apt-get --yes autoremove --purge
apt-get autoclean
deluser --remove-home mysql
delgroup mysql
rm -rf /etc/apparmor.d/abstractions/mysql /etc/apparmor.d/cache/usr.sbin.mysqld /etc/mysql /var/lib/mysql /var/log/mysql* /var/log/upstart/mysql.log* /var/run/mysqld
updatedb
exit
Installing MySQL 8 on Ubuntu:
sudo apt update && sudo apt upgrade -y sudo apt install curl nano git
It is important to specify the version of mysql, e.g. (apt purge on an already removed package. Usually, apt remove is more than enough for uninstalling a package.)
apt --yes purge mysql-server-5.7 mysql-client-5.7
sudo apt-cache search mysql | grep client >output> mysql-client-8.0 - MySQL database client binaries sudo apt-cache search php- | less
>Custom install> sudo apt-get install mysql-server-5.7 mysql-client-5.7 -y
To install MySQL, run the following command from a terminal prompt:
sudo apt install mysql-server
The network status of the MySQL service can also be checked by running the ss command at the terminal prompt:
sudo ss -tap | grep mysql
When you run this command, you should see something similar to the following:
LISTEN 0 151 127.0.0.1:mysql 0.0.0.0:* users:(("mysqld",pid=149190,fd=29))
LISTEN 0 70 *:33060 *:* users:(("mysqld",pid=149190,fd=32))
If the server is not running correctly, you can type the following command to start it:
mysql -V sudo service mysql restart
A good starting point for troubleshooting problems is the systemd journal, which can be accessed at the terminal prompt with this command:
sudo journalctl -u mysql
[
/usr/bin/mysql -u root -p
***
mysql> quit;
]
Do not write mysql -u root, Just write "sudo mysql", In Ubuntu systems running MySQL 5.7 (and later), the root user is authenticated by the auth_socket plugin by default.
(For version MySQL 5.7 and later, enter the following command in the mysql shell, replacing password with your new password:)
Secure the MySQL
sudo mysql_secure_installation utility
Answer them all with ...y
Start /stop
sudo service mysql start sudo service mysql stop sudo service mysql restart
After making a configuration change, the MySQL daemon will need to be restarted:
sudo systemctl restart mysql.service
Start the server on System startup
sudo systemctl enable mysql
Create a new database, user, and to grant privileges for the database to the user /revoke.
Create user and Database
sudo mysql REVOKE ALL PRIVILEGES ON dbname.* TO 'user1'@'localhost'; DROP database dbname; DROP USER 'user1'@'localhost'; CREATE DATABASE dbname; CREATE USER 'user1'@'localhost' IDENTIFIED BY '%^passg7W'; >Only for below 8>GRANT ALL PRIVILEGES ON dbname.* TO 'user1'@'localhost' IDENTIFIED BY '%^passg7W'; MySQL8 = ( GRANT ALL ON dbname.* TO 'user1'@'localhost'; ALTER USER 'user1'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password'; ) FLUSH PRIVILEGES; quit
Views
mysql> SELECT User, Host, authentication_string FROM mysql.user; mysql> show databases; mysql> DROP database dumbschool;
mysql> SET GLOBAL log_bin_trust_function_creators = 1;
Display MySQL User Account Privileges:
SHOW GRANTS FOR 'user1'@'localhost';
Revoke Privileges from a MySQL User Account
mysql> REVOKE ALL PRIVILEGES ON database_name.* TO 'database_user'@'localhost';
Remove an Existing MySQL User Account
mysql> DROP USER 'user'@'localhost'
Import a Database
mysql -u username -p database_name < FILE.sql
Firewall: SELinux
Todo
Todo
Todo
Firewall: UFW
https://linuxize.com/post/how-to-setup-a-firewall-with-ufw-on-ubuntu-18-04
https://www.digitalocean.com/community/tutorials/how-to-set-up-a-firewall-with-ufw-on-ubuntu-18-04
Got connection refused! plz check bellow.
apt-get install ufw sudo ufw app list sudo ufw status verbose sudo ufw status
Let us look into the “Apache Full” profile. To do so, run:
sudo ufw app info 'Apache Full'
Run the following command to allow incoming HTTP and HTTPS traffic for this profile:
sudo ufw allow 'Apache Full' sudo ufw allow 'OpenSSH' sudo ufw allow 10000/tcp
Configure Your Firewall:
sudo ufw disable
sudo ufw enable
ufw reset ( turn off UFW completely and delete all the rules)
Delete rule:
sudo ufw status numbered ufw delete *2 ufw delete allow http123
Anything actually listening on port 80 :
netstat -lpn | grep :80
Shorewall
iptables *
chkconfig iptables
iptables -L -v -n --line-number
sudo lsof -n -sTCP:LISTEN -i:80
sudo iptables -A INPUT -p tcp --dport 80 -j ACCEPT
Then to prevent it from losing the iptables configuration on restart, use:
sudo apt install iptables-persistent sudo /etc/init.d/netfilter-persistent save ./firewall-reload iptables-save > /etc/iptables/iptables.rules reboot now
netplan
ip a ip route nslookup google.com ifconfig netplan generate netplan apply
Install Apache2.4
sudo apt update && sudo apt upgrade -y sudo apt-get install curl nano git wget vim -y sudo apt-cache search apache2 | grep ver sudo apt-get install apache2 -y apache2 -version
Enable on Startup:
sudo systemctl enable apache2
Backup your orginal site config filesudo cp /etc/apache2/sites-available/000-default.conf /etc/apache2/sites-available/000-default.conf.orginal sudo cp /etc/apache2/sites-available/default-ssl.conf /etc/apache2/sites-available/default-ssl.conf.orginal sudo cp /etc/apache2/mods-enabled/fastcgi.conf /etc/apache2/mods-enabled/fastcgi.conf.backupRedhat: /etc/httpd/
Install FastCGI:
CGI like FastCGI processes are persistent and they can handle more than one requests per processes.
sudo apt-cache search apache2 | grep libapache2-mod-fcgi
Note: sudo apt install libapache2-mod-fcgi (not working now. 2019)
sudo apt install libapache2-mod-fcgid -y (working...2020 )
cd /tmp && wget https://mirrors.edge.kernel.org/ubuntu/pool/multiverse/liba/libapache-mod-fastcgi/libapache2-mod-fastcgi_2.4.7~0910052141-1.2_amd64.deb
sudo dpkg -i libapache2-mod-fastcgi_2.4.7~0910052141-1.2_amd64.deb
Start:
sudo systemctl start apache2.service service apache2 start
Status:
sudo systemctl status apache2 service apache2 status
Restart:
sudo systemctl restart httpd
sudo systemctl restart apache2.service service apache2 restart
Reload:
sudo systemctl reload apache2.service service apache2 reload
Stop:
sudo systemctl stop apache2.service
Configuration files:
Redhat: /etc/httpd/conf/httpd.conf
/etc/apache2/apache2.conf – This is the main Apache configuration file and controls everything Apache does on your system. Changes here affect all the websites hosted on this machine.
/etc/apache2/ports.conf – The port configuration file. You can customize the ports Apache monitors using this file. By default, Port 80 is configured for Http traffic.
/etc/apache2/sites-available – Storage for virtual host files. A virtual host is a record of one of the websites hosted on the server.
/etc/apache2/sites-enabled – This directory holds websites that are ready to serve clients. The a2ensite command is used on a virtual host file in the sites-available directory to add sites to this location.
Default webroot: /var/www/html/
*** Checking the inbound rules from the EC2 dashboard, from below we can see that only the “PORT 22” is open, which is only for “SSH“.
See the ufw firewall section.
Install Modules:
a2enmod proxy_http
a2enmod proxy
service apache2 reload
PHP 7.4 (fpm - Fast Process Manager)
sudo apt update && sudo apt upgrade -y sudo apt-cache search php7.2 | grep php
To verify if PHP is installed already, in the command line, type:
php -v
$ sudo apt-get install php7.4-fpm php7.4-mysql php7.4-mbstring php7.4-curl php7.4-dom -y
$ sudo apt-get install php7.2 libapache2-mod-php7.2 php7.2-common php7.2-gd php7.2-mysql php7.2-curl php7.2-intl php7.2-xsl php7.2-mbstring php7.2-zip php7.2-bcmath php7.2-iconv php7.2-soap -y
For Magento with FPM only
$ sudo apt install php7.4-fpm libapache2-mod-php7.4 php7.4-common php7.4-gd php7.4-mysql php7.4-curl php7.4-intl php7.4-xsl php7.4-mbstring php7.4-zip php7.4-bcmath php7.4-iconv php7.4-soap -y php -v
Laravel Server Requirements mention that BCMath, Ctype, JSON, Mbstring, OpenSSL, PDO, Tokenizer, and XML extensions are required. Most of the extensions are installed and enabled by default.
PHP version-specific installation (if PHP 7.4 installed)
sudo apt-get install zip unzip php-zip
sudo apt install php7.4-fpm php7.4-common php7.4-bcmath openssl php7.4-json php7.4-mbstring php-xml php-mysql php7.4-curl -y
sudo phpenmod pdo_mysql
libapache2-mod-php7.4
sudo apt-cache search apache2 | grep libapache2-mod-e$ sudo apt install php7.3-fpm libapache2-mod-php7.3 php7.3-common php7.3-gd php7.3-mysql php7.3-curl php7.3-intl php7.3-xsl php7.3-mbstring php7.3-zip php7.3-bcmath php7.3-iconv php7.3-soap -y
Verify that all required PHP extensions were installed:
sudo php -me
and check "Server API Apache 2.0 Handler" that is PHP-FPM is not configured yet!
To locate the PHP command-line configuration, enter
php --ini | grep "Loaded Configuration File"
Configure Apache with PHP-fpm on Ubuntu 20
Right now, Our Apache web server and PHP-FPM are configured and can work individually. But we still have to tell our Apache webserver to pass PHP requests to PHP fast process manager.
To enable PHP 7.4 FPM in Apache2 do (after php7.2-fpm installed): [If disable the older version of PHP (a2dismod [oldversion])] [Edit for 7.* if version changed]
sudo cat /etc/apache2/conf-available/php7.4-fpm.conf sudo cp /etc/apache2/conf-available/php7.4-fpm.conf /etc/apache2/conf-available/php7.4-fpm.conf.orginal sudo vi /etc/apache2/conf-available/php7.4-fpm.conf
<IfModule mod_fastcgi.c> AddHandler php7-fcgi .php Action php7-fcgi /php7-fcgi Alias /php7-fcgi /usr/lib/cgi-bin/php7-fcgi FastCgiExternalServer /usr/lib/cgi-bin/php7-fcgi -socket /var/run/php/php7.4-fpm.sock -pass-header Authorization -idle-timeout 60 <Directory /usr/lib/cgi-bin> Require all granted </Directory> </IfModule>
Test conf script for errors:
sudo apache2ctl configtest
PHP 7.4 FPM disabled by default. To enable PHP 7.4 FPM in Apache2 do:
sudo a2enmod proxy_fcgi setenvif sudo a2enconf php7.4-fpm sudo a2enmod actions expires
sudo systemctl restart apache2 sudo systemctl reload apache2
The module proxy_fcgi provides support for the FastCGI protocol. The associated setenvif sets the variables sent to the FastCGI.
sudo systemctl restart php7.4-fpm apache2 sudo service php7.4-fpm status
Making a new website with a domain
Make a particular user for a particular site standard practice and also put him to the www group.
sudo mkdir -p /var/www/ejamuna.com
Then assign the ownership of the directory to Apache2 through the following commands:
Is Apache running as www-data?
ps axu | grep -E 'apache|www-data|http'
sudo chown -R <www-data>:www-data /var/www/ejamuna.com no need: sudo chmod -R 755 /var/www/ejamuna.com
[ no need also
sudo chown -R ec2-user:apache /var/www
sudo chmod 2775 /var/www && find /var/www -type d -exec sudo chmod 2775 {} \;
find /var/www -type f -exec sudo chmod 0664 {} \;
]
Create HTML file:
echo "ejamuna!" > /var/www/ejamuna.com/index.php
or
sudo vi /var/www/ejamuna.com/j.php
<h1>eJamuna!</h1>
<?php
phpinfo();
?>
If you want to change Apache to serve PHP files rather than others, move index.php to first position in the dir.conf file as shown below:
sudo vi /etc/apache2/mods-enabled/dir.conf
Apache needs a virtual host file to serve the contents of your domain from the server.
sudo vi /etc/apache2/sites-available/ejamuna.com.conf
<VirtualHost *:80> ServerAdmin webmaster@ejamuna.com ServerName ejamuna.com ServerAlias www.ejamuna.com DocumentRoot /var/www/ejamuna.com #ProxyPass / http://localhost:3000/ #ProxyPassReverse / http://localhost:3000/ <Directory "/var/www/ejamuna.com"> AllowOverride All </Directory> <FilesMatch \.php$> SetHandler "proxy:unix:/var/run/php/php7.4-fpm.sock|fcgi://localhost/" </FilesMatch> ErrorLog ${APACHE_LOG_DIR}/ejamuna.com-error.log CustomLog ${APACHE_LOG_DIR}/ejamuna.com-access.log combined </VirtualHost>
Test for errors:
sudo apache2ctl configtest
Enable the domain configuration file:
sudo a2ensite ejamuna.com.conf
a2ensite 000-default.conf a2ensite default-ssl.conf
To disable a website:
sudo a2dissite 000-default.conf sudo systemctl reload apache2 sudo service apache2 reload
Handy codes:
sudo mkdir /var/www/ejamuna.com sudo chown -R <www-data>:www-data /var/www/ejamuna.com
SSL
Update Your System–Frequently
sudo apt update && sudo apt upgrade -y
Install Certbot Apache on Ubuntu 20.04
sudo apt-get update sudo apt-get install software-properties-common sudo add-apt-repository universe sudo apt-get update
sudo apt-get install certbot python3-certbot-apache
Version (24 Jun, 2020)
certbot --version
My version of certbot was 0.40.0
Get a certificate with Route 53 plugin
Install correct DNS plugin
-sudo apt install python3-certbot-dns-<PLUGIN> sudo apt install python3-certbot-dns-route53
Manual
The access keys for an account with these permissions must be supplied in one of the following ways, which are discussed in more detail in the Boto3 library’s documentation about configuring credentials.
Examples:
certbot certonly \ --dns-route53 \ --dns-route53-propagation-seconds 30 \ -d example.com \ -d www.example.com
Install certificate Manually( without Plugins)
Generate Strong Dh (Diffie-Hellman) Groupsudo openssl dhparam -out /etc/ssl/certs/dhparam.pem 2048
Obtaining a Let’s Encrypt SSL certificatesudo vi /etc/apache2/conf-available/letsencrypt.conf
Alias /.well-known/acme-challenge/ "/var/lib/letsencrypt/.well-known/acme-challenge/" <Directory "/var/lib/letsencrypt/"> AllowOverride None Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec Require method GET POST OPTIONS </Directory>
sudo vi /etc/apache2/conf-available/ssl-params.conf
# SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH SSLCipherSuite ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:\ ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA256:\ ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:\ ECDHE-RSA-AES128-SHA:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA256:\ ECDHE-RSA-AES256-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:\ DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA256
SSLProtocol All -SSLv2 -SSLv3 -TLSv1 -TLSv1.1 SSLHonorCipherOrder On
# Header always set Strict-Transport-Security "max-age=63072000; includeSubDomains; preload" Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" Header always set X-Frame-Options DENY Header always set X-Content-Type-Options nosniff
# Requires Apache >= 2.4 SSLCompression off # Requires Apache >= 2.4.11 SSLSessionTickets Off
# Activate OCSP stapling on Apache 2.4+ # https://www.tbs-certificates.co.uk/FAQ/en/active-ocsp-apache.html # SSLUseStapling on # SSLStaplingCache "shmcb:logs/stapling_cache(128000)"
SSLStaplingCache shmcb:/var/tmp/ocsp-stapling-cache/cache(128000000) SSLUseStapling on SSLStaplingResponderTimeout 2 SSLStaplingReturnResponderErrors off SSLStaplingFakeTryLater off SSLStaplingStandardCacheTimeout 86400 # https://www.tbs-certificates.co.uk/FAQ/en/install-cert-ssl-apache-2-4-8.html SSLOpenSSLConfCmd DHParameters "/etc/ssl/certs/dhparam.pem" SSLOpenSSLConfCmd ECDHParameters secp384r1
# https://httpd.apache.org/docs/current/mod/mod_ssl.html SSLOptions +StrictRequire
# Add vhost name to log entries:
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" vhost_combined
LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost_common
Test for errors:
sudo apache2ctl configtest
Enable these mods:
sudo a2enmod ssl headers
Enable these scripts:
sudo a2enconf letsencrypt ssl-params
Enable these mods:
sudo a2enmod http2 rewrite
Reload Apache2:
sudo systemctl reload apache2 (conf) sudo systemctl restart apache2 (mod) sudo service apache2 reload
Apache Status checking:
sudo systemctl status apache2
sudo mkdir -p /var/lib/letsencrypt/ sudo chgrp www-data /var/lib/letsencrypt sudo chmod g+s /var/lib/letsencrypt sudo mkdir -p /var/lib/letsencrypt/.well-known/acme-challenge/ sudo chmod -R 775 /var/lib/letsencryptTesting the setup:sudo gpasswd -a tommy_user javagroup (add user to a group) sudo echo -n "Testing acme-challenge" > /var/lib/letsencrypt/.well-known/acme-challenge/test sudo curl -ikL http://www.ejamuna.com/.well-known/acme-challenge/testSetting directories with g+s makes all new files created in the said directory have their group set to the directory's group. When used on a directory, instead, the setgid bit alters the standard behaviour so that the group of the files created inside said directory, will not be that of the user who created them, but that of the parent directory itself. This is often used to ease the sharing of files (files will be modifiable by all the users that are part of said group).This can actually be really handy for collaborative purposes if you have the umask set so that files have group write by default.
Obtain the certificate
Getting a certificate:
Ref: Example 1:
Ref: Example 2:
certbot certonly \ -d example.com \ -d *.example.com \ --dns-route53 \ --logs-dir /home/username/letsencrypt/log/ \ --config-dir /home/username/letsencrypt/config/ \ --work-dir /home/username/letsencrypt/work/ \ -m email@example.com \ --agree-tos \ --server https://acme-v02.api.letsencrypt.org/directory
Renew example:
certbot renew --dns-route53 \ --logs-dir /home/username/letsencrypt/log/ \ --config-dir /home/username/letsencrypt/config/ \ --work-dir /home/username/letsencrypt/work/ \ --server https://acme-v02.api.letsencrypt.org/directory \ --post-hook "sudo service nginx reload"
dns-route53 plugin: certbot website
sudo certbot certonly \ -i apache \ --dns-route53 \ --dns-route53-propagation-seconds 30 \ -d dumbschool.com \ -d www.dumbschool.com \ --agree-tos \ --email bdjunayed@gmail.com
Webroot: authenticator plugin (Single domain)
sudo certbot certonly \ -i apache \ -a webroot \-w /var/www/haanz.online/ \-w /var/lib/letsencrypt/ \ -d haanz.online \ -d www.haanz.online \ --email bdjunayed@gmail.com \ --agree-tos \ --server https://acme-v02.api.letsencrypt.org/directory
Webroot: authenticator plugin (to obtain a single certificate for multiple domains)
To use the webroot plugin, your server must be configured to serve files from /.well-known
sudo certbot certonly \ --webroot \ -w /var/www/d1.com \ -d d1.com \ -w /var/www/d2.com \ -d d2.com --agree-tos \ --email bdjunayed@gmail.com \
Manual: kind of webroot plugin but manual.
sudo certbot certonly \ --preferred-challenges=dns \ --manual -d example.com \ -d www.example.com \
Manual: (CrazyDomain don't allow the TXT record)
sudo certbot certonly \ --preferred-challenges=http \ --manual \ -d saustralasia.online \ -d www.saustralasia.online \ --email bdjunayed@gmail.com \ --agree-tos \ --server https://acme-v02.api.letsencrypt.org/directory
Successful output sample:
Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator webroot, Installer None Cert not yet due for renewal You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry. (ref: /etc/letsencrypt/renewal/saustralasia.online.conf) What would you like to do? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1: Keep the existing certificate for now 2: Renew & replace the cert (limit ~5 per 7 days) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2 Renewing an existing certificate IMPORTANT NOTES: - Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/saustralasia.online/fullchain.pem Your key file has been saved at: /etc/letsencrypt/live/saustralasia.online/privkey.pem Your cert will expire on 2020-03-30. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run "certbot renew" - If you like Certbot, please consider supporting our work by: Donating to ISRG / Let's Encrypt: https://letsencrypt.org/donate Donating to EFF: https://eff.org/donate-le root@node1:~#
Now, you have the certificate files, edit your domain virtual host configuration as follows:
sudo vi /etc/apache2/sites-available/ejamuna.com.conf
<VirtualHost *:80>
ServerAdmin admin@ejamuna.com
ServerName ejamuna.com
ServerAlias www.ejamuna.com
DocumentRoot /var/www/ejamuna.com/pub
<Directory /var/www/ejamuna.com>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
Allow from all
</Directory> #ProxyPass / http://localhost:3000/
#ProxyPassReverse / http://localhost:3000/
<FilesMatch \.php$>
SetHandler "proxy:unix:/var/run/php/php7.4-fpm.sock|fcgi://localhost/"
</FilesMatch> ErrorLog ${APACHE_LOG_DIR}/ejamuna.com-error.log
CustomLog ${APACHE_LOG_DIR}/ejamuna.com-access.log combined
#Redirect permanent / https://ejamuna.com/
RewriteEngine on
RewriteCond %{SERVER_NAME} =www.ejamuna.com [OR]
RewriteCond %{SERVER_NAME} =ejamuna.com
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>
<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerName ejamuna.com
ServerAlias www.ejamuna.com
ServerAdmin admin@ejamuna.com
Protocols h2 http:/1.1
#<If "%{HTTP_HOST} == 'www.ejamuna.com'">
# Redirect permanent / https://ejamuna.com/
#</If>
DocumentRoot /var/www/ejamuna.com/pub
# Apache 2.4 If you are not the administrator of the server, you depend
# on the AllowOverride Level that theses admins allows for you.
<Directory /var/www/ejamuna.com>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
Allow from all
</Directory>
#ProxyPass / http://localhost:3000/
#ProxyPassReverse / http://localhost:3000/
<FilesMatch \.php$>
SetHandler "proxy:unix:/var/run/php/php7.4-fpm.sock|fcgi://localhost/"
</FilesMatch> # Allow encoded slashes
AllowEncodedSlashes NoDecode ErrorLog ${APACHE_LOG_DIR}/ejamuna.com-error.log
CustomLog ${APACHE_LOG_DIR}/ejamuna.com-access.log combined
# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf
SSLEngine On
# Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/ejamuna.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/ejamuna.com/privkey.pem
# SSLCertificateChainFile /etc/letsencrypt/live/saustralasia.online/chain.pem (Obsolute)
Header always set Strict-Transport-Security "max-age=31536000"
Header always set Content-Security-Policy upgrade-insecure-requests
</VirtualHost>
</IfModule>
Test for errors:
sudo apache2ctl configtest
Reload Apache2 for conf:
sudo service apache2 reload
Test your certificate:
Auto-renewing Let’s Encrypt SSL certificate
Ref: Certbot documentation
Let’s Encrypt’s certificates are valid for 90 days. To automatically renew the certificates before they expire, the certbot package creates a cronjob which runs twice a day and will automatically renew any certificate 30 days before its expiration.
Let’s Encrypt’s certificates are valid for 90 days. To automatically renew the certificates before they expire, the certbot package creates a cronjob which runs twice a day and will automatically renew any certificate 30 days before its expiration.
FIY, it will dry-run for all the domains already added.
Once the certificate is renewed we also have to reload the Apache service. Append --renew-hook "systemctl reload apache2" to the /etc/cron.d/certbot file so that it looks like the following:
sudo vi /etc/cron.d/certbot 0 */12 * * * root test -x /usr/bin/certbot -a \! -d /run/systemd/system && perl -e 'sleep int(rand(3600))' && certbot -q renew --renew-hook "systemctl reload apache2"
--renew-hook "systemctl reload apache2"
Test automatic renewal:
sudo certbot renew --dry-run
Delete cert:
sudo certbot delete --cert-name dumbschool.com
List cert:
sudo certbot certificates
Certbot troubleshoots:
grep -r 443 /etc/apache2
If there are no errors, it means that the renewal process was successful! Or visit: Check DNS, Urls + Redirects, Certificates and Content of your Website
Dismental a site:
sudo apache2ctl configtest
sudo certbot certificates
sudo certbot delete --cert-name saustralasia.online
sudo a2dissite saustralasia.online.conf
sudo service apache2 reload
sudo service apache2 status
Installing Composer
Prerequisite: Php
Installing Globally
Ref: Composer.org Doc
Ref: Composer download
Run as a sudo user
sudo php -r "copy('https://getcomposer.org/installer', 'composer-setup.php');" sudo php -r "if (hash_file('sha384', 'composer-setup.php') === 'e0012edf3e80b6978849f5eff0d4b4e4c79ff1609dd1e613307e16318854d24ae64f26d17af3ef0bf7cfb710ca74755a') { echo 'Installer verified'; } else { echo 'Installer corrupt'; unlink('composer-setup.php'); } echo PHP_EOL;" sudo php composer-setup.php sudo php -r "unlink('composer-setup.php');"
sudo mv ~/composer.phar /usr/local/bin/composer or sudo mv composer.phar /usr/local/bin/composer or mg@node1:~$ sudo mkdir -p ~/bin/composer mg@node1:~$ sudo mv composer.phar ~/bin/composer/
sudo vi ~/.bashrc alias composer='/home/mg/bin/composer/composer.phar'
For Local changes:
source ~/.bashrc
For Global Changes:
sudo vi /etc/bash.bashrc
To update Composer itself
/usr/local/bin/composer/composer.phar self-update
Uninstall composer?
Changing your PATH
Check the current path settings:
mg@node1:~$ echo $PATH
Simply add /place/with/the/file to the $PATH variable with the following command:
export PATH=$PATH:/place/with/the/file
Check which shell is running
echo $0
Set your PATH permanently
A file called ~/.bash_profile, ~/.bashrc, or ~/.profile. ~/.bashrc is a good choice.
#added to set the PATH PATH=$PATH:/home/mg/composer.phar
To test your path, run
composer --version
See these also (if not required):
The COMPOSER_HOME var allows you to change the Composer home directory. This is a hidden, global (per-user on the machine) directory that is shared between all projects.
echo $COMPOSER_HOME echo $COMPOSER_BIN_DIR
Magento 2.4
Elasticsearch - Ubuntu 20
Java runtime is required for the Elasticsearch.
Install Java
java -version sudo apt update && sudo apt upgrade -y apt search openjdk sudo apt install default-jre sudo apt install openjdk-11-jre-headless sudo apt install openjdk-11-jdk-headless sudo apt install openjdk-14-jre-headless sudo apt install openjdk-14-jdk-headless java -version javac -version
Java Environment setup
sudo vi /etc/bash.bashrc # At the end export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64/ export PATH=$PATH:$JAVA_HOME/bin
Uninstall Elasticsearch
You need to setup global config in /etc/profile OR /etc/bash.bashrc file for all users:
sudo vi /etc/bash.bashrc
Installing Elasticsearch ref1
sudo apt-get install apt-transport-https
Download and install the Debian package manually
wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.7.1-amd64.deb wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.7.1-amd64.deb.sha512 shasum -a 512 -c elasticsearch-7.7.1-amd64.deb.sha512 sudo dpkg -i elasticsearch-7.7.1-amd64.deb
Elasticsearch is not started automatically after installation. How to start and stop Elasticsearch depends on whether your system uses SysV init or systemd (used by newer distributions). You can tell which is being used by running this command:
ps -p 1
Running Elasticsearch with systemd
To configure Elasticsearch to start automatically when the system boots up, run the following commands:
sudo /bin/systemctl daemon-reload sudo /bin/systemctl enable elasticsearch.service
Elasticsearch can be started and stopped as follows:
sudo systemctl stop elasticsearch.service sudo systemctl start elasticsearch.service sudo systemctl status elasticsearch.service sudo systemctl restart elasticsearch
These commands provide no feedback as to whether Elasticsearch was started successfully or not. Instead, this information will be written in the log files located in /var/log/elasticsearch/.
Elasticsearch loads its configuration from the /etc/elasticsearch/elasticsearch.yml file by default. The format of this config file is explained in Configuring Elasticsearch.
sudo vi /etc/elasticsearch/elasticsearch.yml
Test the Elasticsearch working: (no need to open port 9200)
curl -XGET http://localhost:9200/
To verify that Elasticsearch is working, enter the following command on the server on which it is running:curl -XGET '<host>:9200/_cat/health?v&pretty'curl -XGET 'localhost:9200/_cat/health?v&pretty'
Set up a proxy for Apache 2.4
This section discusses how to configure an Elasticsearch proxy using a virtual host.
Enable mod_proxy as follows:
a2enmod proxy_http
Use a text editor to open /etc/apache2/sites-available/000-default.conf
Add the following directive at the top of the file:
Listen 8080
Add the following at the bottom of the file:
<VirtualHost *:8080> ProxyPass "/" "http://localhost:9200/" ProxyPassReverse "/" "http://localhost:9200/" </VirtualHost>
Test config and Restart Apache:
sudo apache2ctl configtest sudo service apache2 reload
Verify the proxy works by entering the following command:
curl -i http://localhost:<proxy port>/_cluster/health
For example, if your proxy uses port 8080:
curl -i http://localhost:8080/_cluster/health
Messages similar to the following display to indicate success:
HTTP/1.1 200 OK
Date: Tue, 23 Feb 2016 20:38:03 GMT
Content-Type: application/json; charset=UTF-8
Content-Length: 389
Connection: keep-alive
{"cluster_name":"elasticsearch","status":"yellow","timed_out":false,"number_of_nodes":1,"number_of_data_nodes":1,"active_primary_shards":5,"active_shards":5,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":5,"delayed_unassigned_shards":0,"number_of_pending_tasks":0,"number_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":0,"active_shards_percent_as_number":50.0}
Configure Magento 2 Elasticsearch
Reindexing catalog search and refreshing the full page cache.
After you change Magento’s Elasticsearch configuration, you must reindex the catalog search index and refresh the full page cache using the Admin or command line.
bin/magento cache:clean bin/magento indexer:reindex catalogsearch_fulltext bin/magento indexer:reindex
Wait until reindexing completes.
Unlike the cache, indexers are updated by a cron job. Make sure cron is enabled before you start using Elasticsearch.
Secure communication with Apache
Step 1: Create a password
which htpasswd /usr/bin/htpasswdIf a path displays, it is installed; if the command returns no output, htpasswd is not installed.
If necessary, install htpasswd:
Ubuntu: apt-get -y install apache2-utilsCreate a password file(http://httpd.apache.org/docs/2.4/howto/auth.html)
sudo mkdir -p /usr/local/apache/password
Example 2: Elasticsearch You must set up authentication for two users: one with access to Nginx and one with access to Elasticsearch. To create password files for these users, enter the following commands:
mkdir -p /usr/local/apache/password htpasswd -c /usr/local/apache/password/.<password file name> <username> sudo htpasswd -c /usr/local/apache/password/.htpasswd_elasticsearch haanz_online sudo htpasswd /usr/local/apache/password/.htpasswd_elasticsearch ejamuna_com
Add additional users: To add another user to your password file, enter the following command as a user with root privileges:
Use a text editor to add the following contents to your secure virtual host.
Apache 2.4:
curl -i http://<hostname, ip, or localhost>:<proxy port>/_cluster/health
For example, if you enter the command on the Elasticsearch server and your proxy uses port 8080:
htpasswd /usr/local/apache/password/.htpasswd <username> sudo htpasswd /usr/local/apache/password/.htpasswd_elasticsearch mg
Step 2: Secure communication with Apache
This section discusses how to specify who can access the Apache server.Use a text editor to add the following contents to your secure virtual host.
Apache 2.4:
sudo vi /etc/apache2/sites-available/000-default.conf
Listen 8080
<VirtualHost *:8080>
ProxyPass "/" "http://localhost:9200/"
ProxyPassReverse "/" "http://localhost:9200/"
</VirtualHost>
<Proxy "*">
Order deny,allow
Allow from all
AuthType Basic
AuthName "Elastic Server"
AuthBasicProvider file
AuthUserFile /usr/local/apache/password/.htpasswd_elasticsearch
Require valid-user
# This allows OPTIONS-requests without authorization
<LimitExcept OPTIONS>
Require valid-user
</LimitExcept>
</Proxy>
<VirtualHost *:80>...Verify communication is secure
Test config and Restart Apache:
sudo apache2ctl configtest
sudo service apache2 reloadUse a curl command to verify cluster status
curl -i http://<hostname, ip, or localhost>:<proxy port>/_cluster/health
For example, if you enter the command on the Elasticsearch server and your proxy uses port 8080:
curl -i http://localhost:8080/_cluster/healthThe following message displays to indicate authentication failed:
HTTP/1.1 401 Unauthorized Date: Tue, 23 Feb 2016 20:35:29 GMT Content-Type: text/html Content-Length: 194 Connection: keep-alive WWW-Authenticate: Basic realm="Restricted"Now try the following command:
curl -i -u <username>:<password> http://<hostname, ip, or localhost>:<proxy port>/_cluster/health curl -i -u magento_elasticsearch:mypassword http://localhost:8080/_cluster/health curl -i -u gcrecruitment_site:55Uu*^ http://localhost:8080/_cluster/health
HTTP/1.1 200 OK
Date: Thu, 18 Jun 2020 07:10:49 GMT
Server: Apache/2.4.29 (Ubuntu)
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
content-type: application/json; charset=UTF-8
content-length: 389
{"cluster_name":"elasticsearch","status":"yellow","timed_out":false,"number_of_nodes":1,"number_of_data_nodes":1,"active_primary_shards":1,"active_shards":1,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":1,"delayed_unassigned_shards":0,"number_of_pending_tasks":0,"number_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":
Perform the same tasks as discussed in Configure Magento to use Elasticsearch
Subscribe to:
Posts (Atom)