Forum Replies Created

Viewing 15 replies - 16 through 30 (of 49 total)
  • I have a similar issue, using the Transposh plugin.

    The Google XML Sitemaps plugin generates a mydomain/sitemap.xml files, where all results are of the format https://mydomain.com/sitemap-pt-post-YYYY-MM.xml containing URLs of various languages, of the format https://mydomain.com/de/YYYY/MM/, https://freewheely.com/it/YYYY/MM/

    I don’t know why this hierarchy is confusing, and what I’m trying to achieve is to exclude some translations from the sitemap.

    @cocreation Thanks! Unfortunately, I can’t find where to change it.

    However, my php7 installation shows a max_execution_time of 300, so how does BackWPup fetches 600 from admin.php?page=backwpupsettings#backwpup-tab-information ?
    When I output <?php phpinfo(); ?> there’s no value set at 600

    And how does that explain, from the log posted above, that BackWPup restarts every 5 minutes (300 seconds), with either of:
    – WARNING: Job restarts due to inactivity
    – WARNING: ftp_nb_fput(): Restart position accepted (262652475)
    ?

    The only settings I can change in BackWPup settings panel is the timeout for FTP connection. I’ve set it to 30, and it prevents the transfer to complete after 30 seconds. So, how come the FTP timeout cuts the connection during the transfer? How can I make it happen, considering the max value of 300 seconds is not enough today (even if it completed in less than a minute with previous versions of BackWPup) ?

    Thanks

    Hi @duongcuong96,

    I have been facing the same problem for a couple of weeks.
    Nothing changed on the FTP server. I just kept updating WP and BackWPup (now 4.9.3 and 3.4.4). The backup file is around 400 MB. It used to backup fine on FTP, and still does it fine on localhost and Dropbox

    BackWPup settings:
    Maximum execution time 600 seconds

    Job settings:
    Timeout for FTP connection : 300s (maximum value)
    Use explicit SSL-FTP connection: yes
    Use passive mode: yes

    Log:

    [18-Mar-2018 22:50:50] 1. Try to send backup file to an FTP server …
    [18-Mar-2018 22:50:50] Connected via explicit SSL-FTP to server: 123.123.123.123:21
    [18-Mar-2018 22:50:50] FTP client command: USER <backwpup user>
    [18-Mar-2018 22:50:50] FTP server response: User <backwpup user> logged in.
    [18-Mar-2018 22:50:50] FTP client command: SYST
    [18-Mar-2018 22:50:50] FTP server reply: UNIX
    [18-Mar-2018 22:50:50] FTP current folder is: /mydomain/
    [18-Mar-2018 22:50:50] FTP client command: PASV
    [18-Mar-2018 22:50:50] FTP server reply: Entering passive mode
    [18-Mar-2018 22:50:50] Starting upload to FTP  …
    [18-Mar-2018 22:51:11] Restart after 23 seconds.
    [18-Mar-2018 22:51:12] Connected via explicit SSL-FTP to server: 123.123.123.123:21
    [18-Mar-2018 22:51:12] FTP client command: USER <backwpup user>
    [18-Mar-2018 22:51:12] FTP server response: User <backwpup user> logged in.
    [18-Mar-2018 22:51:12] FTP client command: SYST
    [18-Mar-2018 22:51:12] FTP server reply: UNIX
    [18-Mar-2018 22:51:12] FTP client command: PASV
    [18-Mar-2018 22:51:12] FTP server reply: Entering passive mode
    [18-Mar-2018 22:51:12] Starting upload to FTP  …
    [18-Mar-2018 22:56:12] WARNING: ftp_nb_fput(): Restart position accepted (262652475).
    [18-Mar-2018 21:56:12 UTC] PHP Warning: mysqli_ping(): MySQL server has gone away in /home/mydomain/www/wp-includes/wp-db.php on line 1690 [18-Mar-2018 22:56:12] ERROR: Cannot transfer backup to FTP server!
    [18-Mar-2018 22:56:12] Restart after 301 seconds.
    [18-Mar-2018 22:56:13] 2. Try to send backup file to an FTP server …
    [18-Mar-2018 22:56:13] Connected via explicit SSL-FTP to server: 123.123.123.123:21
    [18-Mar-2018 22:56:13] FTP client command: USER <backwpup user>
    [18-Mar-2018 22:56:13] FTP server response: User <backwpup user> logged in.
    [18-Mar-2018 22:56:13] FTP client command: SYST
    [18-Mar-2018 22:56:13] FTP server reply: UNIX
    [18-Mar-2018 22:56:13] FTP client command: PASV
    [18-Mar-2018 22:56:13] FTP server reply: Entering passive mode
    [18-Mar-2018 22:56:13] Starting upload to FTP  …
    [18-Mar-2018 23:01:13] WARNING: ftp_nb_fput(): Restart position accepted (262652475).
    [18-Mar-2018 22:01:13 UTC] PHP Warning: mysqli_query(): MySQL server has gone away in /home/mydomain/www/wp-includes/wp-db.php on line 1924 [18-Mar-2018 22:01:13 UTC] PHP Warning: mysqli_query(): Error reading result set's header in /home/mydomain/www/wp-includes/wp-db.php on line 1924 [18-Mar-2018 23:01:13] ERROR: Cannot transfer backup to FTP server!
    [18-Mar-2018 23:01:13] Restart after 301 seconds.
    [18-Mar-2018 23:01:14] 3. Try to send backup file to an FTP server …
    [18-Mar-2018 23:01:14] Connected via explicit SSL-FTP to server: 123.123.123.123:21
    [18-Mar-2018 23:01:14] FTP client command: USER <backwpup user>
    [18-Mar-2018 23:01:14] FTP server response: User <backwpup user> logged in.
    [18-Mar-2018 23:01:14] FTP client command: SYST
    [18-Mar-2018 23:01:14] FTP server reply: UNIX
    [18-Mar-2018 23:01:14] FTP client command: PASV
    [18-Mar-2018 23:01:14] FTP server reply: Entering passive mode
    [18-Mar-2018 23:01:14] Starting upload to FTP  …
    [18-Mar-2018 23:06:14] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [18-Mar-2018 23:06:14] 3. Try to send backup file to an FTP server …
    [18-Mar-2018 23:06:14] Connected via explicit SSL-FTP to server: 123.123.123.123:21
    [18-Mar-2018 23:06:14] FTP client command: USER <backwpup user>
    [18-Mar-2018 23:06:14] FTP server response: User <backwpup user> logged in.
    [18-Mar-2018 23:06:14] FTP client command: SYST
    [18-Mar-2018 23:06:14] FTP server reply: UNIX
    [18-Mar-2018 23:06:14] FTP client command: PASV
    [18-Mar-2018 23:06:14] FTP server reply: Entering passive mode
    [18-Mar-2018 23:06:14] Starting upload to FTP  …
    [18-Mar-2018 23:06:14] WARNING: ftp_nb_fput(): Restart position accepted (268652475).
    [18-Mar-2018 22:06:14 UTC] PHP Warning: mysqli_query(): MySQL server has gone away in /home/mydomain/www/wp-includes/wp-db.php on line 1924 [18-Mar-2018 22:06:14 UTC] PHP Warning: mysqli_query(): Error reading result set's header in /home/mydomain/www/wp-includes/wp-db.php on line 1924 [18-Mar-2018 23:06:14] ERROR: Cannot transfer backup to FTP server!
    [18-Mar-2018 23:06:14] Restart after 301 seconds.
    [18-Mar-2018 23:06:37] ERROR: Step aborted: too many attempts!

    Sometimes I end up with a bit of the 400 MB file on the server (up to 250ish MB).
    When I first set that backup up (on 2016-09-13), the job finished successfully in 36 seconds with a 420 MB file.

    • This reply was modified 8 years, 4 months ago by jbd7.
    • This reply was modified 8 years, 4 months ago by jbd7.
    • This reply was modified 8 years, 4 months ago by jbd7.

    Hi, I have the same problem with BackWPup 3.4.4
    I have a backup job to 3 locations, local folder, FTP and Dropbox. All leave old backup files despite having set a value for “file deletion”.

    Is there a solution to make the plugin work again other than deleting the job and recreating it?

    Hi,

    I have the same problem. Since mid-december, for a same backup size (380 MB) as previous successful backups, BackWPup fails to upload to Dropbox. Local backups and uploads to remote FTP servers still happen fine.

    Now that I cleared the cache, I have, on top of Dropbox failing, the WARNING: mysqli_ping(): MySQL server has gone away errors.

    [03-Jan-2017 14:05:40] 1. Try to send backup file to Dropbox …
    [03-Jan-2017 14:05:41] Authenticated with Dropbox of user: XXX
    [03-Jan-2017 14:05:41] Uploading to Dropbox …
    [03-Jan-2017 14:07:00] WARNING: mysqli_ping(): MySQL server has gone away
    [03-Jan-2017 14:12:16] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [03-Jan-2017 14:12:17] 2. Try to send backup file to Dropbox …
    [03-Jan-2017 14:12:17] Authenticated with Dropbox of user: XXX
    [03-Jan-2017 14:12:17] Uploading to Dropbox …
    [03-Jan-2017 14:13:57] WARNING: mysqli_ping(): MySQL server has gone away
    [03-Jan-2017 14:15:35] WARNING: mysqli_ping(): MySQL server has gone away
    [03-Jan-2017 14:17:16] WARNING: mysqli_ping(): MySQL server has gone away
    [03-Jan-2017 14:23:20] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [03-Jan-2017 14:23:20] 3. Try to send backup file to Dropbox …
    [03-Jan-2017 14:23:21] Authenticated with Dropbox of user: XXX
    [03-Jan-2017 14:23:21] Uploading to Dropbox …
    [03-Jan-2017 14:25:35] WARNING: mysqli_ping(): MySQL server has gone away
    [03-Jan-2017 14:26:43] WARNING: mysqli_ping(): MySQL server has gone away
    [03-Jan-2017 14:27:44] WARNING: mysqli_ping(): MySQL server has gone away
    [03-Jan-2017 14:29:08] WARNING: mysqli_ping(): MySQL server has gone away
    [03-Jan-2017 14:34:30] WARNING: Job restarts due to inactivity for more than 5 minutes.
    [03-Jan-2017 14:34:30] ERROR: Step aborted: too many attempts!

    Sorry for the double post, but I found a great hint by @itoben on https://wordpress.org/support/topic/ssl23-error-unknow/page/2/

    As explained in French here (https://bugs.reinom.com/view.php?id=1783), OVH installs SSL certificates on the load balancer, while an intra-site request remains local and thus bypasses the certificate.

    If you force HTTPS on your website, you can use the http://website:443 trick.

    I put that in my child theme functions.php :

    function ovhwpcron($url) {
      if ($url == "https://website.com/wp-cron.php") return "http://website.com:443/wp-cron.php";
    return $url;
    }
    add_filter('site_url', 'ovhwpcron');

    And now BackWPup works again (and probably another plugin too, which relies on wp-cron.php, that had stopped without me noticing).

    That looks like a cheap hook, so if you write a cleaner solution than this, or a solution that catches all SSL23_GET_SERVER_HELLO:unknown protocol errors caused by the OVH shared hosting setup, feel free to share.

    jb

    Anthony, same here.
    It seems it impacts OVH clients switching to HTTPS with Let’s Encrypt.

    The plugin already provided by Daniel doesn’t restore the functionality. BackWPup still doesn’t want to start any job, even manually.

    You could look at the UpdraftPlus plugin, nowhere as good as BackWPup, but it works …

    Hi Vandakam & Ofer,
    I have the same message with Transposh 0.9.9.0 at line 2069, and it doesn’t translate anymore.
    Have you found a fix yet?
    Thanks,
    jb

    I see.
    I have a website on which even the cron job doesn’t even start, after moving to HTTPS

    Thread Starter jbd7

    (@jbd7)

    Hi,

    Thanks for investigating.
    You can check at http://wurl.cc/F3d , is it the only message in the console.

    jb

    Hi Daniel and vincenzo75

    I have the same problem, and Daniel’s plugin doesn’t change anything.
    The scheduled backup via a cron job works fine, but the “run now” issues an error, that same:

    Server self connect:	Not expected HTTP response:
       WP Http Error: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

    Have you guys found a solution?
    My host is OVH as well (Perso 2014). I have read that they disabled SSLv3 and one must use TLS >= 1.0.
    Does that help?

    Thanks,

    jb

    Hi tosunkaya,

    It seems you have resolved the problem on your website. How did you do it?

    Thanks for sharing

    Thread Starter jbd7

    (@jbd7)

    Thanks for your clarification.

    Thread Starter jbd7

    (@jbd7)

    For those interested, this is what I added in the JS of the plugin to make it consider the height of the WPR static menu:

    if (document.getElementById('wprmenu_bar').offsetHeight == null) {
        adjustment = 0;
      }
    else {
        adjustment = document.getElementById('wprmenu_bar').offsetHeight;
    }
    
    toolbar_top = parseInt(image_offset.top) + 10 - adjustment; ...

    Hi all,

    Just to contribute a bit: this same error happens to me, but only for 1 image. It’s the image that is significantly larger than the other ones: > 5 MB and dimensions of 7974 x 11421.

    As mentioned above, it could therefore be a memory issue. I am not trying to fix it as I don’t need to, I may not even be able to since I am on a shared hosting.

Viewing 15 replies - 16 through 30 (of 49 total)