Search blog

Monday, February 17, 2020

Allow Clemetine Remote App Access in UFW [Uncomplicated Firewall]

If you would like to use the Clementine Remote App with your Ubuntu system, then try the following steps:

Allow Access to Clementine Remote App in UFW [Uncomplicated Firewall]
Image 1
 
Image 2
  1. Open Clementine
  2. Open Preferences using the keyboard shortcut (CTRL+P) or open on Tools >> Preferences from the Clementine menu
  3. Click on Network Remote tab on the left, and make note of the following two values:
    • Port
    • Your IP Address
  4. In my case, my IP address was 192.168.0.113
  5. Open your terminal, and enter the following command:
    sudo ufw allow from 192.168.0.0/24 to any port 5500. Please note that if your IP is, say for example 192.168.1.20, then your terminal command should be as:
    sudo ufw allow from 192.168.1.0/24 to any port 5500
  6. Download the Clementine Remote app by clicking on the following link http://bit.ly/39CTNCo Play store. Now open the app, and you should be seeing a screen as shown in the Image 2 above. Enter your IP address & click on connect.
  7. Now you should be able to remotely access your Clementine music player from your Clementine Remote App

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 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
>> REF: 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

Top 5 Posts (Weekly)