The 502/503/504 are HTTP status codes that a server can send back when it was unableto complete a request. There can be several different causes for the error. Below are some common fixes when using Duplicator.
Issue AGeneral 500 Errors
During the install process you receive a more general error with a 500/502/503/504 status.
Solution 1ModSec
Check to make sure your host does not have a mod_security (ModSec) rule that gets tripped. On some servers running allot of database commands or even unzipping a file cantrigger a mod_security black list rule. This simply means the host your on is blocking your IP from doing certain operations. This can easily be solved by contactingyour host and making sure they don’t have a mod_security rule that is blocking you from accessing the installer properly.
Solution 23rd Party Services
There are a few issues around WordFence and Cloudflare that can cause these codes. See the FAQ below for details:
- What can I try for 502/503/504 Gateway issues during the build?
Solution 3DYI
During the install process it is possible that your host might automatically lay-down a .htaccess file. Typically Duplicator works best if no .htaccess files are presentdurning the install process as some of the directives in the file can cause conflicts. If your wanting to try and resolve the issue your-self without your hosts assistance thencheck out the article below:
- How to Fix 504 Gateway Timeout Error in WordPress
Solution 4Permissions
A 500 error in Step 1 processing on Duplicator Lite can sometimes be due to a timeout during zip extraction or on Duplicator Lite or Pro when file permissions are being set.To get around this, first do a Manual Extraction then uncheck the Files and Directorypermissions boxes on Step 1 of the installer.
Solution 5Cloudflare
If you’re using Cloudflare the below settings may help
- Log in to Cloudflare
- From Overview Page click “Advanced” > Click “Pause”
- Run installer deployment
- Turn Cloudflare back on
Issue BAJAX 503
During the install process you receive an error titled ” AJAX ERROR! STATUS:503 Service Unavailable”
Solution 1In the event the host you are on has issues with AJAX callbacks the best solution is run a manual install. For a step by step run of this processsee the FAQ item How do I do a ‘Manual Extraction’ or run installer without Zip enabled?.
Notice: The quickest way to isolate this error is contact your hosting provider or server admin. They will be able to monitor the web server logs for clues much quickerthat our support staff can with logs only generated by PHP.
Добрый день. Несколько недель назад на разных сайтах, которые расположены на разных хостингах при попытке создания бекапа плагин duplicator выдает то 500, то 504 ошибки Internal Server Error. Бэкапы до ошибки не успевают создаваться. Плагин нигде не обновлялся, вордпресс где-то обновился сам, где-то нет. Все версии разные, но не работают повально все. Пробовала изменять значение max_execution_time но никак не повлияло. Уже не знаю даже куда копать.
-
Вопрос заданболее трёх лет назад
-
1316 просмотров
Tell me please.
With the help of a duplicator free made a site archive.
I could successfully install the site on the test domain.
– exemple1.com
Everything worked!
At the new hosting and other domain examle2.com, the installation ends with an error – 500.
The archive is the same.
The hoster even gave me more resources at the time of installation, but an error still appears – 500.
Nothing happens to do anything.
In the site directory according to the file manual: readme.html, I manually prescribed the name of the new hosting database. Username and password.
The installation continues, but interrupts the Server Code: 200
Unauthorized Access: Please provide a password!
FILE:/home/domainname/public_html/dup-installer/classes/class.logging.php[200]
TRACE:
#0 /home/domainname/public_html/dup-installer/main.installer.php(229): DUPX_Log::error(‘Unauthorized Ac…’)
#1 {main}
What other password does he need?
I entered the database password.
Thanks for the help.
-
This topic was modified 1 year, 4 months ago by
weiuffu.
Local | Local WordPress development made simple
- Download
- Releases
- Feature Requests
- Help Docs
- API
Blog
Issue:
During scanning stage of running the Duplicator plugin on a WordPress site, there was an error: Server Error 500.
Solution:
Modify /etc/php.ini file to increase memory:
memory_limit = 256M
from 128M
Tricks:
Even there is error during the scanning stage, Duplicator still allowed building step to proceed and showing no error.
Error 500 actually does not tell anything informative
No special message was logged in Apache web server
Config:
- PHP 5.6.30
- WordPress 4.7.4
- Duplicator 1.2.4