Reading Time: 4 minutes

The Web Application Firewall (WAF) has the function of protecting web applications from various attacks at the application level such as cross-site scripting (XSS), SQL injection and cookie poisoning etc. In fact, app attacks are the main cause of breach: just think that apps are the gateway to your precious data. With the right WAF in place, you can block all attacks that aim to exfiltrate that data by compromising your systems.

Why do you need a WAF?

Threats on the internet are now commonplace and unfortunately they are evolving in parallel with technology. It therefore becomes essential to have a tool that can protect users and their data.

Network and local firewalls alone can no longer prevent hackers from entering your website. Therefore, having an effective Web Application Firewall (WAF) offers companies and website owners complete peace of mind.

Another important aspect of having a WAF on your website is the time it will save you in the long run. Once you have successfully set up a WAF on your website, you will no longer waste precious time thinking about how to protect it. So a substantial tool to have on your site, especially if Ecommerce.

How does a web application firewall (WAF) work?

A WAF protects web apps by filtering, monitoring and blocking any malicious HTTP / S traffic traveling to the web application and prevents unauthorized data from leaving the app. It does this by adhering to a set of criteria that help determine which traffic is malicious and which traffic is safe. Just like a proxy server acts as an intermediary to protect a client’s identity, a WAF works in a similar but reversed way, called a reverse proxy, acting as an intermediary that protects the web application server from a potentially malicious client.

WAFs can come in the form of software, appliance, or delivered as a service. Policies can be customized to meet the specific needs of the web application or set of web applications. Although many WAFs require you to regularly update your policies to address new vulnerabilities, advances in machine learning allow some WAFs to automatically update. This automation is becoming increasingly critical as the threat landscape continues to grow in complexity and ambiguity.

WAF-operation

What is the difference between WAF – IPS – NGFW?

There are major differences between a web application firewall (WAF), an intrusion prevention system (IPS) and a next generation firewall (NGFW).

An IPS is an intrusion prevention system, a WAF is a web application firewall, and an NGFW is a next-generation firewall. But what are the differences between all of them?

An IPS is a more targeted security product. It is typically based on signatures and policies, which means it can check for known vulnerabilities and attack vectors against a database of established signatures and policies. The IPS sets a standard based on the database and criteria, and then sends alerts when traffic deviates from the standard. In general, IPS secures traffic across a range of protocol types such as DNS, SMTP, TELNET, RDP, SSH, and FTP. IPS typically operates and protects levels 3 and 4.

A web application firewall ( WAF ) protects the application layer and is specifically designed to parse every HTTP / S request at the application layer .

You can think of a WAF as an intermediary between the user and the app itself, which analyzes all communications before they reach the app or the user. Traditional WAFs ensure that only permitted actions (based on security criteria) can be performed. For many organizations, WAFs are a reliable first line of defense for applications.

A Next Generation Firewall (NGFW) monitors outbound traffic on the Internet, between websites, email accounts, and SaaS. Simply put, it protects the user (compared to the web application). An NGFW will enforce user-based policies and add context to security policies as well as add features such as URL filtering, antivirus / antimalware, and potentially their own intrusion prevention systems (IPS). Although a WAF is typically a reverse proxy (used by servers), NGFWs are often forward proxies (used by clients such as a browser).

What is the difference between WAF on network, host and cloud?

A WAF can be implemented in several ways – it all depends on where your applications are deployed, what services you need, how you want to manage it, and the level of flexibility and architectural performance you require. Do you want to manage it yourself or do you want to outsource this management? Is it a better model to have a cloud-based option or do you want your WAF to reside locally? Your options are listed below.

WAF on host

This WAF can be integrated into an application software and allows for different customizations. If we want to find a disadvantage, we can identify it in the fact that this type of WAF consumes a lot of local server resources. Last but not least, the costs related to maintenance and not very easy implementation are certainly to be considered.

WAF over the network

This is the most expensive option that also requires some maintenance. However, being installed locally, it has the advantage of significantly reducing latency.

WAF on the cloud

They are a fairly affordable and easy to implement solution. Generally, users pay a monthly or annual fee, which is not too expensive and can use the service in complete peace of mind. This type of WAF also has the advantage of always being up to date and thus protecting in an even more effective way.

