5 Common Magento 2 Issues That Can Ruin Your Store


When running a Magento store, you will definitely face plenty of problems. This article will show you 5 prevalent Magento 2 issues that most of the stores will meet with corresponding detailed solutions.

Configuring And Running Cron

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

– Catalog price rules

– Newsletters

– Generating Google sitemaps

– Customer Alerts/Notifications (product price change, product back in stock)

– Reindexing

– Private sales (Magento EE only)

– Automatic updating of currency rates

– All Magento e-mails (including order confirmation and transactional)

We recommend you to run the cron as the Magento file system owner. Do not run the cron as root. Also, you must avoid running the cron as the webserver user.

Besides, Magento depends on the proper cron job configuration for many important system functions, including indexing. Failure to set it up properly means that Magento won’t operate as expected.

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

Page Caching

The second Magento 2 issue that we want to mention looks simple but fundamental – page caching. Although this is one of the most effective ways to improve the performance of web applications, many users usually ignore it. There are two ways to cache: client-side (browser) and server-side.

In addition, there are two types of content: public (available to multiple customers) and private (specific to one customer).

Magento page caching is synonymous with full-page caching; in other words, we cache the entire page. The Magento application gives you the following options:

– The default caching mechanism which stores cache files in any of the following:

+ On the file system. You don’t need to do anything to use file-based caching.

+ Database

+ Redis

– Varnish (recommended)

By deleting or clearing the cache, you can solve many issues in Magento.

The cache folder is located in your Magento root directory  /var/cache. To clear the cache, simply delete the folder and then go to Magento admin => System > Cache Management and clear all Cache.

Configuring Magento With A New Domain

Rebranding or changing the goods you sell may lead to a need for a change in the domain name of your store. Therefore, we will help you reconfigure your Magento store to open via a new domain.

Before you continue, make sure your new domain is properly configured and pointed to the servers of the hosting provider on which your current Magento 2 installation resides.

Now you will need to login to the admin area of your Magento 2 website and navigate to the Stores =>Configuration section from the main admin panel.


Go to the General =>Web tab from the navigation menu on the left and expand the Base URL section.


If your current domain is example.com and you wish to change your Magento 2 to be accessible via your new domain example22.com, you must change the URL here.


You will also need to expand the Base URL (Secure) section and make the same change on the URL.

Once you are ready, hit the Save Config button at the top right corner of the page to apply the changes and make Magento 2 open via your new domain.

Indexing both HTTP and HTTPS versions of the website

When you index the HTTP and HTTPS versions of the website, one of them is considered as duplicate content.

To avoid this mistake, you should index the preferred version, and the other version of the same URL should point to the HTTPS version with rel canonical. For example, HTTPS is the preferred version for your website, then in the HTML coding, the HTTP version should have the rel canonical pointing to HTTPS and vice versa.

Handling Troubles With Magento 2 Extensions

Nearly all owners installed some extensions to enhance functions for their Magento stores. However, these extensions can also bring about a lot of handicaps if you ignore to check the following issues:

– Compatibility with the Magento versions: Before you download any of our Magento 2 extensions, let’s check whether it is compatible with the Magento version you are currently using. For example, a lot of extensions made for M 2.1 maybe not work for 2.0.

Installation steps: Follow all the steps provided in the installation guideline

Latest versions of Magento 2 extensions: If you want to use any of the extensions, make sure to download the latest release of that extension for better features.

Clearing Static Cache: Once you have installed the extension, don’t forget to clear the static cache before you actually use the extension on your store. You can do that by going through System => Cache Management => Flush Static Files Cache.

– Static Content Cache: After making any changes to settings or extensions, make sure you clear the static content cache. This will make sure that the front-end is working on the new settings and not the old CSS files.

Admin Sessions Problems: To solve the admin sessions issue, try to log out and then login again to your admin panel.

Functionalities: Before you download, install and apply the extension to your store, check the functionalities carefully as they may clash with the functionalities of the existing extension on the store.

The right place to copy the extensions: The extensions should be copied to the correct folders to work properly. For example, the MConnect Media’s extension will go under app/code/Mconnect/MODULE_NAME.

System requirements: Before you run Magento 2, confirm that you have had all the system requirements.