Key factors.

• Open Ports.
• Insecure or non-updated software.
• Weak passwords policy.
• Attacks on administrator accounts.
• Lack of physical securities.

Open Ports.

Ports scanning is the first thing that any Attacker would do before attacking your servers. They could get an idea of which service can be compromised based upon open ports. There are multiple methods to scan and identify open ports Nmap is one of them.

# apt install nmap
# yum install nmap

Insecure or non-updated software

If you are not updating the server regularly, attackers can gain access via using exploits. Misconfigures services can be harmful too. Always make sure to keep Operating System updated. Multiple tools are available to test vulnerabilities. OpenVAS is one of the famous tool that can be installed on the server to scan vulnurabitiels.

Install OpenVAS

#apt install openvas
#yum install openvas

Start Service.

# openvas-start && openvas-setup

Login to get reports.

Weak passwords policy

Using a tool like hydra attackers can gain access if your system is set up with weak passwords and have unwanted ports open. Always use complicated passwords and keeping them changing from time to time can reduce the chances of attacks. Let’s take a look at how hydra can be used to target servers with weak passwords. create a list of usernames and passwords with all possible combinations (userlist.txt & passwd.txt are created in my scenario).

# apt install hydra

Run command.

# hydra -L /root/userlist.txt -p /root/passwd.txt -u 127.0.0.1 ssh

Attacks on administrator accounts

Remember, if an attacker can gain access to an administrator account. An attacker can gain access to other servers as well. Even after having to have good securities, the hackers were able to gain access. Always make sure not to share passwords with unauthorized persons.

Lack of physical securities

Proving multi-factor authentications, providing physical locks can save servers from unwanted access. Do not provide any direct physical access like monitors or keyboards. Block all USB or other serial ports that can be attached directly to servers. No media file sharing has to be with critical operational servers.

Conclusion.

Today, we have learned how an attacker can gain easy access to servers & how to avoid it. Scanning ports with Nmap, system’s health check with OpenVAS are part of security assessment. In the next article, we will understand other aspects of security.

The post How to master Linux Server Securities appeared first on Linux Windows and android Tutorials.

UVdesk offers SaaS-based and Open Source helpdesk solution to easier the overall support process to deliver best customer service. All this information can be found on the project’s website.

Install UDVesk on Ubuntu 20.04

1.- Install some required packages

Before starting the whole installation process we have to install some necessary packages.

To do this, open a terminal or start an SSH session on your server and run:

sudo apt update
sudo apt upgrade

Then it installs the necessary packages I referred to. Among them, GIT, Apache, and some modules of the latter.

sudo apt install git unzip apache2 libapache2-mod-fcgid

Then enable the Apache modules needed to perform the installation.

sudo a2enmod actions fcgid alias proxy_fcgi rewrite

And apply the changes by restarting Apache.

sudo systemctl restart apache2

2.- Preparing MariaDB for UVDesk

The next step is to install and configure correctly MariaDB, for this we have a post where it is explained in detail

How To Install MariaDB on Ubuntu 20.04?

After MariaDB is installed and configured, you have to create the database and the user so that UVDesk can work with it.

Open the MariaDB shell:

sudo mysql -u root -p

And then create the database, as well as the user with their permissions.

sudo mysql -u root -p
CREATE YOUR DATABASE uvdeskdb;
GRANT ALL PRIVILEGES ON uvdeskdb . * TO 'uvuser'@'localhost' IDENTIFIED BY 'uvpps';
FLUSH PRIVILEGES;
exit;

So, now we can continue.

3.- Install and configure PHP for UVDesk

Now the next step is to install PHP along with some of its modules:

sudo apt install php-cli php-fpm php-pdo php-json php-common php-mysql php-zip php-gd php-mbstring php-curl php-xml php-bcmath php-imap php-intl php-mailparse php-pear

And it is advisable to make some changes in the configuration of PHP to adapt it to UVDesk.

Open the PHP configuration file

sudo nano /etc/php/7.4/fpm/php.ini

And with the help of the key combination CTRL + W look for the parameter memory_limit and assign another higher value to it.

memory_limit = 256M

You can also change the Timezone of PHP to your location.

Save the changes and close the editor.

4.- Install UVDesk on Ubuntu 20.04

The installation of UVDesk is through Composer, so we have to install it first.

Download it with the curl command:

curl -sS https://getcomposer.org/installer -o composer-setup.php

And then install it with this command:

sudo php composer-setup.php --install-dir=/usr/local/bin --filename=composer --version=1.10.17

You can check the status of Composer, by running

composer -V

Now it’s time to create the folder where UVDesk will be and assign it as the owner of the current user:

sudo mkdir /var/www/udvesk
sudo chown -R $USER:$USER /var/www/

And now start the installation with Composer from the created folder.

cd /var/www/udvesk
composer clear-cache
composer create-project uvdesk/community-skeleton helpdesk-project

If the whole process has gone well, you will see a screen output similar to this one:

Now you need to create a new Virtualhost for the application:

sudo nano /etc/apache2/sites-enabled/uvdesk.conf

And add the following content

Listen 8080
<VirtualHost *:8080>
ServerName uvdesk.osradar.test
DocumentRoot /var/www/udvesk/helpdesk-project/public

<Directory /var/www/udvesk/helpdesk-project/public>
    Options -Indexes +FollowSymLinks +MultiViews
    AllowOverride All
    Require all granted