Conclusion

As you have seen, the WAF is an absolutely necessary tool for safeguarding the security of the data of the users of your site. There are several possibilities related to this aspect and you can choose the best condition that can best suit your needs.

If you need advice in this regard, contact us and we will be happy to find the best solution for you.

Reading Time: < 1 minute

There are many versions and editions of Magento 2. Sometimes you need to know which version of Magento you are using, for example to schedule the upgrade.

Here are some tricks, which will show your current Magento 2 version.

Special page for Magento 2 version

The easiest way to know which version you are running without logging in is this interesting page, which features every Magento store.

Just visit this URL: http://your_store.com/magento_version

From here you will come to a simple page where you will find your version of Magento 2.

However on this page, you will only be shown the major version number. If you want to know the minor version as well, check out the following methods.

Backend Footer

Another simple way to check the version is available, when you have access to the backend. Here’s what you need to do:

  • Log into your shop’s backend and open any page, such as “Orders”.
  • Pay attention to the bottom right section – you will see the current Magento 2 version.

SSH / CLI command

Another simple method is a special CLI command. Here’s what you need to do:

  • Log into your store’s SSH / CLI and go to the root of your store.
  • Run the bin / magento –version command

You will see the log, which describes the current version of the Magento CLI, which corresponds to your current Magento version:

Magento CLI version 2.2.3

Composer installation file

If your Magento was installed via Composer, you have another method to check the Magento 2 version. Here is what you need to do:

  • Log into your store using FTP / SSH and go to the root of your store.
  • Open the composer.json file .
  • The version property in the first data structure contains the precise version of your Magento 2
Reading Time: 3 minutes

There are now so many CMSs for E-Commerce, such as Shopify, Woocommerce, Magento, etc. Among these platforms however, Magento can be considered the most popular and widely used e-commerce platform . This is because it is the most robust, flexible and best performance oriented alternative . As a result, Magento 2, the latest update of this platform, becomes the first choice for most e-commerce startups and online stores.

However, nothing is perfect… Precisely because Magento is full of great configurations, likewise, it still has several flaws and the most obvious one is related to speed. In this article, we see what are the reasons that make Magento 2 slow and how to speed it up.

Why is Magento 2 slow?

Well this is definitely the first question to ask us, just to understand where the problem can be.

The speed of Magento 2 is not slow by default, but rather the default store is robust and runs smoothly. In fact, most of the slow interface problems and high loading times are due to bad behavior and lack of knowledge in website optimization. Once you can’t meet the basic requirements for running a store on Magento, such as using inappropriate extensions or not enabling the right plugins, your store’s speed will definitely slow down. If you don’t do something to fix this, your store could lose a large number of potential customers.

How to speed up Magento?

There are various ways that could help you increase the speed of your Magento store . You need to know some Magento speed best practices to run a Magento website smoothly. Below are several ways you can refer to to optimize your Magento website:

Step 1: Optimize server and system requirements

The server and system requirements can be considered as the two most important factors that can help you increase the speed of your Magento 2 website.

Server Requirements: Since Magento is quite a powerful store, you can choose instead a shared hosting for Magento, a dedicated server or VPS hosting .

System requirements: click here .

Step 2: Update to the latest version of Magento 2

When it comes to optimizing Magento speed , one of the easiest ways you can’t forget to use is to update it to the latest version . Each time Magento releases a new version, the performance, as well as other changes, will be significantly improved. As a result, I highly recommend that you update your store version to the latest to improve the speed of your store site.

Step 3: Turn on Varnish Cache

There are several practices that need to be implemented to speed up the Magento site including caching.

Below you can see how to enable Varnish Cache to improve Magento 2 loading speed.

From the admin panel, go to Store> Configuration> Advanced . In the Advanced tab , click on System , you will see the Full Page Cache section . In this section, you change the Application Catching value to Varnish Caching .

Step 4: Configure Memcached

Another method to speed up Magento 2 stores is to reduce database load. And the way to do that is to configure Memcached .

Step 5: Enable categories and flat products

One of the most common reasons that slow down your Magento 2 site is the database reading speed. To fix this, you can enable Flat Catalog.

