WordPress duplicator ошибка

Archive Upload Issues

Issue AImport Link
How to resolve import links not properly pulling down the archive?

Currently not every url will work with the import feature. Below is a table of what is currently supported.

Status Source Notes
Generic Host Most hosts that allow .zip or .daf files to be downloaded directly should work. If issues arise with a specific host try the download directlyfrom your browser and if issues arise then contact your host.
Dropbox Dropbox is currently supported.
Google Drive Google Drive is currently supported Starting in 4.5.9
AWS This is currently not supported.
OneDrive This is currently not supported.

Issue BImport File
How to resolve import file (drag-n-drop) archives not uploading?

Common Error Messages

AJAX ERROR! STATUS:403 Forbidden

Solution 1AJAX 403 Forbidden
In the event you receive a “AJAX ERROR! STATUS:403 Forbidden” message consider checking to make sure you do not have Imunify360 enabled. For more details see the FAQ itemHow to fix installer validation checks (Issue A)?.

If Imunify360 is not installedits possible you might have a .htaccess file that is preventing requests to access the proper server paths. In this case we recommend letting your host know or justtrying Solution 2 or 5.

Solution 2Manual Upload
If the file or link upload of the archive.zip/daf file is having issues simply FTP the archive file upto the server which will allow it to show in the import list. In order to manually uploada Duplicator archive follow these instructions:

  1. Open an FTP Client -OR- go to your host’s control panel (cPanel) file manager.
  2. Copy the archive.zip/daf file to the WordPress root -OR- to wp-contentbackups-dup-proimports directory.
    Note: The WordPress root is normally where your wp-config.php is located allow with the wp-admin and wp-content folders.
  3. Browse to Duplicator Pro > Import screen and look for the uploaded archive file in the archive list.
Installer Launch Issues

Issue CInstaller Start
How to resolve import installer launch issues?

Common Error Messages

Duplicator cannot launch Import because on this Server it isn’t possible to execute PHP scripts in folders:
– /var/www/htdocs/wp-content/backups-dup-pro/imports
– /var/www/htdocs/

cURL error 7: Failed to connect to localhost port 8080: Connection refused”

Solution 1Server Permissions
If you see a permission error in the log consider visiting this FAQ for solving various permission issues. I get an error/warning about file permissions what should I do?

Solution 2PHP Execution
There are several items you check if the location where the import installer file is trying to run does not allow PHP execution.

  1. htaccess File:A block via htaccess file. For example an .htaccess files placed in the wp-content folder that prevented execution might look like this:

    <Files *.php>
    Order Deny,Allow
    Deny from all
    </Files>

    The presence of an .htaccess file in wp-content does not necessarily prevent execution. Solution: Temporarily rename the htaccess file

  2. Security Plugin: Some plugins like Wordfence “might” try to block the request. If this is the case try to temporarily disablethe plugin to see if it resolves the issue.
  3. Host or SoftwareIf the hosting has set the block via server setting the only solution is to ask the hosting to deactivate the block or change hostingOn other systems software like Secure 360 have the ability to prevent the execution of PHP files via cPanel settings.

Solution 3Install Modes
In the event your host does not allow for PHP execution in the directories where Duplicator is trying to run the import then you may need to switch to a differentInstall Mode. For example you could try an overwrite install mode by copying both the installer and archive tothe root directory, browse to https://{domain}/installer.php, then click ‘apply’ to reuse the database of the site you are overwriting. After that, just proceed with the install.

Solution 4Docker Container
If you are using Docker and running into curl errors consider changing how the port are setup. Modify the Apache2 conf inside the container so that Apache will respond inside on theoutside port.

See /etc/apache2/ports.confListen 80
Listen 8080
/etc/apache2/sites-available/000-default.conf<VirtualHost *:*>For more detailsto this solution see stack overflow.

Was this article helpful?

Related Articles

Источник

I can’t make a backup with Duplicator. The process reaches 59.7% and then stops giving me the following errors. The plugin informs me that my site occupies 5GB while the DB 12MB.