</Directory>

<FilesMatch \.php$>
    # 2.4.10+ can proxy to unix socket
    SetHandler "proxy:unix:/var/run/php/php7.4-fpm.sock|fcgi://localhost"
</FilesMatch>

ErrorLog /var/log/apache2/uvdesk-error.log
CustomLog /var/log/apache2/uvdesk-access.log combined
</VirtualHost>

Replace ServerName with yours. And save the changes.

Then update the permissions and make Apache the new owner of the UVDesk folder.

sudo chown -R www-data:www-data /var/www/udvesk
sudo chmod -R 755 /var/www/udvesk

And to apply all the changes, restart the service.

sudo systemctl restart apache2

5.- Complete the installation using the web interface

So, open your web browser and go to http://your-server:8080 and you will see the welcome screen

The installer will then perform a system check and if you meet all the requirements, you will see the following screen.

Then, it’s time to set up the parameters of the database that we have previously created. Set yours.

After this, it’s time to create the administrator user.

Then you can configure the website. You can leave it as it is or you can modify the values by which you think convenient.

Finally, you will see the screen where you can start the installation.

If everything goes well, you will see the following screen. There you have the links to the Front-end and the Admin Panel.

This is what the frontend looks like

And so the login screen

When you log in you will see the administration screen.

So enjoy it.

Conclusion

The open-source is gaining more and more ground in the business environment where applications such as UVDesk are becoming impractical for many organizations worldwide.

So, enjoy it.

The post How to install UVDesk on Ubuntu 20.04? appeared first on Linux Windows and android Tutorials.

According to Wikipedia:

“GLPI is an open source IT Asset Management, issue tracking system and service desk system (..) The solution is able to build an inventory of all the organization’s assets and to manage administrative and financial tasks”

It is open source because it is released under the GPLv2 license which makes it accessible to many. Moreover, it is perfectly compatible with many operating systems.

So, let us start the job.

Install GLPI on Ubuntu 20.04

1.- Install LAMP on Ubuntu 20.04

One of the main advantages of using and installing GLPI is that it is a web application, and is therefore compatible with many operating systems. Also, the installation is not complicated at all, but it requires that the LAMP stack is installed and working on the server.

So let’s get to work on this first.

How to install LAMP on Ubuntu 20.04?

Also, you have to install other PHP modules that become necessary. These are all of them:

php7.4 php7.4-curl php7.4-zip php7.4-gd php7.4-intl php-pear php7.4-imagick php7.4-imap php-memcache php7.4-pspell php7. 4-tidy php7.4-xmlrpc php7.4-xsl php7.4-mb php7.4-ldap php-cas php-apcu libapache2-mod-php7.4 php7.4-mysql

Once it is installed and correctly configured we can move on to GLPI.

2.- Creating the new user and database for GLPI

With MariaDB already working properly, we now have to create a new user and a new database.

The main reason for this is that GLPI needs to store different data and it is convenient that the root user is not the user that GLPI is going to use. This is for security reasons.

So, open the MariaDB console as the root user:

:~$ sudo mysql -u root -p

And then, create the database, the new user together with the privileges over the new database.

> CREATE DATABASE glpidb;
>GRANT ALL PRIVILEGES ON glpidb.* TO 'glpiuser'@'localhost' IDENTIFIED BY 'password';
> FLUSH PRIVILEGES;
>EXIT;

Remember that you can change the values set here to your own. Above all, the password has to be a strong one and must be safe.

3.- Download GLPI on Ubuntu 20.04

So, it’s time to download GLPI using the wget command. This will make the download faster and we’ll still be in a CLI environment.

Navigate to the /tmp/ folder and download it from there.

:~$ cd /tmp/
:~$ wget -c https://github.com/glpi-project/glpi/releases/download/9.4.5/glpi-9.4.5.tgz

Once the download is complete, decompress the file with the tar command.

:~$ tar -xvf glpi-9.4.5.tgz

Then, move it to the Apache root folder in Ubuntu and assign the correct permissions.

:~$ sudo mv glpi /var/www/html/
:~$ sudo chmod 755 -R /var/www/html/

And to make sure Apache has no problem running all GLPI, make Apache the owner of the folder.

:~$ sudo chown www-data:www-data -R /var/www/html/

After this, create a new Virtualhost for GLPI.

:~$ sudo nano /etc/apache2/sites-available/glpi.conf

And add the following content to the file:

<VirtualHost *:80>
   ServerAdmin admin@your_domain.com
   DocumentRoot /var/www/html/glpi
   ServerName your-domain.com

   <Directory /var/www/html/glpi>
        Options FollowSymlinks
        AllowOverride All
        Require all granted
   </Directory>

   ErrorLog ${APACHE_LOG_DIR}/your-domain.com_error.log
   CustomLog ${APACHE_LOG_DIR}/your-domain.com_access.log combined

</VirtualHost>

Replace the value “your-domain” with your own. You are also free to add new rules for this Virtualhost.

Then save the changes and close the text editor.

To enable the new Virtualhost, simply make a symbolic link from the file to the Apache-enabled sites.

:~$ sudo ln -s /etc/apache2/sites-available/glpi.conf /etc/apache2/sites-enabled/glpi.conf

Then, enable Apache’s rewrite module and apply the changes by restarting Apache.

:~$ sudo a2enmod rewrite
:~$ sudo systemctl restart apache2