Here’s how to do it:

First, go to the admin panel of your Magento store. From here go to Store> Configuration> Catalog . Then click on Catalog located on the Catalog tab. Here you will see the Storefront section . Here there are two fields Use Flat Catalog Category and Use Flat Catalog Product and on these set Yes .

Step 6: Optimize Javascript and CSS

Another reason that leads to Magento 2 slow speed is Javascript and CSS .

Here’s how we can remedy the problem.

From the admin panel, go to Store> Configuration> Advanced . On the Advanced tab , click Developer . In the Javascript Setting section , change the values ​​in the three fields Merge JavaScript File, Enable JavaScript Bundling and Minify JavaScript File, setting them to Yes . Then, change the Merge Css File and Minify CSS file fields in the CSS setting section, setting these fields to Yes .

Step 7: Configure the Content Delivery Network

You can also configure the Content Delivery Network to improve the speed of your Magento store.

From the admin panel, go to Store> Configuration> General . Click on Web located under the General tab . Then, you can explore the Base URL (Secure) section and add the HTTPS ULRs

Step 8: Use a good theme

I highly recommend you to use a light and fast Magento theme. This indeed can help you improve Magento 2 loading speed significantly.

Step 9: choose extensions

Many users tend to use extensions without verifying or confirming their safety. For example, if they contain bugs, the speed of Magento will surely suffer. That’s why you should always use bug-free third-party extensions.

Step 10: Optimize the images

There are tons of product images on your shop website. This may slow down the speed of Magento if these images are not optimized properly. Here are some key points you can use in image optimization:

  • Images must be compressed.
  • Your shop logo must be in PNG or SVG format.
  • The product image must be in JPEG format.

Conclusion

Bottom line, why is Magento 2 so slow?

As you have seen, there are various ways you can use to speed up your Magento 2 speed . It is up to you to choose the most suitable one for your store. What you need to keep in mind is that a slow sit will only drive your users away. You must therefore focus on finding the best solution to make your Store fast. In this article you have seen some ways that you can use to get more speed.

Check if your site is slow

Reading Time: 3 minutes

Having a good hosting service , you know, can make a difference. In fact, if our site is fast, it immediately provides the answers the customer is looking for, most likely the customer will remain on our site. So we can actually say that hosting can affect conversions.

It’s not just about hosting of course. The path is however more complex, because it also involves other factors, such as the usability of the site or even its structure, its graphics. In short, all this influences what is defined as Conversion Rate Optimization , or more simply CRO. This parameter does nothing but define the conversion rate optimization of your website. Especially if we are talking about Ecommerce, this fact becomes fundamental, because it can make the difference between a sale and not.

So you understand that it becomes very important to be able to provide our users with a site that is effective and above all responds quickly to the stimuli of those who surf it. So let’s see in this article how secure, fast and reliable hosting can really make a difference!

Secure hosting

The security of your data and those of customers is a fundamental and indisputable aspect, especially when it comes to online sales. We must be able to guarantee full safety to those who browse our store. Good hosting also means secure hosting. The primary parameter is definitely an SSL Certificate. This in fact allows you not to have that annoying message that says “site not safe”.

secure-hosting-hostgento

It is clear that especially if we are making an online purchase, if we run into a site with the word “not safe”, we would probably desist from the purchase. Who wants to buy on a site that is not deemed safe? So keep this particularly important element in mind.

Effective hosting

Have you ever understood that in a moment of very high traffic on your Ecommerce, perhaps during the periods corresponding to holidays or sales, your site crashes and becomes unreachable? Do you know how many sales you can lose? But above all, think about reputation too! A site, in particular E-Commerce, must never find itself in a similar situation, because it can lead the user to no longer have faith in the seller.

Assuming that with a good hosting, consciously chosen according to the traffic needs of the site, these events are rare, but these can happen. So when you choose your hosting, make sure that the provider has an excellent support service and that they can intervene immediately where problems of this type arise.

Fast hosting

As I mentioned a few lines ago, a site, especially if Ecommerce, must know how to respond quickly to user requests . This means that if a user clicks on a page, it must load quickly, otherwise the user leaves. Not to mention that from May 2021, the issue of speed becomes an important parameter for Google. If you want to know more read our article on the Google Core Web Vitals .

