Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

pkgacct htaccess failed

Discussion in 'Data Protection' started by hinhthoi, Sep 6, 2017.

Tags:
  1. hinhthoi

    hinhthoi Member

    Joined:
    Mar 28, 2017
    Messages:
    13
    Likes Received:
    2
    Trophy Points:
    3
    Location:
    Vietnam
    cPanel Access Level:
    Root Administrator
    Hi,

    When I run the pkgacct to backup account, I got the following error

    Fixing up EA4 .htaccess blocks: /home/username/public_html/.htaccess ^[[1;30;43m(failed)^[[0m Done

    I'd like to ask how to fix this problem? (Why does it need to fix up something of htaccess file? I think the htaccess is working normally)

    Thanks!
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,220
    Likes Received:
    1,376
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    That step of the backup process ensures the .htaccess file is supported if the account is restored on a different environment (e.g. different default PHP version, EasyApache 3). Could you let us know the full contents of the .htaccess file utilized by that account (ensure to remove references to real domain names)?

    Thank you.
     
  3. hinhthoi

    hinhthoi Member

    Joined:
    Mar 28, 2017
    Messages:
    13
    Likes Received:
    2
    Trophy Points:
    3
    Location:
    Vietnam
    cPanel Access Level:
    Root Administrator
    Hi,

    Here is the content of the htaccess file

    <code>

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress
    # BEGIN MainWP
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^wp-content/plugins/mainwp-child/(.*)$ /wp-content/plugins/THIS_PLUGIN_DOES_NOT_EXIST [QSA,L]
    </IfModule>

    # END MainWP
    </code>

    So, if the new server has different default/easyapache 3 versions, the actual htaccess file should still be restored (it may or may not work, but the physical file should be restored, is it correct?)

    Thank you!
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,220
    Likes Received:
    1,376
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    Yes, the .htaccess file should still be included in the archive and restored as-is based on the logs you provided.

    Thank you.
     
Loading...

Share This Page