Now to complete the installation.

4.- Install GLPI on Ubuntu 20.04

Now open a web browser and go to http://your-domain and you will see the following screen where you can choose the installation language:

Then, you will have to accept the license terms:

In the next screen, you will have to specify if it is a new installation or an upgrade. In this case, it is a new installation:

Then, the wizard will verify that the server meets all the requirements.

Now you will see the first step of the installation which is to configure the database credentiials. Just type the previously created credentials:

Then, select the database created and continue the process:

If the installer manages to connect to the database, you will be informed on this screen:

GLPI is an open-source and improved by the community. Therefore you will be asked if you want to anonymously send statistics to the developers:

Then, on the next screen, you will be informed that the installation was successful and you will see the default credentials for each GLPI role. Remember that you can change this.

In the end, you will see the Login screen where you will enter the necessary credentials:

Finally, you will see the main screen of the application and it will be ready for work.

So, enjoy it.

Conclusion

GLPI is an application to control the informatics equipment of your company. It is an administrative tool, more than anything. It is created in PHP and uses MariaDB as a database manager.

We are talking about a solid tool used by many organizations worldwide. Free is not a problem for small projects but it is solid enough to be used in larger ones

Please share this post and join our Telegram channel.

The post How to install GLPI on Ubuntu 20.04? appeared first on Linux Windows and android Tutorials.

Introducing XCart

Xcart is an open-source application that allows you to intuitively create an online store. Not only creating it but also managing it. Xcart has a free version that is quite basic but can serve as an instruction to the application or if the store is quite small; it also has paid versions with many more advantages.

Thanks to Xcart you can create and manage an online store quickly. It was the first application of this type and the initial version is from 2000. This indicates the experience and maturity of the project and a well-earned reputation.

With Xcart you have all the features you need to achieve your goals, with a carefully designed interface, integration with multiple providers, themes to customize the store and a panel to manage it.

So let’s start installing XCart on Debian 10.

Install XCart on Debian 10

As with the vast majority of content site generators such as WordPress or prestashop, Xcart is built with web technologies. This means that you have to install a web server and PHP. In addition, for data manipulation, it requires MariaDB or a similar database manager.

So, you have to install LAMP.

How to install LAMP on Debian 10?

Also, you have to include the following PHP modules:

php php-cli libapache2-mod-php php-common php-mbstring php-curl php-mysql php-json php-xml php-phar php-pdo php-gd

Then you can continue.

Create a new database for MariaDB

The next step is to create a new database for Xcart to store the generated data.

:~$ sudo mysql -u root -p
> CREATE YOUR DATABASE xcartdb;
> GRANT ALL ON xcartdb.* TO 'xcartuser' IDENTIFIED BY 'xcartpss';
> FLUSH PRIVILEGES;
> exit;

So, continue.

Download XCart on Debian 10

Now we can really start the XCart download. To do this, use the wget command and do it from the /tmp folder

:~$ cd /tmp/
:~$ wget -c http://img.x-cart.com/software/a/2f8a9fdc-c1c8-4f4f-814e-bb7a3e4d3b72/x-cart-5.4.0.10-en.tgz

When the download is finished, you have to decompress the downloaded file but we will do it in the Apache root folder.

:~$ sudo tar xvzf x-cart-5.4.0.10-en.tgz -C /var/www/html/

It then assigns the appropriate permissions to the folder so that the server can run it correctly.

:~$ sudo chown -R www-data:www-data /var/www/html/xcart
:~$ sudo chmod -R 755 /var/www/html/xcart

Then, create a new Virtualhost for the XCart site.

:~$ sudo nano /etc/apache2/sites-available/xcart.conf

And add the following:

<VirtualHost *:80>
    ServerAdmin admin@your_domain.com
    DocumentRoot /var/www/html/xcart
    ServerName shop.osradar.lan

    <Directory /var/www/html/xcart>
         Options FollowSymlinks
         AllowOverride All
         Require all granted
    </Directory>       
ErrorLog ${APACHE_LOG_DIR}/shop.osradar.lan_error.log
CustomLog ${APACHE_LOG_DIR}/shop.osradar.lan_error.log
</VirtualHost>

Remember to change the value of ServerName to your own.

Then, enable the new VirtualHost and enable Apache’s rewrite module. Finally, restart the Apache service.

:~$ sudo ln -s /etc/apache2/sites-available/xcart.conf /etc/apache2/sites-enabled/xcart.conf
:~$ sudo a2enmod rewrite
:~$ sudo systemctl restart apache2

We will now complete the installation from the XCart web interface.

Install XCart on Debian 10

The next step is to open your favorite web browser and go to the server to complete the installation. In this case, it is shop.osradar.lan

You’ll see what follows:

Click on the Yes button to start the installation.

Then, you will see the license terms. Accept them to continue.

Then, create the administrator user account.

Next, the installer will verify all the requirements needed to perform the installation.

Then you have to enter the credentials of the database you have created.

Then, the installation will begin and you will see that everything has gone well.

For security reasons, execute the commands that the installer proposes.

:~$ chmod 755 /var/www/html/xcart/
:~$ chmod 755 /var/www/html/xcart/etc/
:~$ chmod 644 /var/www/html/xcart/etc/config.php

Then go to the administration panel but log in first.

And finally, you will see the dashboard.

So, that is it.

Conclusion