hosting-fast-hostgento

Basically, a fast site definitely converts more! If the site is slow, people go somewhere else. Not to mention that in addition to Google, as I told you before, SEO also rewards fast sites. So don’t underestimate this last aspect if you want a site that truly converts.

Conclusions

Basically having a fast site is just the tip of the iceberg to increase conversions and therefore sales. But without a site with good performance from this point of view, we certainly cannot be competitive. For this we recommend that you buy a hosting that reflects your traffic needs, that we have good assistance and that allows you to have full security.

If you are looking for a hosting with all these features, contact us and we will find the right solution for you!

Reading Time: 2 minutes

Varnish Cache is an open source web application accelerator (also known as HTTP accelerator or HTTP reverse proxy caching). Varnish stores (or caches) files or file fragments in memory; this allows Varnish to reduce response time and network bandwidth consumption on future equivalent requests. Unlike web servers like Apache and nginx, Varnish was designed to be used exclusively with the HTTP protocol.

Magento 2.4.2 is tested with Varnish 6.4. Magento 2.4.x is compatible with Varnish 6.x
Magento itself strongly recommends using Varnish in production. Built in full page caching (in the file system or database) is much slower than Varnish and Varnish is designed to speed up HTTP traffic.

You can find more information in the link below:

Varnish Topology Diagram
The following figure shows you a basic view of Varnish in Magento topology.

In the figure above, you can see how HTTP requests from users on the Internet result in numerous requests for CSS, HTML, JavaScript, and images (collectively referred to as resources). Varnish stands in front of the web server and forwards these requests to the web server.

When the web server returns the resources, the cacheable resources are stored in Varnish. Any subsequent requests for these resources are satisfied by Varnish himself (which means that the requests do not reach the web server). Varnish then returns the cached content extremely quickly. The results are faster response times to return content to users and a reduced number of requests that need to be fulfilled by Magento .

Resources cached by Varnish expire at a configurable interval or are replaced by newer versions of the same resources. You can also clear the cache manually using Magento Admin or the magento cache: clean command .

Process overview

In this section we will see how to initially install Varnish with a minimum set of parameters and test its operation. Then you will export a Varnish configuration from the Magento admin and test it again.

The process can be summarized as follows:

  • Install Varnish and test it by going to any Magento page to see if you are getting HTTP response headers indicating that Varnish is working.
  • Install the Magento software and use the Magento Admin to create a Varnish configuration file.
  • Replace your existing Varnish configuration file with the one generated by the administrator.
  • Try everything again.

If there is nothing in your <magento_root> / var / page_cache directory, you have successfully configured Varnish with Magento!

Unless otherwise specified, you must enter all the commands discussed above, as a user with root privileges.
This applies to Varnish on CentOS and Apache 2.4. If you are setting up Varnish in a different environment, some commands may be different. Consult the Varnish documentation for more information.

Problems encountered

In this process some problems can arise, let’s see which ones:

  • Varnish does not support SSL
    Alternatively, use SSL termination or an SSL termination proxy .
  • If you manually delete the contents of the <magento_root> / var / cache directory , you need to restart Varnish.
  • Possible error while installing Magento:
Error 503 Service Unavailable
Service Unavailable
XID: 303394517
Varnish cache server


If this error occurs, edit default.vcl and add a timeout to the backend as follows:

backend default {
    .host = "127.0.0.1";
    .port = "8080";
    .first_byte_timeout = 600s;
}



























Reading Time:  3 minutes
VPS, Dedicated or shared: how to choose the right hosting solution for our needs?


We see below in detail the solutions offered on the market and the meanings linked to these three types


    

  1. Shared Hosting
    2. 

  2. Dedicated Hosting
    3. 

  3. VPS hosting
    4. 



Shared Hosting




 


A shared hosting is when within the same server machine are hosted more websites. This therefore implies that all the resources of the machine are divided among all the sites present. Therefore the performance of each of them may not be the best if the server is not optimized and configured correctly. Basically a shared hosting service occurs when the computational resources (CPU and RAM) are shared resources with other clients on the same server / node.


