Support » Plugin: BackWPup - WordPress Backup Plugin » backup no longer starts

  • Resolved lello1

    (@lello1)


    I have always used the plugin without problems … but now it says to me like this:
    it is running, but did not declare for 10 seconds
    what can I do, thanks:

    Versione di WordPress: 5.3.2
    Versione di BackWPup: 3.7.0
    Versione PHP: 5.6.40 (64bit)
    Versione MySQL: 5.7.27-30-log
    Versione cURL: 7.67.0
    Versione SSL cURL: OpenSSL/1.0.2k-fips
    WP-Cron url:: https://www.liceonuzzi.edu.it/wordpress01/wp-cron.php
    Auto Connessione: Risposta HTTP non prevista:
    Codice-Stato: 403
    Server: aruba-proxy
    Date: Sun, 15 Mar 2020 12:18:11 GMT
    Content-type: text/html; charset=iso-8859-1
    Vary: Accept-Encoding
    Content-encoding: gzip
    Contenuto: <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”>
    <html><head>
    <title>403 Forbidden</title>
    </head><body>
    <h1>Forbidden</h1>
    <p>You don’t have permission to access this resource.</p>
    </body></html>

    Document root: /web/htdocs/www.liceonuzzi.edu.it/home/
    Cartella temporanea:: /web/htdocs/www.liceonuzzi.edu.it/home/wordpress01/wp-content/uploads/backwpup-a851ef-temp/
    Cartella di log:: /web/htdocs/www.liceonuzzi.edu.it/home/wordpress01/wp-content/uploads/backwpup-ca3011-logs/
    Server: Apache
    Sistema operativo: Linux
    PHP SAPI: cgi-fcgi
    Utente PHP corrente: ID14472263
    Tempo massimo di esecuzione: 120 secondi
    Tempo di esecuzione massima per lo script BackWpUp: 30 secondi
    WP cron alternativo: Off
    Disabilita WP Cron: Off
    CHMOD per la directory: 493
    Orario del server: 12:18
    Orario del blog: 13:18
    Fuso orario del blog: Europe/Rome
    Differenza di tempo per il Blog: 1 ore
    Lingua del blog: it-IT
    Codifica client MySQL: utf8
    Limite di memoria per PHP: 1024M
    Limite di memoria per WP: 1024M
    Limite massimo di memoria per WP: 256M
    Memoria in uso: 150,75 MB
    Funzioni PHP disabilitate:: system, popen, dl, passthru, proc_open, shell_exec
    Estensioni PHP caricate:: Core, PDO, Phar, Reflection, SPL, SimpleXML, SourceGuardian, Zend Guard Loader, bcmath, bz2, calendar, cgi-fcgi, ctype, curl, date, dom, ereg, exif, fileinfo, filter, ftp, gd, gettext, hash, http, iconv, imagick, imap, intl, ionCube Loader, json, libxml, mbstring, mcrypt, mhash, mysql, mysqli, mysqlnd, openssl, pcre, pdo_mysql, pdo_sqlite, posix, propro, raphf, session, soap, sqlite3, standard, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib

