Updated Version of myNetShop Client Portal Released: What’s New

NetShop ISP, a leading web hosting provider based in Cyprus, announces, today, a major release update of the myNetShop client portal. The new release features an updated and highly sophisticated engine, as well as a new, intuitive design interface for both desktop and mobile devices.

NetShop ISP, a leading web hosting provider based in Cyprus, announces, today, a major release update of the myNetShop client portal.

The year 2022 has seen an accelerated uptake of hosting services and digital products, as well as a remarkable increase in the time an average customer spends daily in the portal. Comparing to the previous year, in 2022 there has been a 43% growth in the number of customers who are using myNetShop on a daily basis, as well as a notable 31% increase in the number of API calls per minute for activities such as DNS management, OS re-build for VPS, Password reset on Dedicated Servers, and remote deployments of Forex VPS servers.

The new release features an updated and highly sophisticated engine, as well as a new, intuitive design interface for both desktop and mobile devices.

myNetShop Engine New Features

Some of the new features introduced in this version are:

  1. Backup/snapshots creation and management for VPS servers
  2. Multi-factor Authentication (MFA)
  3. Real-time inventory check for Dedicated Servers (in/out of stock)
  4. Revolut added in list of accepted payment methods
  5. USDT (Tether) added in list of accepted payment cryptocurrencies
  6. Quote Estimates now visible to customers with ability to approve or reject
  7. Clients can now Invite Users (other myNetShop registered clients) to view information on their Account
  8. Option to send encrypted message via ticket for sensitive data exchange
  9. “Emergency Button” available for customers subscribed to Premium SLA and/or Managed Services

In addition to the new functionality enhancements, there have been important UI changes to enhance the user experience – from signup to product ordering, payment and service management.

New User Interface

The new UI is a result of an in-depth analysis of the users activity throughout the years and their engagement with the tools to order or manage their services.

Here are the most important changes one can see in the updated myNetShop portal interface:

  1. Left Sidebar Menu – all offered hosting services are visible by default, with navigation to order or manage in one click
  2. Top Menu – quick access to important tools such as Support, Invoices, Notifications and User Menu
  3. Accessibility – improved contrast between background and foreground elements, as well as navigation improvements from mobile devices
  4. Dashboard – New, widget-based interface design.
  5. Single Management Page per Product Category – Easier navigation to a product category’s management page. Different products (e.g. Cyprus VPS, UK VPS, Singapore VPS) can now be viewed and managed from a single category page (e.g. Virtual Servers)

“I am honored to be leading NetShop ISP, a hosting company of choice for more than 3,000 customers worldwide. We are committed to building out the myNetShop portal as a hub for centralized and efficient administration of all services used by our customers; from website hosting, domain names and backups, to cloud, dedicated servers and co-location hosting. Stay tuned for many new myNetShop features scheduled to roll out within Q1 and Q2 2023”, said Stefano Sordini, CEO at NetShop ISP.

Stefano Sordini, CEO at NetShop ISP, comments on new myNetShop Portal release

“I am honored to be leading NetShop ISP, a hosting company of choice for more than 3,000 customers worldwide. We are committed to building out the myNetShop portal as a hub for centralized and efficient administration of all services used by our customers; from website hosting, domain names and backups, to cloud, dedicated servers and co-location hosting. Stay tuned for many new myNetShop features scheduled to roll out within Q1 and Q2 2023”, said Stefano Sordini, CEO at NetShop ISP.

How To Change RDP Port on Windows Server 2016/2019/2022

In this article we will explain how to change the RDP Port on Windows Server 2016/2019/2022 via regedit and then make the necessary changes on Windows Firewall for allowing inbound connections to the new RDP port.

The remote accessibility of a Windows server is managed by the Remote Desktop Services (given it’s enabled) which “listens” to port 3389 and its open by default. Whilst this is an essential communication protocol for establishing connection to remote Windows machines, it is often used by hackers to deliver a ransomware or a DDoS attack to a single server or a distributed network of inter-connected machines.

One of the best security practices we follow when setting up Windows Servers is to change the default RDP port ‘3389’ to a custom, non-standard port. Have in mind that ports ranging from 1 to 1023 are called known or standard ports, while ports 49152-65535 are dynamic/non-standard. You are free to use any ports from the dynamic range but not one from the known/standard range as the latter may be in use by another Windows service.

In this article we will explain how to change the RDP Port on Windows Server 2016/2019/2022 via regedit and then make the necessary changes on Windows Firewall for allowing inbound connections to the new RDP port.

How To Change RDP Port on a Windows Server

Pre-requisites

  • Tutorial steps can be applied (tested) on Windows Server 2012 R2, Windows Server 2016, Windows Server 2019 and Windows Server 2022
  • Access on Windows Server using Administrator or any other user with admin privileges
  • Out-of-band access on the server such as iDRAC or iLO – useful in case you lose remote connection to the server over the public network