The problem that can sometimes happen is that one site’s traffic spikes can slow down or even block others. Also in terms of risks, shared hosting is definitely not the best choice for medium to large projects, but it is certainly good to start.


This type of hosting is generally recommended for small sites that do not have a lot of traffic or large revenues, instead it is not recommended for sites that have thousands of users per day and to whom a hosting block could lose large sums of money. However, a big advantage of shared hosting is definitely the price,  which is clearly much lower than dedicated hosting. If well configured and well optimized, even shared hosting can offer the experience of dedicated hosting as long as you buy a package that offers the minimum necessary to run Magento2 at its best: from our analyzes, the minimum cut in CPU and RAM is of 2 cores and 2 GB of ram.


Dedicated Hosting


With this type of hosting, on the other hand, unlike shared hosting, you have the entire physical server at your disposal . This therefore has some advantages especially in terms of machine customization. It is therefore a hosting service where every type of resource (CPU, RAM, DISK, BAND) is 100% dedicated to us.


Why choose dedicated hosting over a shared solution? Surely the main advantage is to have all the resources at our disposal and it is recommended for medium and large sites that need dedicated resources . Keep in mind, that unlike the shared one, dedicated hosting needs maintenance and an expert system administrator to be able to manage it and to be able to monitor it.


 




 


Furthermore, the costs of the dedicated server , compared to shared hosting, are much higher as in addition to the cost of the machine, an expert system administrator will be needed to manage it, to configure it and to optimize it for the software that will be hosted (in this case Magento 2).


VPS hosting


VPS stands for Virtual Private Server or a virtual Server dedicated to us where the computational capacity (CPU and RAM), disk and bandwidth are 100% always available to us. Furthermore, being a virtual Server, the basic VPS can scale in “vertical” or by adding CPU and RAM through a reconfiguration of the plan you have purchased and a subsequent reboot. So where is the problem with VPS? In the storage , or rather in the disk where the data is stored, or more simply the space.


The cost of VPS here too is very variable, it depends on the “cut” it is positioned at an intermediate level between the dedicated and the shared.


Conclusion


As we have seen there are different solutions for choosing the hosting of your project, there is no one-size-fits-all solution. So, when making your choice you will need to take the following into consideration:


    

  • Budget available
    • 

  • Number of products
    • 

  • Number of categories
    • 

  • Number of stores and store views
    • 

  • Based on the visits I expect to receive
    • 



Surely you can start from the cheapest solution and evaluate in the future a switch to more complex solutions such as dedicated / VPS.


However, I recommend that you rely on an expert consultant or a company specialized in Hosting for Magento 2 , who can advise you on the best solution for your project.


If you need help choosing your hosting, don’t hesitate to contact us !
























Reading Time:  3 minutes
As you know, in May 2021 there will be a new Google update, namely Google Core Web Vitals , in which the speed of a site becomes even more a fundamental element for the success of an online business.


The question of speed has always been a key point when it comes to websites, especially e-commerce. In fact, in this type of site, having a browsing speed, without hitches and blocks, is necessary to prevent the user from leaving the site. Each process within an E-Commerce must in fact flow continuously and immediately, to allow the user to take advantage of an impeccable user experience.


Much of the fluidity and speed of a site is related to the type of hosting we are going to get. Optimized hosting with certain features can make a difference, especially when it comes to Magento . in fact, this CMS, although spectacular from the point of view of configurations and customizations, still requires hosting structures of a certain type.


However there are also other tools and parameters to consider to increase the speed of Magento 2 . Today we will see in this article, two specific modules , made just for this.


JS & CSS Compressor + Image Optimization


L ‘ performance optimization of a website is a major e-commerce-related trends. Many brands are investing in performance optimization, as they know for a fact that store performance affects the shopping experience and overall customer satisfaction.


JS & CSS Compressor + Image Optimization is a powerful Magento extension, for reducing the number of requests sent to a web server, optimizing images, merging and minifying JS and CSS files. Additionally, it supports GZIP, has HTML minification, slow image loading, Javascript deferred parsing, and image file merging capabilities.


