• Resolved rangrsite

    (@rangrsite)


    I’m attempting to migrate from Bluehost to Byethost. I have tried restoring from the backup link below several times with the same failure.

    Regarding the message, PHP CLI is disabled in your php.ini – I’m not sure if this is in reference to the target or the source. Regardless, I tried looking for a php.ini file in both the source and the target directories to see if I could enable this, but I couldn’t locate one.

    Debug Code: BMI-vXVfQvpB-81140

    Backup URL: https://www.rangr.us/?backup-migration=BMI_BACKUP&backup-id=BM_Backup_2023-05-13_20_07_05_L5a80GsYwuVZjgbz.zip&t=1684008536493

    Target Website URL (where I’m attempting the restore): http://rangr.byethost18.com/

    Log File:

    [STEP] [2023-05-13 20:17:00] Initializing restore process
    [STEP] [2023-05-13 20:17:01] Looking for PHP CLI executable file.
    [WARN] [2023-05-13 20:17:01] PHP CLI is disabled in your php.ini file, the process may be unstable.
    [INFO] [2023-05-13 20:17:01] Backup & Migration version: 1.2.8
    [INFO] [2023-05-13 20:17:01] Creating lock file
    [STEP] [2023-05-13 20:17:01] Initializing download process
    [SUCCESS] [2023-05-13 20:17:01] Downloading initialized
    [STEP] [2023-05-13 20:17:01] Downloading remote file...
    [INFO] [2023-05-13 20:17:01] Used URL: *****.zip&t=1684008536493
    
    [DOWNLOAD GENERATED] File downloaded on (server time): 2023-05-13 20:22:08
    [DOWNLOAD GENERATED] Last update (seconds): 4 seconds ago 
    [DOWNLOAD GENERATED] Last update (date): 2023-05-13 20:22:04 

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter rangrsite

    (@rangrsite)

    Debug Code: BMI-ZVTfuOOF-07225

    I uploaded the actual migration file and tried to restore using that, but it failed again. This time at a different location:

    [INFO] [2023-05-13 22:13:52] Web server: Apache
    [INFO] [2023-05-13 22:13:52] Max execution time (in seconds): 60
    [INFO] [2023-05-13 22:13:52] Memory limit (server): 128M
    [INFO] [2023-05-13 22:13:52] Memory limit (wp-config): 128M
    [INFO] [2023-05-13 22:13:52] Memory limit (wp-config admin): 128M
    [SUCCESS] [2023-05-13 22:13:52] Restore process initialized successfully.
    [STEP] [2023-05-13 22:13:53] Free space checking...
    [INFO] [2023-05-13 22:13:53] Checking if there is enough amount of free space
    [INFO] [2023-05-13 22:13:53] Requires at least 1469865096 bytes. [1.37 GB]
    [INFO] [2023-05-13 22:13:53] Disk free space function is disabled by hosting.
    [INFO] [2023-05-13 22:13:53] Using dummy file to check free space (it can take some time).

    I have the following settings in my wp-config.php file:

    
    @ini_set( 'upload_max_filesize' , '1750M' );
    @ini_set( 'post_max_size', '1750M');
    @ini_set( 'memory_limit', '1750M' );
    @ini_set( 'max_execution_time', '0' );
    @ini_set( 'max_input_time', '3000' );
    Plugin Support MixHa

    (@mixha)

    Hello @rangrsite ,

    It seem like you have very low execution limit threshold, which caused the process to stop while it was trying to check the free space.

    In our plugin it is possible to disable free space checks, but it’s not recommended and you should do that only if you’re 100% sure that you have enough space on the server for the backup.

    If you don’t have enough space for the backup or migration, but you will tell the plugin that there is enough, the process may still fail and your site may encounter many issues due to the lack free space.

    Step list of the solution:

    1. Go to “Other options” section
    2. Disable space checking: https://prnt.sc/PAlbYsz3RszJ
    3. Disable PHP CLI checking: https://prnt.sc/1sljr31
    4. Change backup method: https://prnt.sc/1s1ofpa
    5. Save “Other options” section
    6. Force stop both processes: https://prnt.sc/1trv1tm
    7. Run your process once again

    Let me know if that resolves your issue 🙂
    Thank you!

    P.S. You should not publicly share backup links.

    Plugin Support MixHa

    (@mixha)

    Hey @rangrsite ,

    We haven’t heard from you since, so I’ll assume that the issue is resolved and will close this support ticket. If you face any new issues, please feel free to open a new ticket.

    Kind regards

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Restore Failed’ is closed to new replies.