Steps to Change RDP Port from Registry (regedit)

  1. Type regedit in the Search box
  2. From the left navigation bar follow this path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
  3. Find PortNumber
  4. Right-click Edit, then click Modify, and then click Decimal
  5. Type your new desired port number, and then click OK.
  6. Close the registry editor and restart your server*

* Proceed with server restart only if you are sure there is no Firewall on your server. In any other case, read further below how to whitelist the new RDP port on Windows Firewall.

Change RDP Port on Windows Server from regedit

Allow Custom RDP Port on Windows Firewall

Depending on your Windows Firewall state, you may need to add the new RDP port in the Inbound rules to ensure new connections will be allowed.

  1. Open Windows Firewall on your Server (type firewall in the Search box)
  2. From the left-hand navigation, click Inbound Rules
  3. Click New Rule in the right-hand pane to open the New Inbound Rule Wizard.
  4. In the New Inbound Rule Wizard, under the Rule Type section, select Port and click Next
  5. In the Protocol and Ports section, select TCP. Next, select Specific local ports, enter the custom RDP port as you have set it in Registry and then click Next
  6. In the Action section, select Allow the connection and click Next
  7. In the Profile section, select all appropriate profiles for when this rule applies and click Next
  8. Finally, give your new rule a descriptive name so that it is easy to find later, and click Finish.
  9. Reboot your server if you haven’t done so after the registry changes
Allow new RDP Port on Windows Server Firewall
Create Inbound Firewall Rule for new Windows RDP Port

Verify New RDP Port with PowerShell

Once your server has been rebooted you should be able to access it with the newly added RDP Port. To verify the newly set RDP port number, open PowerShell and run the following command:

Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -name "PortNumber"

Sample Output:

PortNumber : 61489
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations
PSChildName : RDP-Tcp
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry

This is it! You have successfully changed your Windows Server’s Remote Desktop Port and allowed it through your Windows Firewall.

AlmaLinux 9.0 Stable Now Available for Deployment on Cloud VPS and Dedicated Servers

The AlmaLinux project became the first public RHEL-based distribution that has released a stable build based on RHEL 9. Deploy AlmaLinux 9 Stable on VPS and Dedicated Servers.

The AlmaLinux project became the first public RHEL-based distribution that has released a stable build based on RHEL 9. This new distribution is fully binary compatible with Red Hat Enterprise Linux which means you can use it as a replacement for RHEL 9 and CentOS 9 Stream.

New Features and Changes in AlmaLinux 9

There are quite a lot of exciting features introduced by the AlmaLinux project. Here are the best six features we have pinned down and sharing with you.

GNOME 40 and GTK 4 Library

The desktop edition of AlmaLinux 9 is based on GNOME 40 and the GTK 4 library. A noticeable change one can notice is the virtual desktops in Activity Summary mode that have been changed to landscape orientation and are displayed as a continuous scrolling chain from left to right.

GRUB Boot Menu

By default, GRUB boot menu is hidden if it is the only distro installed on the system and if the last boot was successful. To display the menu during boot, simply hold down the Shift key or the Esc or F8 key several times.

OpenSSL and OpenSSH Updates

Security updates could not have been neglected, of course. AlmaLinux 9 distribution now uses a new branch of the OpenSSL 3.0 cryptographic library, which means more secure cryptographic algorithms are in enabled.

Additionally, the OpenSSH package has been updated to version 8.6p1 and Cyrus SASL was moved to the GDBM backend instead of Berkeley DB. The NSS (Network Security Services) libraries no longer support the DBM (Berkeley DB) format and, finally, GnuTLS has been updated to version 3.7.2.

Python 3

AlmaLinux 9 is now fully migrated to Python 3 with default branch set to Python 3.9. Python 2 has been deprecated.

SELinux

SELinux performance has been significantly improved with reduced memory consumption, as there is now support for setting “SELINUX=disabled” to disable SELinux in /etc/selinux/config has been removed (the specified setting now only disables policy loading, and in fact disabling SELinux functionality now requires passing “selinux=0” to the kernel).

Deploy AlmaLinux 9 on VPS and Dedicated Servers

The stable edition of AlmaLinux 9 is now available for deployment in all our VPS plans.

Deployment is instant and all you have to do is choose your favourite VPS plan, choose AlmaLinux 9 and proceed with order.

Deploy AlmaLinux 9 Stable on VPS Server

Similarly, you can choose AlmaLinux 9 from the Operating system drop-down list when ordering a Dedicated server of your choice.

How Server Hosting Reduces Latency and Enhances Performance for Forex Brokers [CEO Interview at Fazzaco]

Stefano Sordini, CEO at NetShop ISP, speaks to Fazzaco in an exclusive interview, about the impact of Server Hosting in Trading Performance and Latency for Forex Brokers.

The article has been originally published on the 8th of December 2022 by Fazzaco.

NetShop ISP, a European-based Hosting & Data Center provider, has more than a decade of presence in the IT industry, servicing companies in the Fintech, Banking, iGaming, Forex, Blockchain and IT industry. 