Studies say customers leave a website if a page doesn’t load in 4 seconds. Keep your users engaged by providing a fast performing Magento store.


Search engines don’t like slow sites either. Website speed is a ranking factor in Google search.


For this, your site must ensure your customers an optimal user experience. This Potato Commerce module allows you to improve your Google Page Speed ​​and GTmetrix performance scores.


In fact, through this extension you can:


    

  • Image optimization feature
    • 

  • Optimize JPEG, PNG and GIF images
    • 

  • Merge images (new and unique feature)
    • 

  • Speed ​​up image loading
    • 

  • Set the image size
    • 

  • Offer scaled images
    • 

  • Advanced management of image optimization
    • 

  • Automatic image backups
    • 

  • Check the image optimization status
    • 



… and much more!


Lifetime free support and updates.


speed-magento2


According to Httparchive.org, 64% of the bytes on the page are images. So it goes without saying that image optimization is the key way to significantly improve web page performance. Image optimization is a process that reduces file size and eliminates excess information. As a result, the files are smaller in size and load faster.


This extension has an important image backup function in the “media” and “skin” folders. Image backup starts before the image optimization process. If necessary, you can exclude specific images from optimization.


Go to extension >>


Google Page Speed ​​Optimizer


Google Page Speed ​​Optimizer for Magento 2  by Amasty, improves the performance of web pages to place your store at the top of the Google search rating. Increase your online store traffic by optimizing speed and get an endless stream of new visitors!


Thanks to this extension you can:


    

  • Optimize the structure of the JS, CSS and HTML code
    • 

  • View pages faster thanks to the WebP image format
    • 

  • Resize and crop images for mobile devices
    • 

  • Use Smart JS Bundling and Server Push
    • 

  • Check the results using the built-in diagnostic tool
    • 

  • Enhance user experience with the help of blazingly fast shop page loading
    • 



It is no secret that stores with slow loading speeds are affected by the Google RankBrain algorithm. The SEO performance of Magento 2 stores is crucial, as you know, nobody wants to search for products beyond the first page of the search results. The websites featured on the first page of the search results receive nearly 95% of the web traffic, leaving only 5% for the remaining pages. Ultimately, if your store isn’t optimized well, Google will penalize it and you won’t get as many potential customers as possible.


Google nowadays takes page speed into consideration as the main ranking factor for searches on mobile and desktop devices. Pages that offer the slowest user experience are out of the game. The same standards of speed touch all developers. This means that only stores with fast loading speed and optimized performance will get the highest rankings in a Google search ranking.


Amasty’s Magento 2 speed optimization extension makes a store’s performance better for both users and search engines. Visitors will not leave your shop due to long page loading. Meanwhile, Google Rankbrain will index your store faster and take you to the highest rankings in Google’s search results. Don’t miss the opportunity to increase conversions!


Go to extension >>


Conclusions


Both of these two extensions can be a valid help in speeding up your E-Commerce, but as I told you, having a good hosting is also essential. For this reason, if you need an optimized hosting solution, contact us and we will be happy to identify with you the best solution for your needs.
























Reading Time:  2 minutes
Since Magento 1 went to end of life, we have noticed an increase in attacks on Magento 1, mainly targeting / downloader. Just lately more than 2000 Magento 1 stores around the world have been hacked.


Many other attacks then occurred some time after the Magento EOL. In this case, many victimized shops had never had a history of security incidents. This suggests that a new attack method was used to gain server access to all of these repositories. This episode may be related to the Magento 1 0day (exploit) that went on sale at the time.


User z3r0day had in fact announced on a hacking forum to sell a Magento 1 “remote code execution” exploit method, including the instruction video, for $ 5000. Seller z3r0day pointed out that since Magento 1 was In End-Of-Life, Adobe would no longer provide official patches to fix this bug, which made this exploit even more damaging for store owners using the legacy platform.


Obviously this was just one of the many episodes that have occurred from the Magento 1 EOL to date. It therefore becomes essential to have the right strategy in order to better protect your Magento 1 site, perhaps waiting for the transition to Magento2.


But how can we do?


How to protect Magento from attacks?


To protect your store from this and future exploits, there are a few basic steps you can take.


Change the name of the backend panel