Phase 1
Scanning the site
Please wait…
Keep this window open during the scanning process.
It may take several minutes.
Phase 2
Package compilation 59.7%
Please wait…
Keep this window open and do not close it during the creation process.
This operation may take several minutes to complete.
Phase 3
It hangs at 59.7% for a long time.
Phase 4
Build status
Compilation aborted by host
This server cannot complete the build due to host setup constraints, see the error message for more details.
If the error details are not specific consider the options below by clicking each section.

********************************************************************************
DUPLICATOR-LITE PACKAGE-LOG: 5 February 2023 22:22
NOTICE: Do NOT post to public sites or forums 
********************************************************************************
VERSION:	1.5.2.1
WORDPRESS:	5.9.5
PHP INFO:	5.6.40 | SAPI: cgi-fcgi
SERVER:		Apache 
PHP TIME LIMIT: (0) no time limit imposed 
PHP MAX MEMORY: 4294967296 (1024M default) 
MEMORY STACK: 81.25MB

********************************************************************************
DATABASE:
********************************************************************************
BUILD MODE:   PHP(query limit - 100)
MYSQLTIMEOUT: 5000
MYSQLDUMP:    Not Supported
TABLES: total:22 | filtered:0 | create:22
FILTERED: []
SQL CREATED: 20230205_xxxxxxxxxxx_af3938eced030e1d8652_20230205222046_database.sql
SQL FILE SIZE: 9.74MB (10209995)
SQL FILE TIME: 2023-02-05 22:22:05
SQL RUNTIME: 2.70 sec.

********************************************************************************
ARCHIVE (ZIP):
********************************************************************************
ARCHIVE DIR:  /web/htdocs/www.nomeadominio.it/home
ARCHIVE FILE: 20230205_xxxxxxxxxxx_af3938eced030e1d8652_20230205222046_archive.zip
FILTERS: *OFF*
DIRS:
	not set
FILES:
	not set