​Today, we have the honor to invite Stefano Sordini, CEO at NetShop ISP, for an exclusive interview with Fazzaco, covering numerous topics such as server hosting​, proxy servers, DDoS protection and server deployment.

Fazzaco: What exactly are server hosting and proxy servers and how do they work for forex brokers?

Stefano: Server hosting, in a nutshell, is required to ensure that content like websites and emails can be accessed via the internet. There are different types of hosting like shared hosting, dedicated hosting and VPS hosting, each with different benefits depending on the specific needs of the client.

A proxy server acts as an intermediary between a user’s computer and the internet. The proxy server effectively hides your IP address, providing heightened security, privacy and performance which is essential for any Forex business, especially those using MetaTrader 5 (MT5). In this case, the proxy server will act as a gateway between your clients’ trading terminals and the trading server, meaning your MT5 server will only receive requests from the proxy server, ultimately enhancing the MT5 server’s security.

In addition to security, a proxy server will also become necessary for brokerages as their trading volume increases, as well as those targeting traders in different areas of the world.

To help you understand the benefit of introducing a proxy within MetaTrader’s ecosystem, let’s take a look at the following scenario. A forex broker operates an MT5 Main Trade server hosted in London (UK) whilst the majority of their customers/traders are based in Malaysia.

Without a proxy in place, an order placed from a trader in Malaysia will ‘travel’ across to London to reach the UK-based Trading server where the order will be executed. In Forex trading, execution speed is everything so due to the physical distance between the two countries, it’s almost certain that the trader will suffer from slippage.

On the contrary, if the same Forex broker had a Proxy/Access server deployed in Asia, let’s say Singapore, then slippage would be avoided. This is simply because the Malaysian trader would connect to the Singapore-based Access Server as the MT5 terminal would detect a better latency/connectivity. Orders will eventually be executed in the Main trade server in London, however as they are passed through the Singapore proxy, the price at which the order was placed will be the same as the executed one.

Fazzaco: Can you explain some important parameters in hosting, such as cores, remote access, CPU processors, IP address, etc., and how they would affect transfer speed for forex brokerage business?

Stefano: Any successful brokerage business heavily relies on the sophistication of its server infrastructure. It’s highly recommended that your trading platform is hosted on dedicated servers, more specifically two dedicated servers each located in different data centers, one being used as the main server and the other as a backup. Ideally, the data from the main server should be backed up in real time, and configured similarly to that of the main server.

Some more specific technical requirements for Forex brokerages running either MT4 or MT5 include a minimum of 8 GB RAM, at least 100Mbps Internet connection for both download and upload and Intel i7 4th Gen Quad Core. These specs consist the minimum requirements a Trading server could have in order to operate and usually are the specs startup brokers would go for.

The more traders a Forex broker acquires means higher trading activity, and therefore, the trading server must be upgraded (in terms of hardware specs) to cope with the increased demand.

Having said that, I don’t want to give the impression that any server meeting the minimum hardware and network requirements is good for hosting a Trading platform. The majority of the recently onboarded Brokers, reach out to NetShop ISP as they are facing issues with slow orders execution, frequent network disruptions and unexpected server reboots. What we have realized is that some of these Brokers were running their Trading platforms on either virtual machines or quite old bare metal hardware. What I would advise everyone who is facing problems with their trading servers or looking for a reliable hosting provider, is to request more information about the type of server they will be given, and not just the specs of the server. Even if everything looks stable in the beginning, a poor choice of a trading server infrastructure will eventually impact the entire trading experience for the traders with impact, of course, to the Forex broker.

Fazzaco: How helpful is it in reducing latency?

Stefano: Not only is it extremely helpful, it has become absolutely essential to integrate the right trading architecture. In fact, the right hardware could potentially reduce latency up to 50%. When we talk about latency it’s important to understand that latency is not just about the “distance” between the trader’s network and the trading server’s. The trading platform should ensure the minimum latency with its Liquidity Bridge, and subsequently the Bridge needs to have as lower latency as possible with the liquidity provider. In an ideal trading environment, latency across between the trading server and the liquidity end should be as low as below 2ms. On the other hands, an acceptable latency for a trader to avoid slippage is up to 50-60ms. As well as the said hardware and networking requirements, the location of your server is also something that plays a huge role in reducing latency. It’s suggested that Forex Brokers opt for a data center situated in a strategic financial location for the most optimal environment to attain low latency.

Fazzaco: How can you help with DDoS protection?

Stefano: By default, we offer protection against the most common amplification DDoS attacks, like NTP amplification, DNS amplification and SSDP amplification, with no further reconfiguration needed on the customer side. The filtering engine drops the malicious amplified packets, leaving the rest of the traffic intact. This is already included in our billing plans at no additional cost.

Protection against sophisticated and expensive DDoS attacks could also be designed through our partner technology (including MT5 trading server protocol protection) if needed. Pricing for a solution like this could only be estimated after the initial solution engineering process.