Magento 1: The default “admin” is defined in the app / etc / local.xml file in admin → router → adminhml → args → frontName . Turn it into something you can easily remember, but hard for others to guess. So don’t use “control” or “admin123” or “manage”.


Empty the cache in the backend via: System → Cache Manager . Or run in SSH: magerun cache: flush


Magento 2: This step is not required, as Magento generates an obfuscated backend name during installation.


Protect / downloader and / rss


Magento 1 uses / downloader as a way to install programs via Magento Connect Manager. This link is a standard Magento URL, making it an easy target for attacks. While you will probably never use this folder, its presence is essential for installing (future) patches. So instead of renaming, we recommend installing IP access control (an “IP whitelist”).


NB. The / rss endpoints can be reached in various ways, including (for example) via /index.phprss/catalog/notifystock.


Install the adaptive filter


Hackers who launch attacks on your store are likely to use other malicious tactics as well. Therefore, it is recommended to block hacking sources as soon as they are identified. This is called an adaptive filter or intrusion prevention system (IPS). This step requires access to the platform / server, so it is usually done by the hosting provider.


Relying on MageShield


Last but not least, if you want to be sure that your Magento 1 site is always safe and updated, you can use MageShield , our Ecommerce protection service in Magento 1.


With MageShield your site will always be safe and secure!


MageShield f adorns a range of features designed to protect both your website and your company’s reputation:


    

  • Malware scan
    • 

  • Automatic malware removal
    • 

  • Vulnerability Scanning
    • 

  • OWASP protection
    • 

  • Firewall
    • 

  • Automated quick setup
    • 

  • Content Delivery Network (CDN)
    • 



If you are interested in the service:



























Reading Time:  3 minutes
If you are a Magento developer, sometimes you happen to have to move a Magento eCommerce from one host server domain to a new host server domain or from one directory location to another directory location.


Migrating Magento to a new server is quite simple once you understand how to do it. Let’s see, in this article, how to do this. Let’s say that to do a migration, there are two different ways. Let’s see them in detail.


How to migrate Magento: method 1


    

  1. Back up the files to the testing server.
    
Go to the admin backend of your test site and update Cache by System> Cache Management. Then download and save the entire Magento store root directory via File manager or FTP tools.
    2. 

  2. Magento database export.
    
Enter the phpmyadmin database area of ​​your server control panel and EXPORT your Magento store database in the format “name.sql.zip”.
    3. 

  3. Move the magento files to the new server.
    
Upload the root directory (all files) of your test Magento store backup taken in step 1 to the new server domain folder.
    4. 

  4. Import the database to the new server.
    
Go to your new phpmyadmin host account and create a new database, database user and database user password. Then open the database sql file saved in step 2 with a text editor and change the mention of the database name to the new database name, save it. Then import the database backup “name.sql.zip” saved in step 2 into this new database.
    5. 

  5. Update the database dump file.
    
The next step is to edit the database dump file. To do this, go to the magento live site folder, find the “app / etc / local.xml” file and enter the most recent database details that are created in step 4.
    6. 

  6. Edit the base URL database table. The next step is to replace the old domain name of the server with the new domain name. For this go to your new phpmyadmin magento server database and edit the core_config_data table as shown below.
    
– web / unsecure / base_url> http://www.newdomain.com/
    
– web / secure / base_url> http://www.newdomain.com/
    7. 

  7. Update the cache and re-index the data.
    
The final step is to clear the cache. Go to your sites admin panel (Log in with test site username and password) System> Cache Manager> Select all and disable cache management. Then navigate through System -> Index Management. Select the fields under Status – “REINDEX REQUIRED”, then choose “Reindex data” from the drop-down menu and click Submit or delete all files in the new site’s “var / session” and “/ var / cache” folders.
    8. 



Take a look at the frontend of your new Magento ecommerce store.


How to migrate Magento: method 2


The only problem with this method is that both Magento setups must be of the same version. But let’s see in detail.


    

  1. Go to the backend of your test site and update the cache from the system> cache management. Then make a backup of the test site phpmyadmin database by exporting the database in the format “dbname.sql.zip” (or any suitable format).
    2. 

  2. The next step is to backup the following folders on the test site on your system
    