EXTS:  not set
----------------------------------------
COMPRESSING
SIZE:	5.06GB
STATS:	Dirs 2,677 | Files 29,397
SQL ADDED: 20230205_xxxxxxxxxxx_af3938eced030e1d8652_20230205222046_database.sql
[PHP ERR][WARN] MSG:filesize(): stat failed for /web/htdocs/www.nomeadominio.it/home/ikkanews/----.mht [CODE:2|FILE:/web/htdocs/www.nomeadominio.it/home/wp-content/plugins/duplicator/classes/package/class.pack.archive.zip.php|LINE:172]
do_action('wp_ajax_duplicator_package_build'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, duplicator_package_build, DUP_Package->runZipBuild, DUP_Archive->build, DUP_Zip::create, filesize, DUP_Handler::error, DUP_Handler::getMessage
[PHP ERR][WARN] MSG:filesize(): stat failed for /web/htdocs/www.nomeadominio.it/home/----.mht [CODE:2|FILE:/web/htdocs/www.nomeadominio.it/home/wp-content/plugins/duplicator/classes/package/class.pack.archive.zip.php|LINE:172]
do_action('wp_ajax_duplicator_package_build'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, duplicator_package_build, DUP_Package->runZipBuild, DUP_Archive->build, DUP_Zip::create, filesize, DUP_Handler::error, DUP_Handler::getMessage

WARNING: Unable to zip files:
FILE: [/web/htdocs/www.nomeadominio.it/home/ikkanews/----.mht]
FILE: [/web/htdocs/www.nomeadominio.it/home/----.mht]

ZipArchive Object
(
    [status] => 0
    [statusSys] => 0
    [numFiles] => 32072
    [filename] => /web/htdocs/www.nomeadominio.it/home/wp-content/backups-dup-lite/tmp/20230205_xxxxxxxxxxx_af3938eced030e1d8652_20230205222046_archive.zip
    [comment] => 
)

FILE ADDED TO ZIP: 32071
COMPRESSION RESULT: '1'
COMPRESSED SIZE: 4.25GB
ARCHIVE RUNTIME: 436.76 sec.
MEMORY STACK: 94.75MB
building installer
[PHP ERR][WARN] MSG:No valid encoded path found in value '' for ioncube.loader.encoded_paths. [CODE:2|FILE:Unknown|LINE:0]
DUP_Handler::shutdown, DUP_Handler::error, DUP_Handler::getMessage

My hosting allows me to edit the following parameters (max_execution_time is already maxed out, memory_limit also):

PHP 8.1
PHP 8.0
PHP 7.4 (obsoleta)
PHP 7.3 (obsoleta)
PHP 7.2 (obsoleta)
PHP 7.1 (obsoleta)
PHP 7.0 (obsoleta)
PHP 5.6 (attualmente in uso ma obsoleta)
PHP 5.5 (obsoleta)
PHP 5.4 (obsoleta)
PHP 5.3 (obsoleta)
PHP 5.2 (obsoleta)
PHP 4.4 (obsoleta)
Nascondi versioni obsolete
display_errors Off
max_input_time 60
max_input_vars 1000
post_max_size 25M
zlib.output_compression Off
allow_url_fopen Off
opcache.jit Off
max_execution_time 900
memory_limit 1024M
output_buffering 4096
upload_max_filesize 25M
short_open_tag Off
mysqli.allow_local_infile Off
ioncube Off

Removing those files I get this log:

********************************************************************************
DUPLICATOR-LITE PACKAGE-LOG: 5 February 2023 23:05
NOTICE: Do NOT post to public sites or forums 
********************************************************************************
VERSION:	1.5.2.1
WORDPRESS:	5.9.5
PHP INFO:	5.6.40 | SAPI: cgi-fcgi
SERVER:		Apache 
PHP TIME LIMIT: (0) no time limit imposed 
PHP MAX MEMORY: 4294967296 (1024M default) 
MEMORY STACK: 80.75MB

********************************************************************************
DATABASE:
********************************************************************************
BUILD MODE:   PHP(query limit - 100)
MYSQLTIMEOUT: 5000
MYSQLDUMP:    Not Supported
TABLES: total:22 | filtered:0 | create:22
FILTERED: []
SQL CREATED: 20230205_xxxxxxxx_00bacebb0a0a153c8817_20230205230513_database.sql
SQL FILE SIZE: 9.72MB (10189462)
SQL FILE TIME: 2023-02-05 23:05:51
SQL RUNTIME: 2.35 sec.

********************************************************************************
ARCHIVE (ZIP):
********************************************************************************
ARCHIVE DIR:  /web/htdocs/www.nomeadominio.it/home
ARCHIVE FILE: 20230205_xxxxxxxx_00bacebb0a0a153c8817_20230205230513_archive.zip
FILTERS: *OFF*
DIRS:
	not set
FILES:
	not set
EXTS:  not set
----------------------------------------
COMPRESSING
SIZE:	5.06GB
STATS:	Dirs 2,676 | Files 29,395
SQL ADDED: 20230205_xxxxxxxx_00bacebb0a0a153c8817_20230205230513_database.sql
ZipArchive Object
(
    [status] => 0
    [statusSys] => 0
    [numFiles] => 32071
    [filename] => /web/htdocs/www.nomeadominio.it/home/wp-content/backups-dup-lite/tmp/20230205_xxxxxxxx_00bacebb0a0a153c8817_20230205230513_archive.zip
    [comment] => 
)

FILE ADDED TO ZIP: 32070

Источник

Добрый день. Несколько недель назад на разных сайтах, которые расположены на разных хостингах при попытке создания бекапа плагин duplicator выдает то 500, то 504 ошибки Internal Server Error. Бэкапы до ошибки не успевают создаваться. Плагин нигде не обновлялся, вордпресс где-то обновился сам, где-то нет. Все версии разные, но не работают повально все. Пробовала изменять значение max_execution_time но никак не повлияло. Уже не знаю даже куда копать.


  • Вопрос задан

    более трёх лет назад

  • 1316 просмотров

Источник

Learn more about WordPress Duplicator access denied error from our experts. Our WordPress Support team is here to help you with your questions and concerns.

WordPress Duplicator Access Denied | Troubleshooting Tips

If you have been running into the “WordPress Duplicator Access Denied” error, you have come to the right place.

WordPress Duplicator Access Denied | Troubleshooting Tips

This error occurs when we have permission-related issues while using the WordPress Duplicator plugin. This error message indicates that the plugin is unable to access or write files in certain directories due to insufficient permissions.

Let’s take a closer look at this error:

  • The error is due to the WordPress Duplicator plugin attempts to create or write files in specific directories, but it doesn’t have the necessary permissions to do so.
  • Insufficient permissions prevent the plugin from accessing the required directories and performing the necessary operations.
  • The error may be due to the directories where the plugin needs to write files not having appropriate write permissions set.
  • Alternatively, the error may be due to the directories not being owned by the correct user or group, leading to permission conflicts.
  • If the server has strict security configurations or restrictions that prevent the plugin from accessing certain directories we will run into the error.
  • We have to verify that the directories where the plugin needs to create or write files have the correct permissions.
    The recommended permissions for directories are usually 755. It grants read, write, and execute permissions to the owner, and read and execute permissions to the group and others.
  • Additionally, ensure that the directories are owned by the correct user or group.
  • We have to look for any server-level restrictions or security measures that could be interfering with the plugin’s file operations.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

To conclude, our Support Techs introduced us to WordPress Duplicator Access Denied error and demonstrated how to resolve it.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

Источник

I have duplicated my site using the duplicator plugin from wordpress.org. However, when I wanted to run this on a new hosting service, first I encountered a 504 gateway timeout error. Therefore, I extracted the .zip contents and chose for manual package extraction, which solved the problem, but after the second step, again in the final step (test), I run into a 403 access denied error.

  1. I checked my access permissions, they were OK. (755 for folders and 644 or 666 for files)
  2. I checked my .htaccess file, it seemed to be OK. (I deleted it and the error appeared again).
  3. There are no plugins on my domain or host which might cause interference as I am installing the package afresh.

I don’t know what is causing this problem.

My .htaccess file contents:

# 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

p u's user avatar

p u

1,3831 gold badge17 silver badges29 bronze badges

asked Apr 28, 2017 at 17:48

T J's user avatar

1

403 Forbidden error code is shown when your server permissions don’t allow access to a specific page.

Another possible cause could be a corrupt .htaccess file or incorrect file permissions on your server.

If you were already using an automatic WordPress backup plugin, then make sure that you have access to the latest backup before moving forward.

Deactivate all WordPress plugins

  • First thing you need to do is to temporarily deactivate all WordPress
    plugins. This includes any security plugins that you may have installed on your site.
  • If this resolves your problem, then this means one of the plugins on
    your website was causing this error.
  • You can figure out which plugin was causing the error by activating
    all your plugins one at a time until you are able to reproduce the
    403 forbidden error.

Corrupt .htaccess File

  • Often the 403 error is caused by a corrupt .htaccess file in your WordPress site. Repairing this file is quite easy.

  • You need to delete the file from your server. (get backup file)

  • Try accessing your website. If 403 forbidden error is resolved, then this means that your .htaccess file was corrupt.

  • You can generate a fresh .htaccess file by logging into your WordPress admin area and going to Settings » Permalinks page.
    Simply click on the Save Changes button at the bottom of the page and WordPress will generate a fresh .htaccess file.

File Permissions in WordPress

  • All folders on your WordPress site should have a file permission of
    744 or 755.

  • All files on your WordPress site should have a file permission of 644
    or 640.

  • You can set the file permission to the root folder to 744 or 755.
    Check the box next to ‘Recurse into subdirectories’ and then check
    the option that says ‘apply to directories only’.

I hope this helped you fix the 403 forbidden error in WordPress

answered Feb 26, 2020 at 3:33

Nmk's user avatar

NmkNmk

1,2732 gold badges14 silver badges25 bronze badges

This is old but I would like to post something I’m about to try. I found that «open_basedir» may be enabled by default on some hosts, like the one I’m using. So I sent a request to the provider to disable it from «php.ini» file.

answered Mar 8, 2021 at 22:31

David Eric Valtorta's user avatar

Источник

Понравилась статья? Поделить с друзьями:
  • Wordpad как включить выделение ошибок
  • Word шаблон ошибка
  • Word синтаксическая ошибка
  • Word пропустить все ошибки орфографии
  • Word произошла серьезная ошибка во время последнего запуска