Search blog

Tuesday, February 12, 2019

[SOLVED] - Alibaba Cloud (ECS) - The Requested URL Could Not Be Retrieved. Unable to Access Website

[SOLVED] - Alibaba Cloud (ECS) - The Requested URL Could Not Be Retrieved. Unable to Access Website


ERROR

The requested URL could not be retrieved

The following error was encountered while trying to retrieve the URL: http://149.x.x.1/

    Connection to
149.x.x.1/ failed.

The system returned: (111) Connection refused

The remote host or network may be down. Please try the request again.

Your cache administrator is webmaster.

Solution

Today after restoring my snapshot to one of my Alibaba Cloud ECS instance; I was unable to access my website from my browser. I tried a lot of this and that but all in vain. Then finally, after much research, I read that the connection was getting refused by my Web Server, in my case the Apache Web Server.

Once I restarted, the Web Server, the website was accessible now.

Command to restart the Apache Web Server:

For Ubuntu:
 sudo service apache2 restart  

For RHEL/CentOS 7:
 systemctl restart httpd  

Friday, January 18, 2019

[SOLVED] - Fix Corrupt NTFS Parition In Ubuntu Using ntfs-3g, Without Using Windows OR fsck

Since yesterday, I've been trying to backup my hard drive using Clonezilla but without any success. Twice I got the following error, when I tried to backup my full hard drive by using Clonezilla.

ntfsclone-ng.c: NTFS Volume '/dev/sda6/' is scheduled for  a check or it was shutdown uncleanly. Please boot Windows or fix it by fsck
& I am know why this issue has cropped up. Few days back I used GParted to expand my main ext4 partition that has Ubuntu installed on it by using a chunk from another NTFS partition.

 >> SOLUTION:


Here's what worked for me. Open your terminal [CTRL+ALT+T]:

1. First list all the partition in your hard drive.

 df -h  

You should be getting a list of parition as shown in the image below. In my case, the NTFS parition is '/dev/sda6.'

[SOLVED] - Fix Corrupt NTFS Parition In Ubuntu Using fsck Without Using Windows
Click on image to enlarge

 2. Now unmount the NTFS partition using the following command. Please note, the command is 'umount' and not 'unmount.'

 sudo umount /dev/sda6  

3. If you do not have ntfs-3g installed, you can install it using the following command:

 sudo apt-get install ntfs-3g  

4. Now run the ntfs-3g command to check/repair your corrupt/problematic NTFS partition:

 sudo ntfsfix -b -d /dev/sda6  
here,
  • b: clear-bad-sectors -- Clear the bad sector list 
  • d: clear-dirty -- Clear the volume dirty flag

5. If the CHECK/REPAIR operation is successful, you should be getting a message as shown in the image below:

Click on image to enlarge
>> Source: Fix corrupt NTFS partition without Windows

Thursday, December 27, 2018

[SOLVED]: Module 'Amasty_Base' from 'app/code/Amasty/Base' has been already defined in 'vendor/amasty/base'

If you have been trying to install Amasty Extension(s) in your Magento 2 installation by using SSH, and run into this error 'Module 'Amasty_Base' from 'app/code/Amasty/Base' has been already defined in 'vendor/amasty/base'', use the solution below to resolve your issue.

This issue occurs if you have installed Amasty Extension(s) manually and the 'Amasty Base' file already exists inside the directory 'app/code/Amasty/Base.' & later when you try to install another Amasty extension using SSH, composer will notice this file in app/code and hence the error. Composer creates the 'Base' directory in the following location 'vendor/amasty/base'.

>> SOLUTION:

1. Go to the root directory of your Magento Installation.
2. Enter the following commands:

1:  composer remove amasty/composer_name_of_your_extension  
2:  rm -rf app/code/Amasty/Base  
3:  rm -rf vendor/amasty/base  
4:  composer dump-autoload  

3. Now INSTALL your Amasty Extension by running the following command:

1:  composer require amasty/composer_name_of_your_extension  
2:  php bin/magento setup:upgrade  
3:  php bin/magento setup:di:compile  
4:  php bin/magento setup:static-content:deploy  

NOTE:

To find the composer name of your extension:
  • Log into your Amasty Account
  • Goto to My Downloads page and look under Composer Name column. See image below to get an idea.
Click on image to enlarge

Friday, December 21, 2018

[SOLVED]: Same Web Property ID Is Tracked Twice | Google Tag Manager | Magento 2

[SOLVED]: Same Web Property ID Is Tracked Twice | Google Tag Manager | Magento 2
Click on image to enlarge

If your Tag Assistant is firing this warning 'Same web property ID is tracked twice' while testing in your Magento 2 site, then it's because you've enabled Google Analytic in your Magento store backend, and also in Google Tag Manager.

SOLUTION: Enable Google Analytics tracking either from your site's backend or by using Google Tag Manager, but not both.

Click on image to enlarge

If you want to use Google Tag Manager for Google Analytics then disable tracking from your site's backend.

Saturday, November 24, 2018

Third Party IT Repair Services & Tech Support Ads Banned By Google Ads

Today while trying to launch some PPC Campaign for a Repair Service for my business, I was met by a RUDE SHOCK due to a policy change in Google Ads.

Each time I tested keywords such as 'iphone repair dubai' 'data recovery dubai', I was greeted with this unfamiliar message 'This candidate is not permitted to show ads in your targeted location.', as shown in the image below:

Click on image to enlarge
After much searching and researching, I finally found out that IT Repair Services, Tech Support, both online or offlline has been banned by Google Ads globally for any 3rd party company. Meaning unless you are the real vendor/manufacturer of the product, you aren't allowed to display Ads providing service or support for that product. Please check the links I've listed below for further clarification. Hard pill to swallow, leave alone digest, but that's what seems to be the case at the moment. And I guess this is the result of all those Indian Tech Scammers, who have been targeting mostly Americans. Because of them now all have to suffer! :-(

This candidate is not permitted to show ads in your targeted location. Google Ads
Click on image to enlarge

References:

Monday, September 3, 2018

[SOLVED] - Thunderbird Could Not Get Password - Fix for Ubuntu/Linux

If you have been getting the following error "Thunderbird Could Not Get Password," and because of this have been unable to log into your Email Account or Send Emails, you can try the solution below that worked for me.

>> Close your Thunderbird Email Client. Goto your Home folder and Press CTRL+H to view hidden folders, or in your Menu, goto View >> Show Hidden Files.

[SOLVED] - Thunderbird Could Not Get Password for Ubuntu
Click on image to enlarge
>> Click on the .thunderbird folder.

[SOLVED] - Thunderbird Could Not Get Password for Ubuntu
Click on image to enlarge
>> Click on the shbh8pem.default folder.

Click on image to enlarge
>> DELETE the following two files as highlighted in the image above:
  • cert8.db
  • key3.db 
>> Now OPEN Thunderbird and press F5 to Send/Receive Emails. If it prompts for a password enter it.

>> Try SENDING an Email from. If it prompts for a password enter it.

>> If the above solution doesn't work, RESTART your system, and repeat the steps above.

>> Your problem should have been resolved now.

Top Magento Hosting:

Top 5 Posts (Weekly)