Deploying an online store can be very difficult but thanks to tools like Xcart it can be made a little easier. Something as easy as installing it on Debian 10 that you now know.

It remains for you to take advantage of the tool and learn more.

Please share this post and join our Telegram channel.

The post Install XCart on Debian 10 appeared first on Linux Windows and android Tutorials.

Cockpit we like very much. It’s just that it’s pretty complete and easy to use the tool. Beyond monitoring, it allows us to control a Linux server through a web interface. Great, isn’t it?

In order to be a program used by multiple teams working on a server is that Cockpit has been carefully designed. In addition, it is friendly enough for those new to Linux and useful for seasoned admins too.

As I mentioned before, the installation of Cockpit is really simple since it is included in the official repositories of many Linux distributions.

As expected many sysadmins are experts in the use of the terminal and therefore using Cockpit is perfectly compatible with it. There’s even an embedded terminal in Cockpit.

In short, we are talking about a necessary program to complement the administration of a server efficiently.

So, let us start.

Install Cockpit on Debian 10

Cockpit is included in the official Debian 10 repositories. So we only need to use the following command:

:~$ sudo apt update 
:~$ sudo apt install cockpit --install-recommends
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  cockpit-bridge cockpit-dashboard cockpit-networkmanager cockpit-packagekit cockpit-storaged cockpit-system cockpit-ws cracklib-runtime dirmngr dns-root-data
  dnsmasq-base dosfstools exfat-fuse exfat-utils exim4-base exim4-config exim4-daemon-light fuse gdisk glib-networking glib-networking-common glib-networking-services
  gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gsettings-desktop-schemas guile-2.2-libs libappstream4 libassuan0 libatasmart4
  libblockdev-crypto2 libblockdev-fs2 libblockdev-loop2 libblockdev-mdraid2 libblockdev-part-err2 libblockdev-part2 libblockdev-swap2 libblockdev-utils2 libblockdev2
  libbluetooth3 libbytesize1 libcrack2 libevent-2.1-6 libfribidi0 libgc1c2 libglib2.0-bin libgnutls-dane0 libgpgme11 libgsasl7 libgstreamer1.0-0 libjansson4
  libjson-glib-1.0-0 libjson-glib-1.0-common libksba8 libkyotocabinet16v5 liblzo2-2 libmailutils5 libmbim-glib4 libmbim-proxy libmm-glib0 libmpfr6 libndp0 libnm0
  libnpth0 libntfs-3g883 libntlm0 libpackagekit-glib2-18 libparted-fs-resize0 libparted2 libpcap0.8 libproxy1v5 libpwquality-common libpwquality-tools libpwquality1
  libpython2.7 libqmi-glib5 libqmi-proxy libssh-4 libstemmer0d libteamdctl0 libudisks2-0 libunbound8 libvolume-key1 mailutils mailutils-common mdadm modemmanager
  network-manager ntfs-3g packagekit packagekit-tools parted pinentry-curses ppp psmisc udisks2
Suggested packages:
  cockpit-doc cockpit-pcp cockpit-docker xdg-utils pinentry-gnome3 tor exim4-doc-html | exim4-doc-info eximon4 spf-tools-perl swaks parcimonie xloadimage scdaemon
  gstreamer1.0-tools libparted-dev libparted-i18n mailutils-mh mailutils-doc dracut-core libteam-utils appstream parted-doc pinentry-doc btrfs-progs f2fs-tools
  nilfs-tools reiserfsprogs xfsprogs udftools udisks2-bcache udisks2-btrfs udisks2-lvm2 udisks2-vdo udisks2-zram
The following NEW packages will be installed:
  cockpit cockpit-bridge cockpit-dashboard cockpit-networkmanager cockpit-packagekit cockpit-storaged cockpit-system cockpit-ws cracklib-runtime dirmngr dns-root-data
  dnsmasq-base dosfstools exfat-fuse exfat-utils exim4-base exim4-config exim4-daemon-light fuse gdisk glib-networking glib-networking-common glib-networking-services
  gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gsettings-desktop-schemas guile-2.2-libs libappstream4 libassuan0 libatasmart4
  libblockdev-crypto2 libblockdev-fs2 libblockdev-loop2 libblockdev-mdraid2 libblockdev-part-err2 libblockdev-part2 libblockdev-swap2 libblockdev-utils2 libblockdev2
  libbluetooth3 libbytesize1 libcrack2 libevent-2.1-6 libfribidi0 libgc1c2 libglib2.0-bin libgnutls-dane0 libgpgme11 libgsasl7 libgstreamer1.0-0 libjansson4
  libjson-glib-1.0-0 libjson-glib-1.0-common libksba8 libkyotocabinet16v5 liblzo2-2 libmailutils5 libmbim-glib4 libmbim-proxy libmm-glib0 libmpfr6 libndp0 libnm0
  libnpth0 libntfs-3g883 libntlm0 libpackagekit-glib2-18 libparted-fs-resize0 libparted2 libpcap0.8 libproxy1v5 libpwquality-common libpwquality-tools libpwquality1
  libpython2.7 libqmi-glib5 libqmi-proxy libssh-4 libstemmer0d libteamdctl0 libudisks2-0 libunbound8 libvolume-key1 mailutils mailutils-common mdadm modemmanager
  network-manager ntfs-3g packagekit packagekit-tools parted pinentry-curses ppp psmisc udisks2