– Contents inside the frontend folder (app \ design \ frontend)
    
– Contents inside the frontend folder (skin \ frontend)
    
– Catalog and other folders requests (media \ catalog)
    3. 

  3. Install a new Magento store on the new server.
    4. 

  4. Go to the server’s new phpmyadmin database and drop all tables.
    5. 

  5. Unzip the backup database in the first step “dbname.sql.zip” and import the file “dbname.sql” into the new database.
    6. 

  6. Copy the folders below into the respective new Magento server directory
    
– Contents inside the frontend (app) folder in app \ design \ frontend.
    
– Contents inside the frontend (skin) folder in skin \ frontend.
    
– Catalog and other required folders in media \ catalog, xx \
    7. 

  7. Change the base URL mention table (core_config_data table) to new magento.
    
– web / unsecure / base_url> http://www.newsite.com/
    
– web / secure / base_url> http://www.newsite.com/
    8. 

  8. Go to your site’s admin panel System> Cache Management> Select All and disable cache management. Also, index the data by going to System -> Index Management. Select the fields under Status – “RE-INDEX REQUIRED”, then choose “Re-index data” from the drop-down menu and click Submit.
    9. 



Check out your new Magento store.
























Reading Time:  2 minutes
As you surely know, in June 2020 support for Magento 1 ended , but this however did not dictate the end of all E-Commerce made with this version of the CMS.


It would have been unthinkable to preclude the possibility for all Magento 1 E-Commerce companies to continue their business and force them to migrate to Magento 2. Also because the transition from Magento 1 to Magento 2 is not a simple update!


But it is necessary to rebuild the whole platform from scratch, because the two versions are completely different in terms of structure and architecture. The timing and costs to make this step are quite substantial.


Magento EOL why was it such an important date?


The End Of Life (EOL) of Magento 1 was still an important date, especially since not having support for M1 anymore, can cause serious security problems . And to be honest, having an E-Commerce that uses a technology now not supported by the manufacturer, involves going against the PCI DSS regulation.


The problem is therefore there and you need to know how to deal with it, to have a safe and secure store.


Your Magento 1 safe with MageShield


The problem of security as you have seen is an element to be taken into great consideration, especially when it comes to managing sensitive data. An Ecommerce, even more than another activity, must be able to guarantee that its own data and that of its customers are always safe and that in general there are no other vulnerabilities on the site.


For this purpose, MageShield is born , a service that allows you to maintain an advanced level of security on your Magento 1 store, also waiting for your possible transition to Magento 2.


MageShield is able to protect your E-Commerce, housed on our servers perfectly optimized for Magento. Your site will thus be protected from any security attacks .


With this service you can keep your Magento 1 site, even after this fateful EOL date, always having security updates and suitable technologies available.


Features of MageShield


With MageShield your site will always be safe and secure!


MageShield f adorns a range of features designed to protect both your website and your company’s reputation:


    

  • Malware scan
    • 

  • Automatic malware removal
    • 

  • Vulnerability Scanning
    • 

  • OWASP protection
    • 

  • Firewall
    • 

  • Automated quick setup
    • 

  • Content Delivery Network (CDN)
    • 



Why should you use MageShield?


MageShield is not simply an additional service for all e-commerce that have decided to stay on Magento 1, but it is what an E-Commerce M1 needs.


With the end of support for Magento 1 in fact:


    

  •  No more features and security patches will be released
    • 

  •  Magento 1 software will become vulnerable to threats
    • 

  •  your safety and that of those who buy on your shop will not be guaranteed
    • 

  •  you will risk heavy fines because your shop will no longer be compliant with international regulations governing credit card transactions
    • 



What does MageShield do?


MageShield protects your shop from vulnerabilities that Magento 1 may have in the future by providing always updated security patches.




Thanks to this service it is possible to solve any compatibility problem between Magento 1 and future versions of PHP and MySQL.




You will also have a Complete Report of your current security situation at your disposal.




Finally, you can have immediate protection from the moment of installation with the integration of WAF technology.






If you are interested in the service:



























🚀 Give your website a boost!
Try bhoost hosting for free for 30 days 





Free Trial 30 days