Forum Replies Created

Viewing 15 replies - 1 through 15 (of 32 total)
  • Thread Starter peterlaz

    (@peterlaz)

    I am using SEOPRESS PRO ver 9.1.

    I am not using any caching plugin.

    Backup log

    [INFO] BackWPup 4.1.4; A project of WP Media
    [INFO] WordPress 6.6.2 on https://***.com/
    [INFO] Log Level: Normal
    [INFO] BackWPup job: Daily Backup (Auto)
    [INFO] Logfile is: backwpup_log_bf149b_2024-09-14_20-03-12.html
    [INFO] Backup file is: 2024-09-14_20-03-12_X5KMZ3ZM01.zip
    [14-Sep-2024 20:03:12] 1. Try to backup database …
    [14-Sep-2024 20:03:12] Connected to database ****_*** on localhost
    [14-Sep-2024 20:03:12] Added database dump "***_***.sql" with 256.86 KB to backup file list
    [14-Sep-2024 20:03:12] Database backup done!
    [14-Sep-2024 20:03:12] 1. Trying to make a list of folders to back up …
    [14-Sep-2024 20:03:15] Added "wp-config.php" to backup file list
    [14-Sep-2024 20:03:15] 915 folders to backup.
    [14-Sep-2024 20:03:15] 1. Trying to create a WordPress export to XML file …
    [14-Sep-2024 20:03:15] Check WP Export file …
    [14-Sep-2024 20:03:15] WP Export file is a valid WXR file.
    [14-Sep-2024 20:03:15] Added XML export "***.wordpress.2024-09-14.xml" with 16.44 KB to backup file list.
    [14-Sep-2024 20:03:15] 1. Trying to generate a file with installed plugin names …
    [14-Sep-2024 20:03:15] Added plugin list file "***.pluginlist.2024-09-14.txt" with 890.00 B to backup file list.
    [14-Sep-2024 20:03:15] 1. Trying to generate a manifest file …
    [14-Sep-2024 20:03:15] Added manifest.json file with 2.27 KB to backup file list.
    [14-Sep-2024 20:03:15] 1. Trying to create backup archive …
    [14-Sep-2024 20:03:15] Compressing files as ZipArchive. Please be patient, this may take a moment.
    [14-Sep-2024 20:03:40] Backup archive created.
    [14-Sep-2024 20:03:40] Archive size is 33.80 MB.
    [14-Sep-2024 20:03:40] 6890 Files with 99.18 MB in Archive.
    [14-Sep-2024 20:03:41] 1. Trying to send backup file to S3 Service …
    [14-Sep-2024 20:03:41] Connected to S3 Bucket "**" in us-west-2
    [14-Sep-2024 20:03:41] Checking for not aborted multipart Uploads …
    [14-Sep-2024 20:03:41] Starting upload to S3 Service …
    [14-Sep-2024 20:03:45] Backup transferred to https://s3.us-west-2.amazonaws.com/***.com/2024-09-14_20-03-12_X5KMZ3***1.zip.
    [14-Sep-2024 20:03:46] 1. Trying to check database …
    [14-Sep-2024 20:03:46] Database check done!
    [14-Sep-2024 20:03:46] Job done in 34 seconds.

    WordPress version: 6.6.2
    BackWPup version: 4.1.4
    PHP version: 7.4.33 (64bit)
    MySQL version: 10.3.39-MariaDB
    cURL version: 7.61.1
    cURL SSL version: OpenSSL/1.1.1k
    WP-Cron url: https://***.com/wp-cron.php
    Server self connect: Not expected HTTP response:
    Status-Code: 200
    Date: Sat, 14 Sep 2024 12:10:59 GMT
    Server: Apache/2
    Expires: Wed, 11 Jan 1984 05:00:00 GMT
    Cache-control: no-cache, must-revalidate, max-age=0
    Upgrade: h2,h2c
    Vary: User-Agent
    Content-length: 0
    Content-type: text/html; charset=UTF-8

    Document root: /home/adst/domains/.com/private_html
    Temp folder: /home/adst/domains/.com/public_html/wp-content/uploads/backwpup/54ccef/temp/
    Log folder: /home/adst/domains/.com/public_html/wp-content/uploads/backwpup/54ccef/logs/
    Server: Apache/2
    Operating System: Linux
    PHP SAPI: fpm-fcgi
    Current PHP user: adstar
    Maximum execution time: 30 seconds
    BackWPup maximum script execution time: 30 seconds
    Alternative WP Cron: Off
    Disabled WP Cron: Off
    CHMOD Dir: 0755
    Server Time: 12:10
    Blog Time: 20:10
    Blog Timezone: Asia/Kuala_Lumpur
    Blog Time offset: 8 hours
    Blog language: en-US
    MySQL Client encoding: utf8
    PHP Memory limit: 256M
    WP memory limit: 40M
    WP maximum memory limit: 256M
    Memory in use: 4.00 MB
    Disabled PHP Functions:: exec, system, passthru, shell_exec, proc_close, proc_open, dl, popen, show_source, posix_kill, posix_mkfifo, posix_getpwuid, posix_setpgid, posix_setsid, posix_setuid, posix_setgid, posix_seteuid, posix_setegid, posix_uname
    Loaded PHP Extensions:: Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, bcmath, calendar, cgi-fcgi, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imagick, imap, intl, ionCube Loader, json, libxml, mbstring, mysqli, mysqlnd, openssl, pcre, pdo_mysql, pdo_sqlite, posix, session, shmop, soap, sockets, sodium, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tokenizer, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib

    I am facing the same problem with the latest of Backwpup version 4.1.4. Please help. Thank you.

    Yes the manual backup now works with the addition of the alternate cron, however scheduled backups does not fire. Why?

    Thread Starter peterlaz

    (@peterlaz)

    I managed to resolve the issue. The settings in the Security Plugin to “Deny Bad Query Strings via rules in .htaccess file to prevent malicious string attacks using XSS” has broken the SMTP mail delivery functionality. The mail delivery is now working like a charm.

    Thank you very much for your assistance.

    Thread Starter peterlaz

    (@peterlaz)

    Thank you for the prompt response. Since the plugin is now fully responsive, I will use it with the default settings for the ticker width.

    What was working perfectly suddenly became broken when upgraded to version 4.3.11.

    Thread Starter peterlaz

    (@peterlaz)

    Thanks for the amended code. It works like a charm.

    Thread Starter peterlaz

    (@peterlaz)

    Thank you for the support.

    The settings within the widget remains intact after the upgrade. However, the colors set for individual social icons were done using CSS code. The following CSS code is no longer working under version 3.

    
    .simple-social-icons li.ssi-facebook a {
        background-color: #3b5998 !important;
    }
    .simple-social-icons li.ssi-gplus a {
        background-color: #dd4b39 !important;
    }
    .simple-social-icons li.ssi-instagram a {
        background-color: #9b3f71  !important;
    }
    .simple-social-icons li.ssi-twitter a {
        background-color: #00aced !important;
    }  
    .simple-social-icons li.ssi-youtube a {
        background-color: #bb0000 !important;
    }
    
    Thread Starter peterlaz

    (@peterlaz)

    Thanks Nick for reaching out promptly.

    My early suspicion of a flaw in the code is proven to be baseless. After working extensively with my hosting company I have positively identified issue.

    The issue is documented in https://wpvulndb.com/vulnerabilities/8807

    The hacker somehow gained access to my website and planted the file xmxweoko.php in the plugin folder wp-content/plugins/genesis-featured-page-advanced/languages/

    This could possibly allow the attacker to intercept the email containing the password reset link in some cases requiring user interaction as well as without user interaction.

    Admittedly the site in question was only a test site without much security setup. I have deleted the entire site and will start again fresh as it is only for testing purposes.

    Luckily, my live sites are adequately protected with premium security plugin. A scan with Sucuri’s site scanner shows they are all safe.

    Once again thank you very much for this lovely plugin.

    Thread Starter peterlaz

    (@peterlaz)

    This is what I am suspecting now as the file xmxweoko.php is not native to the plugin.

    Thread Starter peterlaz

    (@peterlaz)

    The offending file has been identified as
    /home/plan2040/public_html/wp-content/plugins/genesis-featured-page-advanced/languages/xmxweoko.php

    Thread Starter peterlaz

    (@peterlaz)

    I have also updated the studiopress forum on this matter.

    Thread Starter peterlaz

    (@peterlaz)

    It is really very silly of me to make such an elementary mistake.

    I am glad it is resolved now.

Viewing 15 replies - 1 through 15 (of 32 total)