0 upgraded, 103 newly installed, 0 to remove and 0 not upgraded.
Need to get 38.3 MB of archives.
After this operation, 138 MB of additional disk space will be used.
Do you want to continue? [Y/n

The second command not only installs Cockpit but also other recommended packages.

When the installation is finished, the service will be active and running.

And to access Cockpit, just use a current web browser and go to the following address:

https://your-server:9090

Make sure that the port is available on the firewall.

Then, you will see this.

Using cockpit

In that Log in screen, you only have to put your system credentials. Yes, the same ones you use to log in. If your user is in the sudo list you can check the option to reuse my password for privileged tasks. When you log in, you will see the following.

On the left side, you have all the driving options. For example, you can check the system logs:

In this case, there isn’t one in my system yet.

Then you can check the storage function.

A very useful function of Cockpit is the ability to monitor the state of the computer networks.

Also, managing system services such as postgreSQL, MariaDB or FTP are very easy thanks to Cockpit.

The sysadmin will appreciate that Cockpit includes a terminal ready to execute commands:

On the other hand, you can see the Cockpit dashboard there you will have information about the system resources.

So, enjoy this wonderfull tool.

Conclusion

Cockpit is one of those tools that works quite well and easily. That is, without complicated interfaces we can control a Linux server through a web interface. Now you know how to install it in Debian 10.

Please share this post and join our Telegram channel.

The post How to install Cockpit on Debian 10? appeared first on Linux Windows and android Tutorials.

VestaCP is a simple yet fantastic control panel hosting, but at the same time very intuitive and easy to use. It is used to manage user accounts, domains, web directories, FTP, Email, SSL Certificates, backups, etc.. VestaCP is very simple, but at the same time very intuitive and easy to use. You can install vestaCP on many GNU/LINUX distributions, especially those focused on servers, such as Debian or CentOS.

Main features of VestaCP

Despite being simple and intuitive, it is also a powerful tool with many utilities. VestaCP offers us:

• A very neat Web interface open source and written in PHP. So compatibility is guaranteed.
• Vesta core is written in bash. It is native programming language of Linux server administrators. You can execute 381 commands on Core.
• Its license is GNU GPL3. Its source code can be studied and modified
• A powerful CLI ready to give you control of what happens on the server.
• Commercial plugins extend the functionality of VestaCP.

As you can see, it’s a ready-to-use application for everyday work.

So, let us start.

Installing VestaCP on Ubuntu 18.04

First, update the system completely to have everything ready.

:~$ sudo apt update
:~$ sudo apt upgrade

VestaCP has a pretty competent installer that you have to download using curl.

:~$ curl -O http://vestacp.com/pub/vst-install.sh

Once you download it, you can run it with the following command:

:~$ sudo bash vst-install.sh

This will start the wizard.

The first thing it will ask you is your Email and the FQDN of the server.

Then, it will start the whole installation. Be patient, the installation will take a while.

Once the installation is finished and if everything has gone well, you will see the following information:

The image shows all the information you need to access VestaCP. Remember that if you are working in a local network without internet access, the internal IP address is the one you should type.

Also, you can customize the installer with many options that you can generate on this site.

Test VestaCP on Ubuntu 18.04

Now let’s access the tool. Open your favorite web browser and go to https://your-server:8083 and you will see the login screen.

Now type in the credentials that were generated earlier and you will see the VestaCP dashboard.

Now you can see all the information on the server. For example, it’s a good idea to check the graphics:

Or check the cron tasks:

So, enjoy it.

Conclusion

VestaCP is a control panel for Linux with many features that facilitate the administration of a server. So today you have learned to install it in a very simple way.

Please share this post and join our Telegram channel.

The post How to install VestaCP on Ubuntu 18.04? appeared first on Linux Windows and android Tutorials.

WildFly/JBoss is a Java Server used for the development of Java Projects and provides most of the features and being used by the Enterprises for its better performance & almost all features required. So mostly it is used by main Enterprises as compared to its competitors like Apache, Tomcat, Glassfish, Jetty. Other servers do not provides the all features needed but all of them provides most of the enterprise features. WildFly is the community edition & JBoss is the enterprise edition. JBoss is more secure but both are provided by Redhat Inc. So we recommend WildFly & we’re going to Install it on Our Ubuntu system today. So , follow the steps to proceed further.
First of all you must have installed Java.

java -version

Install WildFly 18 on Ubuntu 19.04

Download the WildFly 18 & choose the location to install it .

mkdir -p ~/sabi/servers
cd ~/sabi/servers
wget https://download.jboss.org/wildfly/18.0.1.Final/wildfly-18.0.1.Final.zip
unzip wildfly-18.0.1.Final.zip

Now add an admin to manage some sources (data sources).

cd wildfly-18.0.1.Final/bin/
./add-user.sh 

Fill the required details.

Now, start WildFly server instance in standalone as shown below:

$ ./standalone.sh
 JBoss Bootstrap Environment
 JBOSS_HOME: /home/sabi/sabi/servers/wildfly-18.0.1.Final
 JAVA: java
 JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true  --add-exports=java.base/sun.nio.ch=ALL-UNNAMED --add-exports=jdk.unsupported/sun.misc=ALL-UNNAMED --add-exports=jdk.unsupported/sun.reflect=ALL-UNNAMED
 =========================================================================
 22:16:09,321 INFO  org.jboss.modules JBoss Modules version 1.9.1.Final
 22:16:12,711 INFO  org.jboss.msc JBoss MSC version 1.4.11.Final
 22:16:12,775 INFO  org.jboss.threads JBoss Threads version 2.3.3.Final
 22:16:13,655 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 18.0.1.Final (WildFly Core 10.0.3.Final) starting
 22:16:24,470 INFO  [org.wildfly.security] (ServerService Thread Pool -- 28) ELY00001: WildFly Elytron version 1.10.4.Final
 22:16:29,899 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 22:16:30,156 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 9) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 22:16:30,795 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
 22:16:31,359 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.7.3.Final
 22:16:31,539 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.7.3.Final
 22:16:31,744 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 51) WFLYCLINF0001: Activating Infinispan subsystem.
 22:16:31,875 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 60) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
 22:16:31,934 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 63) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
 22:16:31,945 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 64) WFLYNAM0001: Activating Naming Subsystem
 22:16:32,121 INFO  [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 61) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
 22:16:32,449 INFO  [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 62) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
 22:16:32,110 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 52) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
 22:16:32,444 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 70) WFLYSEC0002: Activating Security Subsystem
 22:16:32,442 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 72) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
 22:16:32,707 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 58) WFLYJSF0007: Activated the following JSF Implementations: [main]
 22:16:32,760 INFO  [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.3.Final
 22:16:32,808 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 74) WFLYWS0002: Activating WebServices Extension
 22:16:32,803 INFO  [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.17.Final)
 22:16:33,440 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 43) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
 22:16:33,835 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 5.0.15.Final
 22:16:34,139 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 53) WFLYRS0016: RESTEasy version 3.9.1.Final
 22:16:34,343 INFO  [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
 22:16:34,347 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
 22:16:34,358 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
 22:16:34,802 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 2.0.27.Final starting
 22:16:35,888 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0014: Creating file handler for path '/home/sabi/sabi/servers/wildfly-18.0.1.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
 22:16:36,574 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 32 (per class), which is derived from thread worker pool sizing.
 22:16:36,574 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 8 (per class), which is derived from the number of CPUs on this host.
 22:16:37,074 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
 22:16:37,106 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
 22:16:37,366 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0493: EJB subsystem suspension complete
 22:16:37,590 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
 22:16:37,838 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
 22:16:39,388 INFO  [org.jboss.as.patching] (MSC service thread 1-2) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
 22:16:39,484 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /home/sabi/sabi/servers/wildfly-18.0.1.Final/standalone/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
 22:16:39,572 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory /home/sabi/sabi/servers/wildfly-18.0.1.Final/standalone/deployments
 22:16:40,643 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
 22:16:41,897 INFO  [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.3.0.Final (Apache CXF 3.3.3) 
 22:16:42,402 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
 22:16:42,418 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
 22:16:42,418 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
 22:16:42,419 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 18.0.1.Final (WildFly Core 10.0.3.Final) started in 35444ms - Started 315 of 577 services (369 services are lazy, passive or on-demand)

You can access the web management interface during the running of WildFly server by visiting http://localhost:9990/console. Provide the Authentication details to access Dashboard.

Now you can easily create, manage & configure datasources, deployments & server respectively.

Adding WildFly 18 to Eclipse IDE

Navigate to Help>Install New software..> Work with:

Add JBoss Tools Plugin

Name: JBoss Tools

Location: http://download.jboss.org/jbosstools/photon/development/updates/

Choose the feature you want to Install & click finish.

After it, restart and click on the server tab.

First time it will be blank with a link to create a new server. Click on the link and configure the server.

Choose WildFly 18 from the JBoss Community.

Click Next.

Set the Home directory of installed WildFly.

Click Finish.

Testing WildFly 18 to Eclipse IDE integration

For testing purposes create a simple project.

You’ll see that you’ve successfully created new project & the server is ready to use from now on your upcoming projects.

If have any queries regarding this tutorial, feel free to ask in comment section!

The post How To Install WildFly 18.0.1.Final & Connecting to Eclipse IDE on Ubuntu 19.04 appeared first on Linux Windows and android Tutorials.

Step 1: Install iscsi-initiator-utils on CentOS / RHEL 8.

sudo dnf -y install iscsi-initiator-utils

Step 2: Configure Initiator Name

Edit the file /etc/iscsi/initiatorname.iscsi/ and name it to match the target server name you’ve used.

sudo vi /etc/iscsi/initiatorname.iscsi

InitiatorName=iqn.2019-11.com.osradar:initiator01

Step 3: Configure Credentials

Open the following file to set up credential details.

sudo vi /etc/iscsi/iscsid.conf

Note: Use the credentials as you’ve done in setting up target so they match.

Uncomment "node.session.auth.authmethod=CHAP"
Uncomment "node.session.auth.username" and set username as "Initiator01"
Uncomment "node.session.auth.password" and set it as you've setup in previous setup.

Step 4: Testing iSCSI Target discovery

Run the following command to confirm that iSCSI can discover our installed iSCSI Target.

iscsiadm -m discovery -t sendtargets -p 172.17.52.184

Note: Use your iSCSI target server IP.

If the IP info and access details is displayed we can say the discovery is successful.

Step 5: Confirm Target’s status

Run the given command to check the status.

iscsiadm -m node -o show

# BEGIN RECORD 6.2.0.874-10  node.name = iqn.2019-11.osradar.com:target01  node.tpgt = 1  node.startup = automatic  node.leading_login = No  iface.hwaddress =   iface.ipaddress =   iface.iscsi_ifacename = default  iface.net_ifacename =   iface.gateway =   iface.subnet_mask =   iface.transport_name = tcp  iface.initiatorname =   iface.state =   iface.vlan_id = 0  iface.vlan_priority = 0  iface.vlan_state =   iface.iface_num = 0  iface.mtu = 0  

Step 6: Access iSCSI Target on CentOS / RHEL 8

Login to your account by typing this command , you will see a success message at the end.

iscsiadm -m node --login

Logging in to iface: default, target: iqn.2019-11.osradar.com:target01, portal: 172.17.255.109,3260 Login to [iface: default, target: , portal: 172.17.255.109,3260] 
 iqn.2019-11.osradar.com:target01 successful.

Make sure you’re logged into your iSCSI Target Server.

iscsiadm -m session -o show

tcp: [1] 172.17.255.109:3260,1 iqn.2019-11.osradar.com:target01 (non-flash)

Check disks if you’ve added Target’s disk

We’ve created backstore of 5GB space in our previous tutorial.

lsb1k

Format & mount the new disk to make it ready for use.

In this tutorial we’ll use fdisk to set up LVM type. You are free to use your desired one.

fdisk /dev/sdb

Confirm the new partition number.

lsb1k

Look at the new partition , we have sdb1 as seen below. Now, add a file system on the new partition.

 NAME            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT  fd0               2:0    1    4K  0 disk  sda               8:0    0   20G  0 disk  ├─sda1            8:1    0  953M  0 part /boot  └─sda2            8:2    0 19.1G  0 part    ├─centos-root 253:0    0    6G  0 lvm  /    ├─centos-swap 253:1    0  956M  0 lvm  [SWAP]    ├─centos-home 253:2    0  7.5G  0 lvm  /home    └─centos-var  253:3    0  4.7G  0 lvm  /var  sdb               8:16   0    5G  0 disk  └─sdb1            8:17   0    5G  0 part ##sdb1 Added  sr0              11:0    1 1024M  0 rom 

Set file system on the partition

Here, we’ll use xfs. You can use any (ext3,ext4,Btrfs etc) to fit your case.

mkfs.xfs /dev/sdb1

Mount your partition and confirm

mount /dev/sdb1/mnt

df -TH

Congratulations! You’ve all done. If have any queries regarding this tutorial, you can ask in comments.

The post How To Configure iSCSI Initiator on CentOS / RHEL 8. appeared first on Linux Windows and android Tutorials.

Step 1: Update your System

Type this command to update your system.

sudo dnf update

Step 2: SELinux is in Enforcing Mode

Make sure your SELinux status is working.

getenforce

As it will cover configuration of SELinux, make sure it is running in enforcing mode.

Step 3: Install Targetcli on CentOS / RHEL 8

The package for iSCSI Target is available as targetcli on your CentOS / RHEL 8 default AppStrean repositories. You can isnstall it by runnign following command.

sudo dnf -y install targetcli

Step 4: Check available space on your system

Before proceeding further make sure you’ve enough space available for allocation. It is recommended to set a different partition for easier way to manage without interfering with the core CentOS files and system.

df -hT

It would be more easy if you’ve a secondary disk on the server so use it if you’ve.

Step 5: Configure iSCSI Target on CentOS / RHEL 8.

Create a directory in your configured disks e.g; in /var/ or a mount point for your secondary disk, or a raid device.

sudo mkdir /var/targetdisk01

Now move towards to create our targets through targetcli admin console.

sudo su -
targetcli

List its contents to look over.

ls

After listing you will see that everything is empty. You will notice that the first thing in the content is the back-stores.

What are Backstores?

Backstores are for the purpose of providing different ways of keeping data locally that can be later exported or made available to an external system such as an initiator. The available options for backstores are block, fileio,pscsi, and ramdisk.

Block backstore can be a Linux block device like hard drive. If you’ve disk in your target you can use this option. Fileio refered to a normal file on the file system that has been created with a predefined size. We will use this option in our set up. Genearally, a block backstore performs better than a single file.

Create a fileio backstore of 5GB.

Change path to backstores/fileio while on the targetcli console and create the backstore.

cd backstores/fileio

Make sure it is created by listing the content.

ls

Create the iSCSI Target

Move to the iSCSI path in your server for creating the iSCSI Target.

cd /iscsi

As we are now inside iscsi path so it is possible to create the iscsi target with a name. The naming convention is standard and be like this.

[ iqn.(year)-(month).(reverse of domain name):(Your favourite name) ].

Our domain is osradar.com, the reverse of it will be the com.osradar. You can select your desired domain according to this method. So, let’s create our first target.

create iqn.2019.11.osradar.com:iSCSITarget1

Have a look at the changes by typing ls command.

ls

Create a LUN

LUN is a logical unit of storage. A target can offer one or more LUNs to the iSCSI clients, who initiates a connection with the iSCSI server. Navigate to the option target portal group (TPG) we created earlier in the previous command. Notice “Created TPG 1” from above.

cd iqn.2019-11.osradar.com:target01/tpg1/luns

Now create the LUN from the targetdisk1. Use your selected disk.

create /backstores/fileio/targetdisk1

List content to verify.

ls

Configur Access Control List (ACL)

ACL is used to connect only known initiators to our Target. Go to file /etc/iscsi/iniatorname.iscsi file on the client/initiator and check the name of initiator. You can use your own according to your requirements.

sudo vi /etc/iscsi/initiatorname.iscsi

While staying on the same path as above navigate to acls

cd acls

Now run the following command with the iqn of the initiator in the acls path.

create iqn.2019-11.com.osradar:initiator1

Set up Credential details

Set up username and password to authenticate the initiator while it sends a request to the target.

Make sure your settings are properly done by navigating to /iscsi and then save it by exiting.

Enable the target and allow firewall rules.

Step 6: Configure iSCSI Initiator

We have all done except configuring our initiator. Follow our following tutorial to learn configuring iSCSI initiator.

How To Configure iSCSI Initiator on CentOS / RHEL 8.

Congratulations! You’ve all done if have any queries regarding this tutorial leave a comment.

The post How To Configure iSCSI Target and Initiator on CentOS 8 /RHEL 8 appeared first on Linux Windows and android Tutorials.

As you know about Cache, it enhances the loading speed by saving web pages, cookies and other data. It saves into memory the requested data and provide faster results. Because of its faster response, it is also used in Linux like Centos to provide faster results. It is also called caching HTTP reverse proxy which is a leading web application accelerator, capturing the visits and boost upon delivery on again request. It saves the web servers time by providing them the same data as saved earlier. Hence, in this tutorial we are going to learn how you can install and configure Varnish Cache 6 on CentOS 8 / RHEL 8.

Step 1: Update System

Make sure your system is up-to-date.

sudo dnf -y update

Step 2: Install Varnish Cache 6 on CentOS 8 / RHEL 8

You can use the following command to install varnish cache on CentOS / RHEL 8.

sudo dnf install @varnish

Allow to continue with the installation process by pressing y key.

If you want to see more information on installed package you can type the following command.

rpm -qi varnish

Important things to Remember:

• Main configuration file of Varnish can be found in /etc/varnish/default.vcl
• Secret file of Varnish is in /etc/varnish/secret
• Cashe executable binary is found in /usr/sbin/varnishd
• Systemd unit file is in /lib/systemd/system/varnish.service

Step 3: Start and Enable Varnish Cache Services

Use the following command to start & enable Varnish Cache services.

sudo systemctl enable --now varnish

Make sure status is working properly

systemctl status varnish

Step 4: Configure Varnish Cache for Nginx/Apache Web Server

As Varnish sits in front of a web server as a caching HTTP Reverse Proxy, so it speeds up web servers.
In this tutorial we are using Nginx/Apache HTTPD server but you can use your favourite one.

For Apache

sudo dnf -y install @httpd

For Nginx

sudo dnf -y install @nginx

1. Configure Nginx with Varnish

By default, TCP port 80 is being used by Nginx, change it to listen to 8080 port because Varnish Cache will use port 80.

sudo vi /etc/nginx/nginx.conf

For Virtual Hosting feature, edit the relevant confiuguration file,

sudo vi /etc/nginx/conf.d/mysite.conf

After it, restart Nginx

sudo systemctl restart nginx

Double-check your settings

ss -tunelp | grep 8080

2. Configure Apache with Varnish

For Apache web server, make sure to set listen port to 8080.

sudo vi /etc/httpd/conf/httpd.conf

After it, restart Apache.

sudo systemctl restart httpd

3. Configure Varnish Cache Server

Set Listen port for Varnish Cache to 80.

sudo vi /etc/systemd/system/multi-user.target.wants/varnish.service

Edit the line starting with ExecStart, and change from:

ExectStart=/usr/sbin/varnishd -a :6081 -f /etc/varnish/default.vcl -s malloc,256m

To:

ExectStart=/usr/sbin/varnishd -a :80 -f /etc/varnish/default.vcl -s malloc,256m

Now, restart Varnish systemd services.

sudo systemctl daemon-reload
sudo systemctl restart varnish

Make sure that Varnish is listening the correct port.

sudo systemctl status varnish

Also make sure that Nginx/Apache server is configured as a back-end server for Varnish proxy.

sudo vi /etc/varnish/default.vcl

Look port 8080 is configured on Apache/Nginx web server.

Your configuration will look like this for multiple back-ends,

backend default {
     .host = "127.0.0.1";
     .port = "8080";
 }
backend java {
     .host = "127.0.0.1";
     .port = "8000";
 } 

But we’ll need to tell Varnish to where send the difference URL using vcl_recv. For example our java application should handle URL beginning with /java/

sub vcl_recv {
     if (req.url ~ "^/java/") {
         set req.backend_hint = java;
     } else {
         set req.backend_hint = default;
     }
 }

You can see more ones on using Multiple backends.

Step 5: Testing Varnish Cache on Nginx/Apache

After all, verify Varnish Cache working by testing it with Apache/Nginx service with the curl command:

curl -I http://localhost

It will provide you HTTP header information.

If you run this command again, it will show you that Varnish Cached Response (Note that Age header):

This will work same for other valid domain names with DNS record set.

curl -I https://osradar.com

We’ve installed & configured Varnish Cache on CentOS 8 / RHEL 8 for Nginx and Apache Web Server.

Visit the Varnish Getting Started and The Varnish Users Guide pages to learn more about configuring & optimizing Varnish.

The post How to Install Varnish cache 6 for Apache/Nginx on Centos / RHEL 8 appeared first on Linux Windows and android Tutorials.