ERROR: S3 Bucket “mybucketname” does not exist!

  • Resolved Tech4Eleven

    (@tech4eleven)


    4 years, 4 months ago

    I have BackWPup on about 20 of the websites that I manage, including my own websites. On all of them I’m sending the backup to my Amazon S3 storage and on all of them it very frequently happens where the backup with fail saying “ERROR: S3 Bucket “mybucketname” does not exist!” Then I have to sign into the site that gives this error and re-enter the S3 Secret Key and then it works again, until it doesn’t. This has really been happening for years but I’d like to finally get to the bottom of it. Any suggestions?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support happyAnt

    (@duongcuong96)

    @tech4eleven
    hmm, so you said for an unknown reason, the S3 secret key just empty and you have to re-enter it again? Do you currently run any WordPress database clean plugin?
    Thank you!

    • This reply was modified 4 years, 4 months ago by happyAnt.
    Thread Starter Tech4Eleven

    (@tech4eleven)

    Yes thats correct. No, I do not use any WordPress database clean plugin. Seems like it just happens randomly. My 20 websites are all on different web hosts too.

    Plugin Support happyAnt

    (@duongcuong96)

    @tech4eleven
    hmm, is it possible for you to list all activated plugin name on the site got the issue to me?
    Thank you!

    Thread Starter Tech4Eleven

    (@tech4eleven)

    Certainly. I just had this issue on my own website this week. Here are my plugins:

    Active plugins:
    ——————————
    Akismet Anti-Spam
    BackWPup
    Contact Form 7
    Custom 404
    Disable Gutenberg
    Google Analytics
    InfiniteWP – Client
    Invisible reCaptcha
    Post SMTP
    Preloader
    Really Simple SSL
    Rotating Tweets (Twitter widget & shortcode)
    Smooth Scroll
    The Grid
    White Label
    WP Super Cache
    Yoast SEO

    Inactive plugins:
    ——————————
    Convert Plus

    Plugin Support happyAnt

    (@duongcuong96)

    @tech4eleven
    could you please give me your server info(please remove your domain) in BackWPUp -> Settings -> Server info.
    Thank you!

    Thread Starter Tech4Eleven

    (@tech4eleven)

    WordPress version: 5.4.2
    BackWPup version: 3.7.1
    PHP version: 7.1.33 (64bit)
    MySQL version: 5.6.41-84.1
    cURL version: 7.71.0
    cURL SSL version: OpenSSL/1.1.1g
    WP-Cron url: https://123.com/wp-cron.php
    Server self connect: Response Test O.K.
    Document root: /how/xxxx/public_html
    Temp folder: /how/xxxx/public_html/wp-content/uploads/backwpup-68beaf-temp/
    Log folder: /home4/xxxx/public_html/wp-content/uploads/backwpup-68beaf-logs/
    Server: Apache
    Operating System: Linux
    PHP SAPI: cgi-fcgi
    Current PHP user: 123
    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: 19:1
    Blog Time: 13:01
    Blog Timezone: America/Denver
    Blog Time offset: -6 hours
    Blog language: en-US
    MySQL Client encoding: utf8mb4
    PHP Memory limit: 256M
    WP memory limit: 40M
    WP maximum memory limit: 256M
    Memory in use: 56.00 MB
    Loaded PHP Extensions:: Core, PDO, PDO_ODBC, Phar, Reflection, SPL, SimpleXML, bcmath, bz2, calendar, cgi-fcgi, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, imagick, imap, intl, ionCube Loader, json, libxml, mbstring, mcrypt, mysqli, mysqlnd, odbc, openssl, pcntl, pcre, pdo_mysql, pdo_pgsql, pdo_sqlite, pgsql, posix, pspell, readline, session, soap, sockets, sqlite3, standard, tidy, tokenizer, wddx, xml, xmlreader, xmlrpc, xmlwriter, xsl, zip, zlib

    • This reply was modified 4 years, 4 months ago by Tech4Eleven.
    Plugin Support happyAnt

    (@duongcuong96)

    Hello @tech4eleven
    hmm I just my guess, If I was on the case, I will try to monitor the InfiniteWP plugin

    Closed because of inactivity

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘ERROR: S3 Bucket “mybucketname” does not exist!’ is closed to new replies.