I understand that DdoS attacks mitigation services can be expensive (starting from 2-3,000 USD per month) and not all Forex brokers can afford it as a preventive solution. NetShop ISP offers a wide-range of solutions which have provenly helped numerous customers of ours to strengthen their trading infrastructure security whilst keep their expenses low. Some of the solutions we offer are protection via Premium DNS, Web Application Firewall (WAF) and Security Hardening for both the network and servers of a customers. These solutions combined will drastically improve the overall security of a trading infrastructure and, in most cases, Brokers did not have to go for the expensive solution of DdoS Attack mitigation service.

Learn more about NetShop ISP’s DDoS Protection services >>

Fazzaco: What’s your recommendation for forex brokers and start-ups when it comes to server deployment? Should they select a physical one or a virtual one, or both combined?

Stefano: Forex Brokers of any size are highly recommended to go for dedicated servers when it comes to hosting their main trading server. Dedicated resources will guarantee heightened performance, and a dedicated server also ensures increased security and overall flexibility when it comes to the configuration.

Of course, my personal recommendation would be to have the following components as dedicated servers: main trading and history server, main trading backup server. The proxy server can be provisioned as virtual as it does not require high and dedicated specifications to run.

However, for startup brokers with a limited budget, I guess a virtual server can be used for their backup trading server; but in all cases, without a doubt, the main trade server should be physical/dedicated, for all of the aforementioned reasons. 

A good physical server does not always have to be expensive. At NetShop ISP we offer dedicated servers with specifications above the minimum that the MetaQuotes software require, at a price which is very reasonable for startup brokers. Of course, as the broker grows along with its clients’ trading volume, they should never forget to revise the infrastructure of the main trade servers, and do any adjustments or upgrades needed to ensure stable and reliable performance.

How to Install PostgreSQL on AlmaLinux 9 Server

In this tutorial we will guide you through the simple steps of installing PostgreSQL on AlmaLinux 9 Operating system.

PostgreSQL is a object-relational, open source database system that can be used for both small and large-scale projects; from simple websites and intranet applications to complex, ‘big data’ projects.

When a new server is installed, PostgreSQL’ s settings are very minimum as they are designed to run on the least amount of hardware possible.

In a survey conducted by Statista in August 2022, PostgreSQL is ranking second (just behind MySQL), in terms of the most used database technologies available. The main reason for PostgreSQL’s popularity, in addition to being open source, is the fact that it requires very minimum requirements on the hardware it will be installed at.

In this tutorial we will guide you through the simple steps of installing PostgreSQL on AlmaLinux 9 Operating system.

Install PostgreSQL on AlmaLinux 9

Before going through the rest of the article on how to install PostgreSQL on AlmaLinux 9 Server, please make sure you check the pre-requisites.

Pre-requisites

  1. VPS or Dedicated Server with AlmaLinux 9 Operating System
  2. Access on the server with a root or sudo privileges user

Step 1 – Update AlmaLinux 9 Server

Once you have access your newly installed AlmaLinux 9 server, update the packages to the latest versions available by executing the following command:

root@almalinux-server:~$ dnf update && dnf upgrade -y

Step 2 – Install PostgreSQL

At the time of writing this article (December 2022) the latest stable PostgreSQL version is 15.0. This version is not available, yet, in the default repo of AlmaLinux 9, so type the following command to install the official PostgreSQL repository in our system:

root@almalinux-server:~$ dnf install -y sudo dnf install -y https://download.postgresql.org/pub/repos/yum/reporpms/EL-9-x86_64/pgdg-redhat-repo-latest.noarch.rpm

Then, update the index of your server’s packages with the following command:

root@almalinux-server:~$ dnf update -y

Now, you can install the PostgreSQL server with the following command:

root@almalinux-server:~$ dnf install postgresql15 postgresql15-server

As soon as the installation completes, execute the following command to initialize the newly installed database:

root@almalinux-server:~$ /usr/pgsql-15/bin/postgresql-15-setup initdb

Sample Output:

Initializing database … OK

Once database has been initialized, enter the following commands to start the PostgreSQL service and automatically enable it on startup:

root@almalinux-server:~$ systemctl start postgresql-15 && systemctl enable postgresql-15

To verify that the service has been started without errors, enter the following command:

root@almalinux-server:~$ systemctl status postgresql-15

Sample Output:

postgresql-15.service – PostgreSQL 14 database server
Loaded: loaded (/usr/lib/systemd/system/postgresql-15.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2022-12-02 21:03:15 CEST; 1min 25s ago
Docs: https://www.postgresql.org/docs/15/static/

Step 3 – Set or Change the PostgreSQL User Password

Upon successful installation and first startup of the PostgreSQL database service, you can change the default user password for PostgreSQL as follows:

root@almalinux-server:~$ passwd postgres

You will be prompted to set a new password and then to re-type it.

Sample Output:

Changing password for user postgres.
New password:
Retype new password:
passwd: all authentication tokens updated successfully.

Step 4 (optional) – Allow Remote Access to PostgreSQL Database

By default, PostgreSQL is configured to listen to local connections only.

If you need to access the database remotely (e.g. from your computer or from a software in another server) then do the following:

  • Open the file /var/lib/pgsql/15/data/postgresql.conf
  • Replace the line listen_addresses = ‘localhost with listen_addresses = ‘*
  • Open the file /var/lib/pgsql/15/data/pg_hba.conf
  • Add this entry at the end of the file: host all all 0.0.0.0/0 md5
  • Save and close the file

For the changes to take effect restart the PostgreSQL service as follows:

root@almalinux-server:~$ systemctl restart postgresql-15

This is it! You have successfully installed PostgreSQL 15 on AlmaLinux 9 Server. Enjoy!

How To Install Latest Python 3.11 on Ubuntu Server

In this article we will demonstrate how to install the latest Python 3.11 version on an Ubuntu server via the apt package manager, and also how to set the default Python version in case you have multiple versions installed on your server.

Python is one of the most popular and fastest-growing object-oriented programming languages. Python is mostly used for building websites, applications for mobile, web and desktop. It is also the programming language of choice for automating tasks and conducting data analysis.

At the time of writing this article (December 2022) there are two main Python versions being used; Python v2 and v3. Whilst Python 2 will see no major releases, the v3 is under active development and has already seen a lot of stable releases. Currently, the latest stable version is 3.11 which was released on Oct. 24, 2022.

In this article we will demonstrate how to install the latest Python 3.11 version on an Ubuntu server via the apt package manager, and also how to set the default Python version in case you have multiple versions installed on your server.

Install Python 3.11 on Ubuntu using apt

In this tutorial we will be using the “deadsnakes” repository as it contains the more recent Python versions ready for Ubuntu.

Pre-requisites

  1. root access (or any sudo level user account)
  2. Ubuntu server (in this tutorial we are using Ubuntu Server 22.10)

Easy Steps to Install Python 3.11 on Ubuntu

Login to your Ubuntu server and type the following commands:

root@ubuntu-server:~$ sudo add-apt-repository ppa:deadsnakes/ppa
root@ubuntu-server:~$ sudo apt update
root@ubuntu-server:~$ sudo apt install python3.11

By adding the repository ppa:deadsnakes/ppa allows us to install other versions as well. See below the commands for installing old python versions.

root@ubuntu-server:~$ sudo apt install python3.11
root@ubuntu-server:~$ sudo apt install python3.10
root@ubuntu-server:~$ sudo apt install python3.7

Finally, type the following command to see all Python binaries installed on your Ubuntu server.

root@ubuntu-server:~$ ls -l /usr/bin/python*

Sample Output:

lrwxrwxrwx 1 root root      10 Dec 2  2022 /usr/bin/python3 -> python3.10
-rwxr-xr-x 1 root root 5901416 Dec  2  2022 /usr/bin/python3.10
-rwxr-xr-x 1 root root 6705016 Dec 3 09:45 /usr/bin/python3.11
-rwxr-xr-x 1 root root     960 Dec 2  2022 /usr/bin/python3-futurize
-rwxr-xr-x 1 root root     964 Dec 2  2022 /usr/bin/python3-pasteurize

In our system, the default Python version used is 3.10, as indicated by the symlink:
lrwxrwxrwx 1 root root 10 Dec 2 2022 /usr/bin/python3 -> python3.10

We can also verify the current Python version by executing the following command:

root@ubuntu-server:~$ python -V

Sample Output:

Python 3.10.4
To use Python 11 whilst maintaining an older version as default, type the following command and hit 'Enter':
root@ubuntu-server:~$ python3.11

By doing so you will enter the Python Shell. To exit the Python interpreter, type the following commands within the shell and then press ‘Enter’:

quit()
OR
exit()

Change Default Python Version on Ubuntu Server

In the case you have multiple Python versions installed, you can change the default version as follows. In our example, our Ubuntu server had as default Python 3.10 and we will change it to Python 3.11.

root@ubuntu-server:~$ python3 --version
root@ubuntu-server:~$ sudo update-alternatives --install /usr/bin/python3 python3 /usr/bin/python3.10 1
root@ubuntu-server:~$ sudo update-alternatives --install /usr/bin/python3 python3 /usr/bin/python3.11 2
root@ubuntu-server:~$ sudo update-alternatives --config python3
root@ubuntu-server:~$ python3 --version

That’s all! If you followed all the steps above you have successfully installed Python 3.11 on your Ubuntu server!

How To Install Node.js and NPM on Debian 11 server

In this tutorial, we will demonstrate two easy ways to to install Node.js and NPM on a Debian 11 server. For the purpose of this writing this tutorial, we have used and tested all commands in a VPS server running Debian 11 64-bit.

Node.js is an open-source JavaScript library built on Chrome’s V8 engine and is primarily used for back-end API services and other server-side applications. Along with React, Node.js is one of the most popular technologies in the world of front-end web development in 2022.

In this tutorial, we will demonstrate two easy ways to to install Node.js and NPM on a Debian 11 server. For the purpose of this writing this tutorial, we have used and tested all commands in a VPS server running Debian 11 64-bit.

Tutorial Pre-requisites

  • Linux machine running Debian 11 OS
  • Root access (or alternative user with root/sudo privileges)

2 Easy Ways To Install Node.js and NPM on Debian 11 Server

First connect via SSH on your server, and ensure all Debian packages are up-to-date. You can do so by executing the following commands:

root@netshopisp-vps:~# apt update && apt upgrade -y

Now that our Debian 11 environment is fully up to date we can proceed to installing Node.js and NPM. We will demonstrate three different, easy ways.

Method 1: Install Node.js and NPM via Debian Repository

The following command will install both packages at once. This is the simplest and most reliable way.

Note that at the time of writing this tutorial (November 2022), Node.js version 12.22 is included by default on Debian’s repositories.

root@netshopisp-vps:~# apt install nodejs npm

As soon as both packages are installed, you can verify their version by executing the following commands:

root@netshopisp-vps:~# node -v
root@netshopisp-vps:~# npm -v

Sample Output:

NodeJS and NPM installation from Debian Repositories – Check versions

Method 2: Install Node.js and npm from NodeSource

The second method requires a bit more effort than the first, however in case you want to install a specific version of NodeJS and/or NPM, then this method is preferred.

NodeSource maintains an APT repository with multiple Node.js versions.

First command will install ‘curl’ in our system:

root@netshopisp-vps:~# apt install curl -y

We are going to download and run the Node.js installation script for version 16.
If you want another version of Node.js  (for example 14.x) just change the setup_16.x with setup_14.x.

root@netshopisp-vps:~$ curl -sL https://deb.nodesource.com/setup_16.x | bash -

Now, install the Node.js version 16 with the following command:

root@netshopisp-vps:~# apt install nodejs

The Node.js package contains both the node and npm binaries. Once installed, verify the installed version of Node.js with the same commands as mentioned earlier in this tutorial.

root@netshopisp-vps:~# node -v
root@netshopisp-vps:~# npm -v

Sample Output:

Manual Installation of NodeJS and NM from NodeSource – Check versions

Congratulations! You have now installed Node.JS and NPM on your Debian 11 server. Both two methods we demonstrated are easy and fast to install.

NetShop ISP CEO Shortlisted at Fazzaco Hall of Fame 2022

Stefano Sordini, CEO at NetShop ISP, is nominated as best Chief Executive Officer in the Fintech category at the Fazzaco Hall of Fame 2022.

NetShop ISP make its appearance at the Fazzaco Hall of Fame 2022, dedicated to companies and individuals who excel in the Forex, Crypto and Fintech industries.

Stefano Sordini, CEO at NetShop ISP, is nominated as best Chief Executive Officer in the Fintech category. Submit your vote here.

Stefano Sordini has an in-depth experience in the Fintech industry of more than 12 years. From his position as a CEO at NetShop ISP has contributed to grow the company into the Fintech sphere to become, today, one of the most preferred hosting providers among Forex brokers and Technology companies in the Fintech sphere. During 2022, the company has on-boarded more than 45 Forex brokers for trading platforms hosting and Disaster Recovery solutions.

Voting period opens on 21st of November until 16th of December 2022.

How To Install MariaDB 10.5, Apache 2.4, PHP 7.4 (LAMP) on Debian 11 Server

In this article we are going to demonstrate, in a few very easy steps, how to install LAMP on a Debian 11 Server. All you have to do is connect on your server, follow this article and copy/paste the commands we provide in each step below.

The LAMP stack is a popular set of open-source software used on Linux environment for hosting database-driven websites. The acronym LAMP stands for Linux, Apache, MySQL/MariaDB, PHP/Perl/Python.

In this article we are going to demonstrate, in a few very easy steps, how to install LAMP on a Debian 11 Server. All you have to do is connect on your server, follow this article and copy/paste the commands we provide in each step below.

Pre-requisites

  • Server with Debian 11 OS installed
  • Root access on your server with SSH enabled
  • Temporarily disable firewall/iptables, or keep enabled with port 80 allowed/unfiltered

Steps To Install LAMP Stack on Debian 11 Server

Before getting into install the necessary software, update your system as follows:

apt-get update && apt-get upgrade

Step 1. Install Apache 2.4 Web Server

Run the following command to install apache2 and the associated libraries:

apt-get install apache2 apache2-utils -y

Now, verify the Apache version installed by executing the following command:

apache2 -v

You should see the following output:

Server version: Apache/2.4.51 (Debian)
Server built:   2022-11-05T09:31:22

The following command will start Apache2 and enable it so that it automatically starts at system boot:

systemctl start apache2 && systemctl enable apache2

Step 2. Install MariaDB 10.5 Database Server

MariaDB 10.5 version will be installed on Debian 11 system. Simply execute the following command:

apt-get install mariadb-server -y

As soon as mariadb is installed, execute the following command to start the service and enable it so it’s auto-started on server boot:

systemctl start mariadb && systemctl enable mariadb

Verify that MariaDB is running.

systemctl status mariadb

The following sample output is what you should get if everything went ok:

mariadb.service - MariaDB 10.5.15 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2022-11-09 06:28:03 EST; 43min ago
       Docs: man:mariadbd(8)
             https://mariadb.com/kb/en/library/systemd/
   Main PID: 3103 (mariadbd)
     Status: "Taking your SQL requests now..."
      Tasks: 8 (limit: 2340)
     Memory: 74.1M
        CPU: 1.817s
     CGroup: /system.slice/mariadb.service
             └─3103 /usr/sbin/mariadbd

By default, MariaDB is installed with empty root password. As this is insecure, we will execute the following command to set the root password and a few more security related settings:

mysql_secure_installation

First prompt will be to set a root password, so type a strong one. Then, answer to the following questions as follows:

Enter current password for root (enter for none):
Change the root password? [Y/n] Y
New password: ***********
Re-enter new password: ***********
Remove anonymous users? [Y/n] Y
Disallow root login remotely? [Y/n] Y
Remove test database and access to it? [Y/n] Y
Reload privilege tables now? [Y/n] Y

Now, restart MariaDB service with the following command:

systemctl restart mariadb

Step 3. Install PHP 7.4

The last step in our LAMP stack environment is to install PHP 7.4.

Use the following command to install PHP and other commonly used extensions:

apt-get install php libapache2-mod-php php-cli php-mysql php-zip php-curl php-xml -y

Once all installations are done, verify the version of PHP by executing the following command:

php -v

Step 3.2. Create Apache Virtual Host

The following commands will create a directory where you can upload your website files and set the right permissions: and will create the necessary apache virtual host configuration.

mkdir /var/www/html/awesomewebsite
chown -R www-data:www-data /var/www/html/awesomewebsite

Now, lets create the virtual host configuration file:

nano /etc/apache2/sites-available/awesomewebsite.conf

Paste the following content in the awesomewebsite.conf. Then save and exit.

<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    ServerName awesomewebsite.com
    DocumentRoot /var/www/html/awesomewebsite.com
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

Now, activate your newly created virtual host and disable the default one as follows:

a2ensite awesomewebsite.conf
a2dissite 000-default

You are all set! Now, reload Apache2 and check the service status by typing:

systemctl reload apache2 && systemctl status apache2

If all went well, you should see the following output:

apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2022-11-09 06:30:40 EST; 51min ago
Docs: https://httpd.apache.org/docs/2.4/
Main PID: 14140 (apache2)
Tasks: 8 (limit: 2340)
Memory: 19.1M
CPU: 852ms
CGroup: /system.slice/apache2.service
├─14140 /usr/sbin/apache2 -k start
├─14292 /usr/sbin/apache2 -k start
├─14293 /usr/sbin/apache2 -k start
├─14294 /usr/sbin/apache2 -k start

Congrats! You now have a properly configured environment with MariaDB database, Apache web server and PHP 7.4!

NetShop ISP Expand in Two New Region Hubs

NetShop ISP is proud to announce their recent expansion within Asia and South America. This year, the company has been steady on the path to global expansion, and introducing three new locations across two continents has been an integral part of their growth strategy.

NetShop ISP is proud to announce their recent expansion within Asia and South America. This year, the company has been steady on the path to global expansion, and introducing three new locations across two continents has been an integral part of their growth strategy.

In addition to their existing Data Center in Singapore, NetShop ISP has now landed in two additional locations in Asia; Hong Kong and Tokyo. They are located in Equinix’s HK2 Data Center for Hong Kong Dedicated Servers, and Equinix’s TY8 for Tokyo Dedicated Servers. In October, NetShop ISP also deployed private network infrastructure in São Paulo, Brazil, located in Ascenty 3.

All three Data Centers are Tier III ready as well as SOC 1/2 Type 2, PCI DSS and ISO 27001 compliant. They all offer high-bandwidth dedicated servers of up to 10 Gbps, 99.99% uptime SLA and 24×7 on-site support. The Hong Kong and Tokyo Data Centers offer direct connection to the Equinix IX, whilst the São Paulo location offers ultra-low latency to the Equinix IX and IX.br.

With the iGaming and Forex market in Asia growing rapidly, NetShop ISP’s decision to expand to two new locations within the region has been highly anticipated by operators in both industries. Since 2020, the Asian market has seen an exponential incline and operators are eager to capitalize on this. The two new Data Centers are designed for all businesses that require a local digital presence or fine-tuned routing in Asia through local internet carriers, which is especially advantageous for iGaming operators and Forex brokers breaking into the region.

The São Paulo Data Center is NetShop ISP’s first in LatAm. The carrier-neutral Data Center has access to over 295 networks, including major providers in South America. Over the last few years, the LatAm iGaming industry has seen a significant rise, and due to the sheer size of the market, shows no sign of slowing down. In fact, it has been noted that Brazil has the potential to become one of the world’s leading markets for online gambling. Similarly, Forex brokers are looking to establish a presence in Latin america to attract a huge pool of traders who are located there. Hosting in the region will no doubt give operators the competitive edge required to make their mark on the LatAm market.

NetShop ISP’s Global Hosting Services

NetShop ISP has over 10 years’ experience within the iGaming and Fintech sectors, and has been the recipient of multiple industry awards. With Data Centers located in prime global locations and a range of comprehensive solutions designed for sportsbook and casino operators, liquidity providers, trading platforms, NetShop ISP has the tools to help you navigate the industry.

How To Resolve Acronis Agent error related to “snumbd26” kernel module on Linux Plesk/cPanel Servers

When trying to update an Acronis agent on your Linux cPanel/Plesk server, you may encounter the following error: Mount points of kernel module ‘snumbd26’ are detected. Unmount them manually, and then repeat the installation. Why this is Happening snumbd26 mount points cannot be unmounted correctly, since p.2 jbd2 kernel daemon created and also writes to […]

When trying to update an Acronis agent on your Linux cPanel/Plesk server, you may encounter the following error:

Mount points of kernel module 'snumbd26' are detected. Unmount them manually, and then repeat the installation.

Why this is Happening

snumbd26 mount points cannot be unmounted correctly, since p.2 jbd2 kernel daemon created and also writes to snumbd block device.

In a situation when writing to mount completes with an error, perhaps due to insufficient free space, then an error is returned to the Snumbd block device and p.2 jbd2 kernel daemon.

How To Resolv snumbd26 Error

If you are free to reboot your Linux server, you can do so and re-attempt the agent update. By rebooting your server the Snumbd and jbd2 kernel daemons are forcefully killed, so there is a high possibility after reboot the agent update will complete successfully.

If you are working on a production server and cannot reboot it, follow these steps:

  1. SSH to your linux server
  2. Create the following config file using vi or nano:
    vi /usr/lib/Acronis/system_libs/8.2.1/config
  3. Insert the following lines inside your newly created file:
    !/bin/bash
    export ACRONIS_MOUNT_TMP_DIR=””
  4. Save & exit the file
  5. Restart the Acronis MMS service as follows:
    service acronis_mms restart

Then go to your Acronis web management portal and re-attempt to update the agent. In our case, as you can see from the screenshot below, it was successfully updated without the need of server reboot.

How to Enable SSH on Debian 11 Bullseye Linux Server

In this tutorial we demonstrate the steps required by a Linux systems admin to install and enable SSH server on Debian 11 Bullseye Linux.

In this tutorial we demonstrate the steps required by a Linux systems admin to install and enable SSH server on Debian 11 Bullseye Linux.

SSH is a network protocol used to administer a server remotely via command line. It’s the Linux alternative protocol to the RDP used in Windows systems.

Here’s what we are going to follow in this article:

  1. Installing OpenSSH service
  2. Checking SSH Server status
  3. Enabling SSH Server on system startup
  4. Troubleshooting Common Issues

1. Installing OpenSSH Service

To install SSH on Debian 11 execute the following commands on your server:

root@localhost:~$ apt update

Since the SSH server is not installed by default, use the following command to do so:

root@locahost:~$ apt install openssh-server

Enter “Y” once prompted to confirm the installation.

2. Checking SSH Server status

Upon installation’s completion, SSH service should be automatically started. To verify this run the following command:

root@localhost:~$ systemctl status ssh

If the SSH service is running, you should see the following on screen:

Loaded: loaded (/lib/systemd/system/ssh.service; enabled; [...]
Active: active (running) since [...]

Pres “q” or “Ctrl-C” to exit and return to the shell.

3. Enabling SSH Server on system startup

To ensure the SSH service is started upon server’s startup, execute the following command:

root@localhost:~$ systemctl enable ssh

You are done! You should be able now to remotely connect on your Debian 11 server via SSH.

Below we are providing the solution for the most common problems you may encounter when trying to install or enable the SSH service.

4. Troubleshooting Common Issues

If you have installed Debian 11 via a network ISO, them during installation you may have answered “No” to the question “Use a network mirror?”. If this is the case, then it means your system was installed without a mirror, or perhaps you didn’t have an active internet connection during installation.

This will cause an incomplete sources.list where repositories for Debian 11 updates and security fixes are not included.

You have to configure a mirror in order to be able to properly install the openssh-server package. Follow these steps:

4.1. Edit the file sources.list as follows:

root@localhost:~$ nano /etc/sources.list

4.2. Include the following 2 lines at the top of the file:

deb http://ftp.debian.org/debian/ buster main contrib non-free
deb-src http://ftp.debian.org/debian/ buster main contrib non-free

4.3. Save and exit the file

4.4. Run the following command to update your system with the newly added repositories:

root@localhost:~$ apt update

Once the update is completed, you can follow the steps in this article from the beginning, starting from the command “apt install openssh-server“.