Viewing 7 replies - 1 through 7 (of 7 total)
  • I have the same problem: how can I solve this problem?

    Plugin Support duongcuong96

    (@duongcuong96)

    @lello1
    @protesilao
    This normally happens because your wp-cron.php has an issue( I saw there is permission issue in the server information )
    So I would suggest you contact the hoster and tell them about the issue because it related to the server-side.

    Or you can use alternative cron workaround:

    modify wp-config.php ( this file in site root directory ), and BEFORE the line:
    /* That’s all, stop editing! Happy blogging. */
    add this line:
    define('ALTERNATE_WP_CRON' , true );

    Hope that could help!

    But I doesn’t use wp-cron, I try to start manually my beckup. Also 5 days ago the backup work normally and I doesn’t changed anyting on the last 5 days.

    This is my debug info.:

    Versione di WordPress: 4.9.13
    Versione di BackWPup: 3.7.0
    Versione PHP: 7.2.28 (64bit)
    Versione MySQL: 5.7.29-cll-lve
    Versione cURL: 7.68.0
    Versione SSL cURL: OpenSSL/1.1.1d
    WP-Cron url:: https://studiomagi.com/wp-cron.php
    Auto Connessione: Risposta HTTP non prevista:
    Codice-Stato: 403
    Date: Mon, 16 Mar 2020 20:24:39 GMT
    Server: Apache
    Content-length: 318
    Content-type: text/html; charset=iso-8859-1
    Contenuto: <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”>
    <html><head>
    <title>403 Forbidden</title>
    </head><body>
    <h1>Forbidden</h1>
    <p>You don’t have permission to access this resource.</p>
    <p>Additionally, a 403 Forbidden
    error was encountered while trying to use an ErrorDocument to handle the request.</p>
    </body></html>

    Document root: /home/xggdsvwd/public_html/–studiomagi.com
    Cartella temporanea:: /home/xggdsvwd/public_html/–studiomagi.com/wp-content/uploads/backwpup-91235f-temp/
    Cartella di log:: /home/xggdsvwd/public_html/–studiomagi.com/wp-content/uploads/backwpup-91235f-logs/
    Server: Apache
    Sistema operativo: Linux
    PHP SAPI: fpm-fcgi
    Utente PHP corrente: xggdsvwd
    Tempo massimo di esecuzione: 30 secondi
    Tempo di esecuzione massima per lo script BackWpUp: 30 secondi
    WP cron alternativo: Off
    Disabilita WP Cron: Off
    CHMOD per la directory: 0755
    Orario del server: 20:24
    Orario del blog: 20:24
    Fuso orario del blog:
    Differenza di tempo per il Blog: 0 ore
    Lingua del blog: it-IT
    Codifica client MySQL: utf8
    Limite di memoria per PHP: 256M
    Limite di memoria per WP: 40M
    Limite massimo di memoria per WP: 256M
    Memoria in uso: 2,00 MB
    Funzioni PHP disabilitate:: mail, exec, , execve, passthru, shell_exec, system, proc_open, popen, parse_ini_file, show_source
    Estensioni PHP caricate:: Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, bz2, cgi-fcgi, ctype, curl, date, dom, enchant, exif, fileinfo, filter, ftp, gd, gettext, hash, iconv, intl, ionCube Loader, json, libxml, mbstring, mysqli, mysqlnd, openssl, pcntl, pcre, pdo_mysql, pdo_sqlite, posix, recode, redis, session, soap, sockets, sqlite3, standard, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib

    • This reply was modified 7 months, 1 week ago by protesilao.
    Plugin Support duongcuong96

    (@duongcuong96)

    @protesilao
    there is 403 response from your wp-cron.php, that why BackWPUp was not able to run correctly:

    WP-Cron url:: https://studiomagi.com/wp-cron.php
    Auto Connessione: Risposta HTTP non prevista:
    Codice-Stato: 403
    Date: Mon, 16 Mar 2020 20:24:39 GMT
    Server: Apache

    So I would suggest you to contact the hoster for help with the 403 error code response or use the alternative cron workaround I said above.

    Hope that could help ^^

    ok, thanks @duongcuong96

    Plugin Support duongcuong96

    (@duongcuong96)

    @protesilao
    any update on this?
    Thank you!

    Plugin Support duongcuong96

    (@duongcuong96)

    @protesilao
    since we haven’t heard back from you, I’m going to mark it as resolved.
    If you’re still having problems, feel free to let us know ;),

    Btw, If you find BackWPUp is useful for you, we would really appreciate. if you leave a positive review and rating.
    This would encourage us to develop new free features and provide free support 😀
    https://wordpress.org/support/plugin/backwpup/reviews/

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘backup no longer starts’ is closed to new replies.